Date: Fri, 16 Sep 2005 09:25:55 +1000 From: Norberto Meijome <freebsd@meijome.net> To: freebsd-questions@freebsd.org Cc: Ashley Moran <work@ashleymoran.me.uk> Subject: Re: Trying to colour syslog-ng logs to ttyv7 but won't work after a reboot Message-ID: <432A0303.9000507@meijome.net> In-Reply-To: <4329A1AF.7030602@dial.pipex.com> References: <43298076.7050705@codeweavers.net> <4329921F.2070006@dial.pipex.com> <43299A1B.8050406@ashleymoran.me.uk> <43299CCA.4040509@meijome.net> <4329A1AF.7030602@dial.pipex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Alex Zbyslaw wrote: > Norberto Meijome wrote: > >> Perhaps the ttyv7 isn't properly created until after all the local rc >> scripts are run? That's all I can think. >> >> you may want to edit the syslogng.sh to add some debug lines to see if >> ttyv7 is up @ that point in time. based on the result of this, you may >> want to background (sleep? wait and try again?) the launch of syslogng >> until after the ttyv7 is ready. >> >> or figure out in which order things are started and make sure the >> ttyvs are launched before syslogng > > > Given that anything in /usr/local/etc will start after anything in /etc, > I would really expect a virtual tty to be available. I don't suppose > that syslogng is logging an error anywhere? (Not on ttyv7, obviously :-)) yes, of course. I guess one other thing to do would be to ktrace the actual call to syslogng and figure out what's going on.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?432A0303.9000507>