Date: Wed, 23 Jul 2008 23:21:16 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Zaphod Beeblebrox <zbeeble@gmail.com> Cc: current@freebsd.org Subject: Re: I like my rc.d boot messages :( Message-ID: <Pine.GSO.4.64.0807232317150.15288@sea.ntplx.net> In-Reply-To: <5f67a8c40807231949i2b2514bbw78dd36cf418cf573@mail.gmail.com> References: <200807231846.33728.jhb@freebsd.org> <Pine.GSO.4.64.0807232104160.15288@sea.ntplx.net> <5f67a8c40807231949i2b2514bbw78dd36cf418cf573@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Jul 2008, Zaphod Beeblebrox wrote: > On Wed, Jul 23, 2008 at 9:04 PM, Daniel Eischen <deischen@freebsd.org> > 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. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0807232317150.15288>