From owner-freebsd-current@FreeBSD.ORG Fri Jul 25 17:02:18 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 2032D1065671 for ; Fri, 25 Jul 2008 17:02:18 +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 9564E8FC08 for ; Fri, 25 Jul 2008 17:02:17 +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 m6PH2EWd032947; Fri, 25 Jul 2008 14:02:14 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-current@freebsd.org Date: Fri, 25 Jul 2008 14:02:00 -0300 User-Agent: KMail/1.9.7 References: <200807231846.33728.jhb@freebsd.org> <200807241448.30627.joao@matik.com.br> <4888D859.3090809@quip.cz> In-Reply-To: <4888D859.3090809@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200807251402.00871.joao@matik.com.br> X-Virus-Scanned: ClamAV 0.93.1/7826/Fri Jul 25 09:51:06 2008 on msrv.matik.com.br X-Virus-Status: Clean Cc: Miroslav Lachman <000.fbsd@quip.cz> 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: Fri, 25 Jul 2008 17:02:18 -0000 On Thursday 24 July 2008 16:30:33 Miroslav Lachman wrote: > JoaoBR wrote: > > [...] > > >>>>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 > > mystical dot thing > > > > something more obvious would be: > > > > starting $service_name ... up > > starting $service_name ... up > > ... > > > > that would be something clear, specially for whom did not invented it > > It seems too verbose. (does anybody expect "stoping" service on system > boot?) And each service on separate line seems to me like vaste of space. > Line like "[ssh] [smtp] [dhcpd] [mysql]" is enough for me. > It is easy to document it in handbook and man pages. > > Just my 0.02 > well, the obvious often is'nt :)=20 for me it would be something like: starting $service_name ... up starting $service_name ... failed starting $service_name ... up what waste of space? running lines not buffered but in dmesg.*=20 anyway the waste of space is it worse as price for clearness and as I said before what is clear for the inventor or for you and me is on= e=20 thing but when you're supporting a remote server which is not coming up and= =20 a "not-knowing-the-secret" person eventual in another language (not english= =20 speaking) needs to say it ... well, then my friend, when this happens to yo= u=20 then you will remember this thread and will bite your ass for not having=20 agreed ... :) =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