[opensuse] syslogd not running
Hi list, I have a system running opensuse 10.3, I installed by default and then I got to install syslogd, I updated the /etc/sysconfig/syslog file with only one param for SYSLOGD_PARAMS="-r" and updated the other SYSLOG_DAEMON="syslogd" to reflect the change of daemons. I restart syslog on /etc/init.d and I keep getting: /etc/init.d/syslog start Starting syslog servicesstartproc: Empty pid file /var/run/syslogd.pid for /sbin/syslogd done But when I check the process I get: ps -aef | grep sysl root 5498 1 0 17:38 pts/2 00:00:00 /sbin/syslogd -r root 5499 5498 0 17:38 ? 00:00:00 [syslogd] <defunct> root 5518 3300 0 17:39 pts/1 00:00:00 grep sysl I have done this before with installing syslogd after I did a default install on lower versions than 10.3 and this is the first time I see this problem. I did reinstall the package from the internet and same results. All of the other config files are setup with the defaults Has anybody has come across this one? Any advice would be appreciate it. Thanks Joseph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-07-04 at 17:45 -0400, Jose wrote:
Any advice would be appreciate it.
Start the daemon directly from a terminal, using the same command line as the init script, and see if it writes some error to the screen Or you could use the now standard syslog-ng. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIbrN7tTMYHG2NR9URAh6iAJ9rka/327/S6bbGJjZrxBRtJaavmACfdBz1 97I02dE7SVWuUfZia4qqpV0= =bwFg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2008-07-04 at 17:45 -0400, Jose wrote:
Any advice would be appreciate it.
Start the daemon directly from a terminal, using the same command line as the init script, and see if it writes some error to the screen
Or you could use the now standard syslog-ng.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFIbrN7tTMYHG2NR9URAh6iAJ9rka/327/S6bbGJjZrxBRtJaavmACfdBz1 97I02dE7SVWuUfZia4qqpV0= =bwFg -----END PGP SIGNATURE-----
Thanks for the reply I tried it and got it back on line, but using the script fails Using syslogd -rd got this: vmware:/etc/init.d # syslogd -dr Allocated parts table for 1024 file descriptors. Starting. Called init. Called allocate_log, nlogs = -1. cfline(kern.warning;*.err;authpriv.none /dev/tty10) symbolic name: warning ==> 4 symbolic name: kern ==> 0 symbolic name: err ==> 3 symbolic name: none ==> 16 symbolic name: authpriv ==> 80 leading char in action: / filename: /dev/tty10 Called allocate_log, nlogs = 0. cfline(kern.warning;*.err;authpriv.none |/dev/xconsole) symbolic name: warning ==> 4 symbolic name: kern ==> 0 symbolic name: err ==> 3 symbolic name: none ==> 16 symbolic name: authpriv ==> 80 leading char in action: | filename: |/dev/xconsole Called allocate_log, nlogs = 1. cfline(*.emerg *) symbolic name: emerg ==> 0 leading char in action: * write-all Called allocate_log, nlogs = 2. cfline(mail.* -/var/log/mail) symbolic name: * ==> 255 symbolic name: mail ==> 16 leading char in action: / filename: /var/log/mail Called allocate_log, nlogs = 3. cfline(mail.info -/var/log/mail.info) symbolic name: info ==> 6 symbolic name: mail ==> 16 leading char in action: / filename: /var/log/mail.info Called allocate_log, nlogs = 4. cfline(mail.warning -/var/log/mail.warn) symbolic name: warning ==> 4 symbolic name: mail ==> 16 leading char in action: / filename: /var/log/mail.warn Called allocate_log, nlogs = 5. cfline(mail.err /var/log/mail.err) symbolic name: err ==> 3 symbolic name: mail ==> 16 leading char in action: / filename: /var/log/mail.err Called allocate_log, nlogs = 6. cfline(news.crit -/var/log/news/news.crit) symbolic name: crit ==> 2 symbolic name: news ==> 56 leading char in action: / filename: /var/log/news/news.crit Called allocate_log, nlogs = 7. cfline(news.err -/var/log/news/news.err) symbolic name: err ==> 3 symbolic name: news ==> 56 leading char in action: / filename: /var/log/news/news.err Called allocate_log, nlogs = 8. cfline(news.notice -/var/log/news/news.notice) symbolic name: notice ==> 5 symbolic name: news ==> 56 leading char in action: / filename: /var/log/news/news.notice Called allocate_log, nlogs = 9. cfline(*.=warning;*.=err -/var/log/warn) symbolic name: warning ==> 4 symbolic name: err ==> 3 leading char in action: / filename: /var/log/warn Called allocate_log, nlogs = 10. cfline(*.crit /var/log/warn) symbolic name: crit ==> 2 leading char in action: / filename: /var/log/warn Called allocate_log, nlogs = 11. cfline(*.*;mail.none;news.none -/var/log/messages) symbolic name: * ==> 255 symbolic name: none ==> 16 symbolic name: mail ==> 16 symbolic name: none ==> 16 symbolic name: news ==> 56 leading char in action: / filename: /var/log/messages Called allocate_log, nlogs = 12. cfline(local0,local1.* -/var/log/localmessages) symbolic name: * ==> 255 symbolic name: local0 ==> 128 symbolic name: local1 ==> 136 leading char in action: / filename: /var/log/localmessages Called allocate_log, nlogs = 13. cfline(local2,local3.* -/var/log/localmessages) symbolic name: * ==> 255 symbolic name: local2 ==> 144 symbolic name: local3 ==> 152 leading char in action: / filename: /var/log/localmessages Called allocate_log, nlogs = 14. cfline(local4,local5.* -/var/log/localmessages) symbolic name: * ==> 255 symbolic name: local4 ==> 160 symbolic name: local5 ==> 168 leading char in action: / filename: /var/log/localmessages Called allocate_log, nlogs = 15. cfline(local6,local7.* -/var/log/localmessages) symbolic name: * ==> 255 symbolic name: local6 ==> 176 symbolic name: local7 ==> 184 leading char in action: / filename: /var/log/localmessages Opened UNIX socket `/dev/log'. cannot create INET6 socket. Opened syslog UDP port. 0: 1F F F F F F F F F F X F F F F F F F F F F F F F F TTY: /dev/tty10 1: 1F F F F F F F F F F X F F F F F F F F F F F F F F PIPE: |/dev/xconsole 2: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 WALL: 3: X X FF X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/mail 4: X X 7F X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/mail.info 5: X X 1F X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/mail.warn 6: X X F X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/mail.err 7: X X X X X X X 7 X X X X X X X X X X X X X X X X X FILE: /var/log/news/news.crit 8: X X X X X X X F X X X X X X X X X X X X X X X X X FILE: /var/log/news/news.err 9: X X X X X X X 3F X X X X X X X X X X X X X X X X X FILE: /var/log/news/news.notice 10: 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 FILE: /var/log/warn 11: 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 FILE: /var/log/warn 12: FF FF X FF FF FF FF X FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FILE: /var/log/messages 13: X X X X X X X X X X X X X X X X FF FF X X X X X X X FILE: /var/log/localmessages 14: X X X X X X X X X X X X X X X X X X FF FF X X X X X FILE: /var/log/localmessages 15: X X X X X X X X X X X X X X X X X X X X FF FF X X X FILE: /var/log/localmessages 16: X X X X X X X X X X X X X X X X X X X X X X FF FF X FILE: /var/log/localmessages logmsg: syslog.info<46>, flags 4, from vmware, msg syslogd 1.4.1: restart (remote reception). Called fprintlog, logging to FILE /var/log/messages syslogd: restarted. Debugging disabled, SIGUSR1 to turn on debugging. I logon on another session with wrong credentials and it's logging now, but I am still tryng to figure out why it does not work with the default script -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-07-04 at 21:30 -0400, Jose wrote:
Thanks for the reply
I tried it and got it back on line, but using the script fails
Using syslogd -rd got this:
You have to try using the same syntax as the script uses, which is: startproc -p ${syslog_pid} ${syslog_bin} ${params} Or you could modify the first line of the script to #!/bin/bash -x so that it prints the entire lot to the screen when it runs and you can see what happens, hopefully. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIb3YBtTMYHG2NR9URAp4dAJ0QKmlmRO2QaCWxnNbH0SaVtl6NkgCfWh9q C7HxW7/f7ceZcHFnRoA0nYE= =W6tK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2008-07-04 at 21:30 -0400, Jose wrote:
Thanks for the reply
I tried it and got it back on line, but using the script fails
Using syslogd -rd got this:
You have to try using the same syntax as the script uses, which is:
startproc -p ${syslog_pid} ${syslog_bin} ${params}
Or you could modify the first line of the script to
#!/bin/bash -x
so that it prints the entire lot to the screen when it runs and you can see what happens, hopefully.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFIb3YBtTMYHG2NR9URAp4dAJ0QKmlmRO2QaCWxnNbH0SaVtl6NkgCfWh9q C7HxW7/f7ceZcHFnRoA0nYE= =W6tK -----END PGP SIGNATURE----- Hi
I tried it the way from the script, but I only get the same message saying the following: Starting syslog servicesstartproc: Empty pid file /var/run/syslogd.pid for /sbin/syslogd This is the output for the /bash -x option: vmware:/etc/init.d # ./syslog start + . /etc/sysconfig/syslog ++ KERNEL_LOGLEVEL=1 ++ SYSLOGD_PARAMS=-r ++ KLOGD_PARAMS=-x ++ SYSLOG_DAEMON=syslogd ++ SYSLOG_NG_PARAMS= + BINDIR=/sbin + test -n syslogd + test -x /sbin/syslogd + case "$SYSLOG_DAEMON" in + syslog=syslogd + config=/etc/syslog.conf + params=-r + syslog_pid=/var/run/syslogd.pid + syslog_bin=/sbin/syslogd + klog_bin=/sbin/klogd + syslog_use= + test -s /etc/syslog.conf + test -x /sbin/syslogd + test -x /sbin/klogd + test -s /var/lock/subsys/syslogd + read -t 5 syslog_use + test -z /sbin/syslogd + syslog_use_pid=/var/run/syslogd.pid + case "$(uname -r)" in ++ uname -r + case "$KLOGD_PARAMS" in + . /etc/rc.status ++ LC_ALL=POSIX ++ export LC_ALL ++ test -z '' -o -z '' +++ exec +++ stty size +++ read L C +++ echo LINES=24 COLUMNS=80 ++ eval LINES=24 COLUMNS=80 +++ LINES=24 +++ COLUMNS=80 ++ test 24 -eq 0 ++ test 80 -eq 0 ++ export LINES COLUMNS ++ case ":$PATH:" in ++ test -t 1 -a xterm '!=' raw -a xterm '!=' dumb ++ stty size +++ echo -en '\033' ++ esc=$'\E' ++ extd='' ++ warn='' ++ done='' ++ attn='' +++ echo -en '\017' ++ norm='' +++ echo -en '\015 ' ++ stat=' ' ++ rc_done=' done' ++ rc_running=' running' ++ rc_failed=' failed' ++ rc_missed=' missing' ++ rc_skipped=' skipped' ++ rc_dead=' dead' ++ rc_unused=' unused' ++ rc_unknown=' failed'' ++ rc_reset=''p=' ++ rc_save='' ++ rc_restor'=' ++ _rc_service=./syslog ++ _rc_status=0 ++ _rc_status_all=0 ++ _rc_todo=start ++ test start = status ++ test -n start + rc_reset + _rc_status=0 + _rc_status_all=0 + rc_check + _rc_status_ret=0 + test 0 -eq 0 + test 0 -eq 0 + return + return 0 + case "$1" in + test -e /var/lock/subsys/earlysyslog + test '' = early + test -e /dev/xconsole + killproc -p /var/run/klogd.pid /sbin/klogd + test -s /var/run/syslogd.pid + echo -n 'Starting syslog services' Starting syslog services+ test -z 1 + startproc -p /var/run/syslogd.pid /sbin/syslogd -r startproc: Empty pid file /var/run/syslogd.pid for /sbin/syslogd + rc_status + rc_check + _rc_status_ret=0 + test 0 -eq 0 + test 0 -eq 0 + return + test 0 -gt 7 + _rc_status_ret=0 + case "$_rc_todo" in + local i + return 0 + echo /sbin/syslogd + test 0 -eq 0 + startproc /sbin/klogd -c 1 -x + rc_status + rc_check + _rc_status_ret=0 + test 0 -eq 0 + test 0 -eq 0 + return + test 0 -gt 7 + _rc_status_ret=0 + case "$_rc_todo" in + local i + return 0 + rc_status -v + rc_check + _rc_status_ret=0 + test 0 -eq 0 + test 0 -eq 0 + return + test 0 -gt 7 + _rc_status_ret=0 + case "$_rc_todo" in + local i + for i in '"$@"' + case "$i" in + local vrt= + local out=1 + local opt=en + test -n '' + opt=e + case "$_rc_status" in + vrt=' done' + echo -e '' done done + _rc_status=0 + return 0 + rc_exit + exit 0 vmware:/etc/init.d # I tried installing syslogd on a suse 11, as I was pretty sure I have done this before on a 10.2 and had no problems with this, and I got no problem using suse 11, I even copied the script from this 11 test and I keep getting the same problem, I am suspecting there is something broken on the system, but I can't figure out what it is yet. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-07-07 at 15:52 -0400, Jose wrote:
Carlos E. R. wrote:
Or you could modify the first line of the script to
#!/bin/bash -x
so that it prints the entire lot to the screen when it runs and you can see what happens, hopefully.
Hi
I tried it the way from the script, but I only get the same message saying the following:
Let's see.
Starting syslog servicesstartproc: Empty pid file /var/run/syslogd.pid for /sbin/syslogd
This is the output for the /bash -x option:
vmware:/etc/init.d # ./syslog start
+ killproc -p /var/run/klogd.pid /sbin/klogd + test -s /var/run/syslogd.pid
This test checks if the file exists and is not empty - and it fails, because it is empty. This corresponds to this code: if test -s ${syslog_use_pid} ; then killproc -p ${syslog_use_pid} ${syslog_use} echo -n "Re-" rm -f /var/lock/subsys/syslogd fi So the killproc is not executed,, and the lock file (which exists) is not removed. Then it executes this code: echo -n "Starting syslog services" test -z "$KERNEL_LOGLEVEL" && KERNEL_LOGLEVEL=1 corresponding to this output:
+ echo -n 'Starting syslog services' Starting syslog services+ test -z 1 + startproc -p /var/run/syslogd.pid /sbin/syslogd -r startproc: Empty pid file /var/run/syslogd.pid for /sbin/syslogd
So... you can manually delete that lock file, and see if the script runs. Then stop and start it again, and see if gets stuck again. And then you could write a bugzilla to request suse adds code checking for an empty lock file in there ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIcp6RtTMYHG2NR9URAgNGAKCWAV62S0oVjbs29fYuUPm92R2q9QCgkoZK yMLxmb4CaAiwZrAVb44klJs= =ogjx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2008-07-07 at 15:52 -0400, Jose wrote:
Carlos E. R. wrote:
Or you could modify the first line of the script to
#!/bin/bash -x
so that it prints the entire lot to the screen when it runs and you can see what happens, hopefully.
Hi
I tried it the way from the script, but I only get the same message saying the following:
Let's see.
Starting syslog servicesstartproc: Empty pid file /var/run/syslogd.pid for /sbin/syslogd
This is the output for the /bash -x option:
vmware:/etc/init.d # ./syslog start
+ killproc -p /var/run/klogd.pid /sbin/klogd + test -s /var/run/syslogd.pid
This test checks if the file exists and is not empty - and it fails, because it is empty. This corresponds to this code:
if test -s ${syslog_use_pid} ; then killproc -p ${syslog_use_pid} ${syslog_use} echo -n "Re-" rm -f /var/lock/subsys/syslogd fi
So the killproc is not executed,, and the lock file (which exists) is not removed. Then it executes this code:
echo -n "Starting syslog services" test -z "$KERNEL_LOGLEVEL" && KERNEL_LOGLEVEL=1
corresponding to this output:
+ echo -n 'Starting syslog services' Starting syslog services+ test -z 1 + startproc -p /var/run/syslogd.pid /sbin/syslogd -r startproc: Empty pid file /var/run/syslogd.pid for /sbin/syslogd
So... you can manually delete that lock file, and see if the script runs. Then stop and start it again, and see if gets stuck again.
And then you could write a bugzilla to request suse adds code checking for an empty lock file in there ;-)
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFIcp6RtTMYHG2NR9URAgNGAKCWAV62S0oVjbs29fYuUPm92R2q9QCgkoZK yMLxmb4CaAiwZrAVb44klJs= =ogjx -----END PGP SIGNATURE----- Hi Carlos,
No dice, I tried it and still does not work. 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. Thanks Carlos for your time and help. Jose -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-07-08 at 10:34 -0400, Jose wrote:
No dice, I tried it and still does not work.
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.
Thanks Carlos for your time and help.
Welcome. I suspect that most of the people are using syslog-ng, so defects in the old syslog will go undetected. I sugest you write a bugzilla. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIc7eCtTMYHG2NR9URAtTrAJ93/mUBnxb3R6GkbYch4Xv1ITmc/wCglNTQ sK/W5QpfLNSFQ0fMpRr74GU= =DY5Q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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. If that does the trick, you need to reconfigure the AppArmor profile for syslogd. -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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.
If that does the trick, you need to reconfigure the AppArmor profile for syslogd.
Correct - Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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... -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-07-09 at 10:34 -0400, Jose wrote:
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?
Run yast/AA/wizard something, find what syslog is trying to open and is refused, correct the AA profile so that it allows that operation (and report to bugzilla). Cheesecake :-) Once you know it is AA... I always forget about AA. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIdP+StTMYHG2NR9URAkjzAJ4/PVd/P9Wi+lkcdqQlJWa+baUrXwCfWAnm esqqcWIfS1cLPYBr7B4Ls9o= =SAz0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R.
-
J Sloan
-
Jose
-
Sandy Drobic