[EMAIL PROTECTED] <[EMAIL PROTECTED]> writes on 31 July 2000 at 10:50:23 -0700
 > On Mon, Jul 31, 2000 at 12:23:38PM -0500, David Dyer-Bennet wrote:
 > > Charles Cazabon <[EMAIL PROTECTED]> writes on 31 July 2000 at 11:20:48 
 >-0600
 > >  > David Dyer-Bennet <[EMAIL PROTECTED]> wrote:
 > >  > >  > 
 > >  > >  > Really? If I want to tail a log file, eg, I go like this:
 > >  > >  > 
 > >  > >  > tail ../someservice/current | tai64nlocal
 > >  > >  > 
 > >  > >  > and it all looks fine for humans.
 > >  >  
 > >  > > Yeah, it works fine for people who check log files by tailing them.  I
 > >  > > check them by bringing them into an emacs buffer, so the funny
 > >  > > timestamps make them darned near useless.
 > >  > 
 > >  > So why not tail them to a temp file and use emacs to view the temp file?
 > >  > Or write an emacs-lisp function to convert the timestamps.
 > > 
 > > If I'm going to go to effort to make it work the way I want, I think
 > > I'll just change multilog to use a sensible format.  It's silly having
 > > archival log files sitting there that don't mean anything without a
 > > conversion program; straight text is the appropriate format for log
 > > files. 
 > 
 > But it *is* straight text. The point about tai is that it's entirely
 > appropriate for log files that may live for a long time. Have you
 > read the rationale for tai at all?

Yes, when I first looked at it.  As is often the case with Dan, I just
disagree.  It's not straight text in the sense I mean; it's not human
readable.  Of all the strange choices Dan's made that I've encountered
in working with qmail, this is the first one that I fail completely to
understand.  All the others, I see the tradeoffs and I see why he
chose as he did, even if I might have chosen otherwise.  This one
makes zero sense.  It's non-functional.  It doesn't connect to the way
I work. 
-- 
Photos: http://dd-b.lighthunters.net/ Minicon: http://www.mnstf.org/minicon
Bookworms: http://ouroboros.demesne.com/ SF: http://www.dd-b.net/dd-b 
David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]

Reply via email to