Hello, on Donnerstag, 4. Oktober 2007, ab wrote:
ab wrote:
only the syslogd gets defunct :(
lsof on my hosed 10.3 production system gives me this after rcsyslog start: [nearly nothing]
I can reproduce the problem here and also have a solution, see below.
i also have tried to reinstall syslogng, syslogd and klogd packages via yast, enforce to install/reinstall the packages. also using fresh /etc/syslog-ng/syslog-ng.conf. but to no avail.
Please don't confuse syslogd (config file: /etc/syslog.conf) and syslog-ng (config file: /etc/syslog-ng/syslog-ng.conf)
my 10.3 system doesnt log any more :(
do i need to upgrade-install 10.3 once again over this messed up system? maybe that would help. or do i need to cleaninstall and move my data to the fresh system?
This bug has nothing to do with your upgrade problems. It's a bug in the syslogd apparmor profile. It seems noone tested with syslogd because syslog-ng is default since some releases. Syslogd wants to lock its pid file, which needs the extra "k" (loc_k_) permission in the latest apparmor version. Fix: Edit /etc/apparmor.d/sbin.syslogd and change /var/run/syslogd.pid lrw, to /var/run/syslogd.pid klrw, and run rcapparmor reload I just entered this in bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=331444 Regards, Christian Boltz -- printk("; corrupted filesystem mounted read/write - your computer will explode within 20 seconds ... but you wanted it so!\n"); [/usr/src/linux/fs/hpfs/super.c] -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org