From owner-freebsd-current@FreeBSD.ORG Thu Jul 24 16:06:11 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 373FC106564A for ; Thu, 24 Jul 2008 16:06:11 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1CFEA8FC16 for ; Thu, 24 Jul 2008 16:06:10 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id DB91B1A009B1A for ; Thu, 24 Jul 2008 08:33:53 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mw2AdrWbkrie for ; Thu, 24 Jul 2008 08:33:52 -0700 (PDT) Received: from coal (s10.sbo [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 54DCF1A009B07 for ; Thu, 24 Jul 2008 08:33:52 -0700 (PDT) From: Freddie Cash To: current@freebsd.org Date: Thu, 24 Jul 2008 08:33:51 -0700 User-Agent: KMail/1.9.9 References: <200807231846.33728.jhb@freebsd.org> <5f67a8c40807231949i2b2514bbw78dd36cf418cf573@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807240833.51750.fjwcash@gmail.com> Cc: Subject: Re: I like my rc.d boot messages :( X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2008 16:06:11 -0000 On July 23, 2008 08:21 pm Daniel Eischen wrote: > On Wed, 23 Jul 2008, Zaphod Beeblebrox wrote: > > On Wed, Jul 23, 2008 at 9:04 PM, Daniel Eischen > > > > > > wrote: > >> On Wed, 23 Jul 2008, John Baldwin wrote: > >> > >> than 'start'. Am I the only one who finds it useful to know which > >> daemon > >> > >>> is > >>> making my startup hang for an extra second? > >> > >> No, you are not. I too would like that. > > > > I'd go further: it was nice when startup scripts printed their name > > (no newline) and then '.\n' when they were finished. It then becomes > > unambiguous who is at fault. It's hard to tell with the current > > non-system which of the 2 scrpts (the one that has printed it's name, > > or the one that next prints it's name) is at fault. Worse.. it could > > be the quiet script in between. > > Agreed, but you could delineate it with something other than '\n" too. > Like '[amd] [smtp] [dhcpd] ...', with the ']' meaning the script is > done and has moved on to the next service. I like that. [ means processing has started, name is the service/script runnging, ] means processing of that script has completed. All the info you need for multiple services, all on one line. -- Freddie Cash fjwcash@gmail.com