[Tfug] Etch log files

[eric christian]

>
> Date: Tue, 24 Jun 2008 15:16:40 -0700
> From: John Gruenenfelder <johng at as.arizona.edu>
> Subject: Re: [Tfug] Etch log files
> To: Tucson Free Unix Group <tfug at tfug.org>
> Message-ID: <20080624221640.GA28469 at as.arizona.edu>
> Content-Type: text/plain; charset=us-ascii
>
> On Tue, Jun 24, 2008 at 02:50:36PM -0700, TR wrote:
>   
>> >To view the boot messages use
>> >$> dmesg
>>     
>
> Unfortunately, dmesg only outputs messages from the kernel.  The message Eric
> is asking about is coming from an init script.
>
> For some reason which I cannot fathom, logging of init script output is not
> enabled by default.  On Debian, edit the /etc/default/bootlogd file to enable
> boot logging.  The result is stored in, I think, /var/log/boot.
>
>   
This did the trick in this case. I suppose trying to manage total linux 
logging (system, demons, shells, apps etc) is like trying to manage a 
herd of cats (or dachshunds). I am looking at logfile  viewers - swatch, 
vigilog etc. I installed one which ran as a demon and i couldn't figure 
it out.
Eric