https://bugzilla.novell.com/show_bug.cgi?id=728774 https://bugzilla.novell.com/show_bug.cgi?id=728774#c38 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #38 from Frederic Crozat <fcrozat@suse.com> 2012-05-29 17:22:54 UTC --- systemd is wrapping all services started (including initscripts) to ensure their input and output / error output are correctly handled (either send to syslog, to stdout / null, etc). I've been able to reduce ntp initscript to a very simple test initscript: #! /bin/sh # ### BEGIN INIT INFO # Provides: foo # Requires-Start: $localfs ### END INIT INFO echo foobar > /dev/stderr exit 0 and it still triggers the error. I'm looking at systemd code to try to understand why the socket setup for handling stderr / stdout isn't used properly. Or it is because it is a socket and not a "standard" file descriptor ? Hints welcome.. -- 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.