[systemd-devel] [PATCH] allow explicit stdout/stderr configuration for SysV services

Andrey Borzenkov arvidjaar at gmail.com
Tue Mar 1 00:04:06 PST 2011

On Tue, Mar 1, 2011 at 12:32 AM, Lennart Poettering
<lennart at poettering.net> wrote:
> On Sun, 27.02.11 01:05, Andrey Borzenkov (arvidjaar at gmail.com) wrote:
>> Currently it is possible to either output legacy initscripts on
>> console which often messes it up completely, or suppress output
>> alltogether which makes it hard to debug boot issues.
>> While DefaultStandardOutput could be used to force syslog, it will
>> affect *all* services, also those that set stdin to tty and rely
>> on inheriting it. So make it possible for SysV to explicitly control
>> output.
> Hmm, how would you use this? Send SysV stdout to /dev/null, but SysV
> stderr to the console? Is this really advisable? i.e. are you sure that
> if current init scripts encounter an error they properly write warnings
> to stderr, instead of just echoing them to stdout?

I do not really need SysVStandardError, it was just monkey job, you
know :) copy'n'paste from DefaultStandardOutput/Error

> if we merge this, is SysVConsole still useful then? Shouldn't we kill
> that then?

Yes, I expected it :)

Revised patch attached. I removed handling of "quiet" for SysV
because, personally, the main point of this patch is to redirect
initscripts output to stable storage (syslog) and it is already quiet
enough for me.

This also corrects a DefaultStandardOutput/Error descriptions in a
couple of places.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sysv_std_output.patch
Type: text/x-patch
Size: 16932 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20110301/0092defb/attachment.bin>

More information about the systemd-devel mailing list