From owner-freebsd-stable@FreeBSD.ORG Thu Sep 17 08:59:02 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06C0A106568D; Thu, 17 Sep 2009 08:59:02 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id C45F58FC15; Thu, 17 Sep 2009 08:59:01 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:9506:2436:ded6:e32f] (unknown [IPv6:2001:7b8:3a7:0:9506:2436:ded6:e32f]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 3723E5C59; Thu, 17 Sep 2009 10:59:00 +0200 (CEST) Message-ID: <4AB1FA57.5090502@andric.com> Date: Thu, 17 Sep 2009 10:59:03 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.4pre) Gecko/20090914 Shredder/3.0b4pre MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG, dougb@FreeBSD.ORG References: <200909170717.n8H7HDe4081801@lurza.secnetix.de> In-Reply-To: <200909170717.n8H7HDe4081801@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: 8.0 rc.d scripts less verbose? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 08:59:02 -0000 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. :)