Date: Thu, 30 Mar 2006 17:16:23 -0500 From: Garance A Drosehn <gad@FreeBSD.org> To: "Joao Barros" <joao.barros@gmail.com>, "John-Mark Gurney" <gurney_j@resnet.uoregon.edu> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, "Christian S.J. Peron" <csjp@FreeBSD.org>, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.c Message-ID: <p06230922c05208b9a352@[128.113.24.47]> In-Reply-To: <70e8236f0603301406p263b244fy80a115cca685d37f@mail.gmail.com> References: <200603302104.k2UL4qF7086165@repoman.freebsd.org> <20060330214216.GC86967@funkthat.com> <70e8236f0603301406p263b244fy80a115cca685d37f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:06 PM +0100 3/30/06, Joao Barros wrote: >On 3/30/06, John-Mark Gurney <gurney_j@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@gilead.netel.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06230922c05208b9a352>