From owner-freebsd-current@FreeBSD.ORG Thu Jul 24 18:17:44 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E1E01065671 for ; Thu, 24 Jul 2008 18:17:44 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 13D968FC0A for ; Thu, 24 Jul 2008 18:17:43 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from anb.p.matik.com.br (anb.p.matik.com.br [200.152.83.34] (may be forged)) by msrv.matik.com.br (8.14.2/8.14.2) with ESMTP id m6OHmh5w096319 for ; Thu, 24 Jul 2008 14:48:43 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-current@freebsd.org Date: Thu, 24 Jul 2008 14:48:30 -0300 User-Agent: KMail/1.9.7 References: <200807231846.33728.jhb@freebsd.org> <200807240833.51750.fjwcash@gmail.com> In-Reply-To: <200807240833.51750.fjwcash@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200807241448.30627.joao@matik.com.br> X-Virus-Scanned: ClamAV 0.93.1/7815/Thu Jul 24 12:09:44 2008 on msrv.matik.com.br X-Virus-Status: Clean 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 18:17:44 -0000 On Thursday 24 July 2008 12:33:51 Freddie Cash wrote: > 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. simply another wiered outcome - not understandable btw same as this mystica= l=20 dot thing=20 something more obvious would be: starting $service_name ... up starting $service_name ... up =2E.. that would be something clear, specially for whom did not invented it =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br