Date: Mon, 14 Jun 2004 13:56:51 -0400 From: Garance A Drosehn <gad@FreeBSD.org> To: Brad Knowles <brad.knowles@skynet.be> Cc: freebsd-current@FreeBSD.org Subject: Re: Minor HEADSUP - "New order" for newsyslog Message-ID: <p06020478bcf390d496d0@[128.113.24.47]> In-Reply-To: <p06002040bcf30b69998f@[10.0.1.3]> References: <p06020462bcf0fce1e891@[128.113.24.47]> <p06020464bcf116ef03f1@[128.113.24.47]> <200406131256.25362.wes@softweyr.com> <p06020472bcf2745be9f1@[128.113.24.47]> <p06020475bcf287766437@[128.113.24.47]> <p06002040bcf30b69998f@[10.0.1.3]>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:00 AM +0200 6/14/04, Brad Knowles wrote: >At 6:41 PM -0400 2004-06-13, Garance A Drosehn wrote: > >> So, maybe something like "log.t2004f14a" instead of "log.0". >> I could obviously spell out the time more, but that would >> be an even longer suffix... > > Could this be a configuration option? For maximum >compression, maybe base64 the ctime, but for maximum >readability use YYYY-MM-DD? Several people have mentioned alternate formats that they would like to see, so I plan to have some flexibility in the format. Since I have not implemented it yet, I cannot say just how flexible it might be... :-) Note that my original example is not base64 of the ctime. It is "base26" (using just the alphabet) for the month and the hour, but standard decimal for the year and the day. So, it is still somewhat readable once you get used to it. But I do intend to support some alternate formats. -- 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?p06020478bcf390d496d0>