Re: CLOG support in syslogd

[Scott Ullrich <sullrich@xxxxxxxxx>]

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



On Fri, 29 Oct 2004 09:21:12 -0700 (PDT), Matthew Dillon
<dillon@xxxxxxxxxxxxxxxxxxxx> wrote:
>     I don't really like the circular log file mechanism.  It's basically a
>     binary coding of a log file which sounds like a horrible idea.  A
>     far better solution is to simply bounce between N log files.
> 
>                                                 -Matt
> 


-- 

-Scott