> Do others have any thoughts on this matter?
Rather than null, why not just send to an empty tty which a user can
optionally switch to.
--
___
'Write programs that do one thing and do it well. Write programs to work
together.
>
> Do others have any thoughts on this matter?
>
I like to know whats going on. Output in some form is always welcome,
although errors should stand out and be obvious.
--
Yesterday is history.
Tomorrow is a mystery.
Today is a gift.
That's why its called the present.
Headmaster Squall :: Th
On Fri, 14 Sep 2012 00:10:54 +0200
Sébastien Luttringer wrote:
> > However, the issue is more general, and I'm
> > unsure whether I should continue posting such bugs.
> Systemd will probably remove all this *bad* but convenient hiding.
> I reminds you, this is to have a clean boot when everyth
On Thu, Sep 13, 2012 at 9:58 PM, Jacob Joseph wrote:
> Some underlying programs produce no output; I'm not proposing that
> Arch address all such cases. Instead, the scenario I continue to run
> into is that the init script redirects all output, good or bad, to
> /dev/null. In my opinion, this i
Hi.
A recurring source of frustration for my use of Arch Linux is
that many init scripts fail to produce any output, to either the
console or syslog, when something goes wrong and the script
fails. The particular cause is always case-dependent (usually
stemming from some config error).
Some unde
5 matches
Mail list logo