Christian Boltz wrote:
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
thankx, your fix is working all right. my logging has been restored now. the only questions is, what else on/with /var has been damaged or disabled during my 10.2 - 10.3 upgrade? kde while dragging icons to the menus, and the kde helptext seems to be trashed also. is there actually a way to reinstall (forced?) all packages, so all scripts and actions are being done again and all files are being written to the filesystems once again to be sure that everything exists, and every step/script has been executed correctly? during my second upgrade over the first trashed 10.2 one, only two more packages were being installed and the upgrade was finished after that pretty quickly. any hints on how to check if all packages work correctly? maybe with some rpm commandline parameters or something? thanks. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org