https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c0 Summary: syslog-service causes issues with the latest systemd (100% cpu hogging due to service failure) Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: tittiatcoke@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1308.0 Safari/537.17 SUSE/24.0.1308.0 I updated during the weekend to the latest factory. It came with the latest systemd and I noticed that certain packages no longer were working due to changed directories. One of them was the syslog-service, which puts everything in /lib/systemd instead of /usr/lib/systemd. This was easy to fix, but then the bigger issue started that with either rsyslog or syslog-ng, the syslogger was not started and that systemd was indicating that the service was failing due to start limitations (started too many times in a too short period). Due to the cpu's are heavily utilized up to 100% and the system becomes unusable. I then validated the service-file that was created by syslog-service and made it to work with rsyslog. I did this by removing certain lines from the /run/systemd/syslog.core file (from within the syslog-system-generator). I can of course submit those changes, but for me I can not understand why this package syslog-service was created in the first place ? Why do we need another automatic selection logic, if the packages are anyway mutual exclusive. We can not install rsyslog, without remove syslog-ng, etc. The service that is required for rsyslog to start, is not compatible with the way that syslog-ng should be started. Wouldn't life be much simpler if each system logger would provide its own service file to work with systemd ?? From what I have seen is that both rsyslog and syslog-ng are already providing those service files, but that they are just removed from within the spec-file ?? People are not left without syslog due to some strange construction to make thing even more generic. Please let me know if this is indeed the way that openSUSE will work with the syslog, or that I can submit a new version of rsyslog and syslog-ng that will provide their own systemd service files ? Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.