[Bug 696963] New: systemd does not start syslog
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c0 Summary: systemd does not start syslog Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: mt@novell.com ReportedBy: aj@novell.com QAContact: qa@suse.de CC: kasievers@novell.com Blocks: 696902 Found By: --- Blocker: --- Currently systemd does not start syslog at all. This might be a fallout from removing the syslog.service file from the syslog package. I have to start syslog manually and then it runs fine... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c1
--- Comment #1 from Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c2
Bruno Friedmann
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c3
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c4
--- Comment #4 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c5
--- Comment #5 from Kay Sievers
which one is the best to use and to be push as default/recommanded ?
For now it's rsyslog, which is actively tested and supported from upstream. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c6
--- Comment #6 from Kay Sievers
(In reply to comment #2)
Most enterprise users want to have the choice between all three sysloggers and the openSUSE is the base of all enterprise products.
Sure, if the syslog implementation supports systemd, it can be enabled/disabled with systemctl commands. No magic needed here, it will work just fine, like everything else on the system.
Next is that systemd should not abuse the kernel kprintf logging buffer but use its own logging ring buffer.
"Abuse' is your personal opinion, which the systemd developers don't share. We have quite to opposite feedback on this feature from many people involved in this decision. Early-boot messages are mixed with the kernel messages, in 'dmesg' and that's exactly what you want to look at if things go wrong. These days it does not matter at all if boot/init components run in user- or kernel-space, hence they should log to the same target during early boot, until a real syslog is available. Laptop- and embedded-like setups do not need to run any syslog service at all, but they still have a fully working 'syslog' from the kernel. It's just that nothing is ever written to disk. Rsyslog can distinguish the userspace messages from the kernel messages just fine, and can even write them to different log files. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c7
--- Comment #7 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c8
--- Comment #8 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c9
--- Comment #9 from Kay Sievers
(In reply to comment #6)
With this approach you're not able to report all kernel and system messages send to /dev/console to all console devices. This is IMHO required for all systems using e.g. a serial console together with an other console
We should not try to make userspace 'smarter' than the kernel with its log messages? We must avoid handling early-boot messages from the kernel differently than the ones from early boot tools. Today it is just an irrelevant detail if an early-boot tool runs in kernel- or userspace. The only visible difference should be the facility value of the syslog prefix. I does not make much sense to have early-boot and kernel bootup-messages separate. These messages belong together during the time the system is brought up. The messages the kernel sends out need to show up the same way, and on all the same devices. So if there is anything missing, please let's change the kernel, and not work around it in userspace without being able to provide a complete solution to the problem. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c10
Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c
Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c12
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c13
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c14
--- Comment #14 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c15
Dr. Werner Fink
participants (1)
-
bugzilla_noreply@novell.com