Date: Thu, 17 Sep 2009 10:59:03 +0200 From: Dimitry Andric <dimitry@andric.com> To: freebsd-stable@FreeBSD.ORG, dougb@FreeBSD.ORG Subject: Re: 8.0 rc.d scripts less verbose? Message-ID: <4AB1FA57.5090502@andric.com> In-Reply-To: <200909170717.n8H7HDe4081801@lurza.secnetix.de> References: <200909170717.n8H7HDe4081801@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2009-09-17 09:17, Oliver Fromme wrote:
> My feeling is that hiding all of the "starting" messages
> is a regression that needs to be fixed. I cannot think
> of a good reason why they should be hidden, but there
> are certainly good reasons to display them.
The commit that introduced this, r179946, has this log message:
====
Move the diagnostic output when the rc.subr(8) glue automatically starts a
service behind $rc_quiet. Instead, output a warning if the pre-command
routine or the command itself failed. Arguably, it's more useful to know when
a command failed to start than it is to have an endless list of
"Starting ...." lines[1].
[1] - This change actually helped me to discover a bug in rc.d/{lockd,statd}
(fixed in r179941) that used to fail silently before.
====
It is really a matter of taste, I guess. There is something to be said
for eliminating verbosity, in order to make real errors more visible.
On the other hand, if one of your startup rc scripts hangs (for whatever
reason), it is nice to have an approximate idea which one it is. :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AB1FA57.5090502>