Date: Thu, 30 Mar 2006 23:06:43 +0100 From: "Joao Barros" <joao.barros@gmail.com> To: "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: <70e8236f0603301406p263b244fy80a115cca685d37f@mail.gmail.com> In-Reply-To: <20060330214216.GC86967@funkthat.com> References: <200603302104.k2UL4qF7086165@repoman.freebsd.org> <20060330214216.GC86967@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 bac= k > 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. -- Joao Barros
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?70e8236f0603301406p263b244fy80a115cca685d37f>