From owner-freebsd-current@FreeBSD.ORG Mon Jul 28 18:20:17 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 31768106564A for ; Mon, 28 Jul 2008 18:20:17 +0000 (UTC) (envelope-from jandrese@mitre.org) Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by mx1.freebsd.org (Postfix) with ESMTP id 72DC08FC15 for ; Mon, 28 Jul 2008 18:20:16 +0000 (UTC) (envelope-from jandrese@mitre.org) Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m6SFcqq6025943 for ; Mon, 28 Jul 2008 11:38:52 -0400 Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m6SFcqiL025902; Mon, 28 Jul 2008 11:38:52 -0400 Received: from IMCSRV6.MITRE.ORG ([129.83.20.237]) by imcfe2.MITRE.ORG with Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 Jul 2008 11:38:51 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 28 Jul 2008 11:38:28 -0400 Message-ID: <53B52415C756A84E8A169F0E3673A329011E9D9A@IMCSRV6.MITRE.ORG> In-Reply-To: <200807251402.00871.joao@matik.com.br> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: I like my rc.d boot messages :( Thread-Index: AcjueD0muBJrQgzKSNyR04Y4fuuyBQCT3jsw References: <200807231846.33728.jhb@freebsd.org><200807241448.30627.joao@matik.com.br> <4888D859.3090809@quip.cz> <200807251402.00871.joao@matik.com.br> From: "Andresen, Jason R." To: "JoaoBR" , X-OriginalArrivalTime: 28 Jul 2008 15:38:51.0830 (UTC) FILETIME=[092F9D60:01C8F0C8] 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: Mon, 28 Jul 2008 18:20:17 -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 :) > for me it would be something like: > > starting $service_name ... up > starting $service_name ... failed > starting $service_name ... up > Personally, I'd like a mix between your above suggestion and the current method: Starting Services: sshd...ok, httpd...ok, ftpd...failed