Mailinglist Archive: opensuse (2460 mails)

[Jose <jtc@xxxxxxxxxxxxxxxxxxxxxxxx>]

Sandy Drobic wrote:
> J Sloan wrote:
> > Sandy Drobic wrote:
> > > Jose wrote:
> > >
> > > > I am suspecting something broken within syslogd, as I changed the 
> > > > parameter from -r to -rd and now it actually works using the script, 
> > > > I tried using without params and I still got a defunct process, it 
> > > > only likes to run regardless if using the script or not if I add the 
> > > > "d" parameter, weird, for now I can live with this till I find which 
> > > > is a similar switch on syslog-ng.
> > >
> > > Disable AppArmor, reboot and try again. Is syslogd running now? I had 
> > > the same problem when I migrated to 10.3.
> >
> > Why the reboot? Just disable apparmor or put it in complain, rather 
> > than enforce mode, and then a quick "rcsyslog restart" will do the trick.
>
> Let's call it bad experience and a lack of trust...

Hi Sandy,

thanks, that do work, I don't mind turning off apparmor off, but I 
wonder what would be the right settings for syslogd with apparmor on?

J
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx