From owner-freebsd-questions@FreeBSD.ORG Thu Sep 15 15:59:23 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E62816A41F for ; Thu, 15 Sep 2005 15:59:23 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: from mta08-winn.ispmail.ntl.com (mta08-winn.ispmail.ntl.com [81.103.221.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id B22B043D45 for ; Thu, 15 Sep 2005 15:59:22 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: from aamta09-winn.ispmail.ntl.com ([81.103.221.35]) by mta08-winn.ispmail.ntl.com with ESMTP id <20050915155921.TUFD10357.mta08-winn.ispmail.ntl.com@aamta09-winn.ispmail.ntl.com> for ; Thu, 15 Sep 2005 16:59:21 +0100 Received: from jigsaw-sbs02.jigsawhq.com ([213.106.224.113]) by aamta09-winn.ispmail.ntl.com with ESMTP id <20050915155921.JCJR18235.aamta09-winn.ispmail.ntl.com@jigsaw-sbs02.jigsawhq.com> for ; Thu, 15 Sep 2005 16:59:21 +0100 X-Filtered-With-Copfilter: Version 0.1.0beta11 (ProxSMTP 1.2.1) X-Copfilter-Virus-Scanned: ClamAV 0.86.2/1082 - Wed Sep 14 16:22:17 2005 X-Copfilter: Client is part of our network, skipped SpamAssassin Received: from [192.168.0.181] ([192.168.0.181]) by jigsaw-sbs02.jigsawhq.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 15 Sep 2005 16:58:20 +0100 Message-ID: <43299A1B.8050406@ashleymoran.me.uk> Date: Thu, 15 Sep 2005 16:58:19 +0100 From: Ashley Moran User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alex Zbyslaw References: <43298076.7050705@codeweavers.net> <4329921F.2070006@dial.pipex.com> In-Reply-To: <4329921F.2070006@dial.pipex.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Sep 2005 15:58:20.0433 (UTC) FILETIME=[4B3A0810:01C5BA0E] Cc: freebsd-questions@freebsd.org Subject: Re: Trying to colour syslog-ng logs to ttyv7 but won't work after a reboot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 15:59:23 -0000 Alex Zbyslaw wrote: > The requirements like BEFORE: SERVERS are not honoured by scripts in > /usr/local/etc/rc.d. Try placing the script in /etc/rc.d calling it say > syslogng (i.e. without the .sh). The BEFORE: doesn't bother me too much. I don't care enormously if I lose a bit of logging. I just put it in to match syslogd's setup. > > man rc has more info, as would scanning back through the freebsd-rc > archives. I believe that work to make scripts in /usr/local/etc/rc.d > work more like system scripts will appear sometime in 6.X, though full > integration is, I believe, not expected until 7.X. I've only got a partial handle on the rc process. A lot of it is black magic to me! (aside: I thought Apple's launchd was pencilled in for at least FreeBSD 7 - which would render rc obsolete.) > > Right now, your syslogng will be being started *after* lots of servers > that might expect to talk to it. I assume you put syslogng_enable="YES" > into /etc/rc.conf? as well as syslogd_enable="NO". (Or, it might work > just to change syslogd_program="/path/to/syslogngd" and not bother with > changing anything else). Yes, syslog-ng is running fine (I'd already configured rc.conf like you say). The problem is that it has a destination set up to pipe to the program ccze, and that pipe doesn't work unless I restart syslog-ng after boot time. I've also tried moving the script into /etc/rc.d and renaming it syslogng. After removing the devfs requirement it boots ok, but still requires a syslog-ng restart. Perhaps the ttyv7 isn't properly created until after all the local rc scripts are run? That's all I can think. I can live with it how it is but it's frustrating that this little thing won't work! I've become obsessed with my logs... I want every machine logged centrally, scanned, summarized and e-mailed on significant events. And our network administrator wants them colour-coded and on display at the back of the office. Perhaps the real problem isn't technical! Thanks for your thoughts anyway. Ashley