Re: CLOG support in syslogd

[Scott Ullrich <sullrich@xxxxxxxxx>]

The reason is that there is very little memory on this emedded device
and the CLOG format prevents the log file from ever growing over X
size (whereas X is definable).  This is basically a 64 meg 133
megahertz device with a 64 meg compact flash card.  Basically the logs
are stored in a memory disk.

-- 

-Scott


On Fri, 29 Oct 2004 09:30:31 -0700 (PDT), Matthew Dillon
<dillon@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> :
> :When I cat a log file that is using a circular log format it appears
> :as clear text.  Here's an example:
> :
> :$ cat /var/log/system.log
> :Oct 28 23:18:58 m0n0wall /kernel: Waiting (max 60 seconds) for system
> :process `vnlru' to stop...stopped
> :Oct 28 23:18:58 m0n0wall /kernel: Waiting (max 60 seconds) for system
> :process `bufdaemon' to stop...stopped
> :Oct 28 23:18:58 m0n0wall /kernel: Waiting (max 60 seconds) for system
> :process `syncer' to stop...stopped
> :Oct 28 23:18:58 m0n0wall /kernel:
> :Oct 28 23:18:58 m0n0wall /kernel: syncing disks...
> :Oct 28 23:18:58 m0n0wall /kernel: done
> :Oct 28 23:18:58 m0n0wall /kernel: Uptime: 1d3h35m0s
> :
> :There is a tiny portion at the very end of the file (less than 10
> :byes) that appear binary but the rest is pure text.
> :
> :Scott
> 
>     And when it circules back to the beginning the time stamps will be
>     out of order.  Again, why not simply flip between two log files?  Why
>     does the log file have to be made circular?  It just doesn't make any
>     sense to me.
> 
>                                                 -Matt
>