[systemd-devel] [PATCH] allow explicit stdout/stderr configuration for SysV services
Lennart Poettering
lennart at poettering.net
Mon Feb 28 13:32:03 PST 2011
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?
if we merge this, is SysVConsole still useful then? Shouldn't we kill
that then?
Lennart
--
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel
mailing list