cvs commit: src/usr.sbin/syslogd syslogd.c

[Garance A Drosehn]

At 11:06 PM +0100 3/30/06, Joao Barros wrote:
>On 3/30/06, John-Mark Gurney <gurney_j at resnet.uoregon.edu> wrote:
>  > I'd be cool if there was a log entry that logged the fact
>  > that we couldn't write entries for a time due to no space
>  > on the device, so that going back through the logs, you
>  > could understand why there was a big gap...
>
>I like the idea , and for those of us that get paranoid with
>logs 2 lines like this would really be nice:
>
>- Logging stopped at 2006-03-29 8:00:01 due to lack of disk space.
>- Logging resumed at 2006-03-29 23:00:01
>
>Of course the 2nd line has an automatic timestamp but it would
>be really nice to know when logging started to fail.
>
>note: the examples were just to show the idea not the format.

Include a count of the lines which were not logged.  Eg:

Logging resumed at 2006-03-29 23:00:01, but 1200 lines were not logged

-- 
Garance Alistair Drosehn     =      gad at gilead.netel.rpi.edu
Senior Systems Programmer               or   gad at FreeBSD.org
Rensselaer Polytechnic Institute;             Troy, NY;  USA