From: Henrik Heil <hhml@zweipol.net>
Subject: Re: svlogd -tt
Date: Tue, 27 Jul 2004 14:31:34 +0200 [thread overview]
Message-ID: <41064B26.3050504@zweipol.net> (raw)
In-Reply-To: <20040727112809.10300.qmail@84ce64a3ba6fa7.315fe32.mid.smarden.org>
Gerrit Pape wrote:
> But I'm not convinced that it's worth the trouble to implement this or
agreed.
> similar. There still is the idea of a log processor program (svlogp)
> which could be also used to list the log files in a directory with human
> readable names, or gives convenient access to the logs by other means.
I see -- this would be the cleanest solution.
I thought the UTC-filenames would be quite trivial to implement because
the timestamps already exist for use with the -tt option but i didn't
look at the consequences for the log directory.
My C programming skills are quite limited -- but i can offer to test
early versions of svlogp if you decide to work on it.
>>What do you think about a runtime option for UTC-filenames that only
>>comes into effect if there are no TAI-filenames in the log directory and
>>vice versa?
>
> I'm not sure; svlogd at least should print a warning in this case, which
> then ends up in the readproctitle log. It's not that intuitive to
> users, and susceptible to misunderstandings in my opinion.
true -- was not a good idea.
Best regards,
Henrik
--
Henrik Heil, zweipol Coy & Heil GbR
http://www.zweipol.net/
next prev parent reply other threads:[~2004-07-27 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 19:00 Henrik Heil
2004-07-23 10:20 ` Gerrit Pape
2004-07-23 10:30 ` Ian Stokes-Rees
2004-07-26 18:39 ` Henrik Heil
2004-07-27 11:28 ` Gerrit Pape
2004-07-27 12:31 ` Henrik Heil [this message]
2004-07-28 23:02 ` Alex Efros
2004-07-29 10:12 ` Henrik Heil
2004-07-29 11:12 ` Alex Efros
2004-07-29 13:07 ` Henrik Heil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41064B26.3050504@zweipol.net \
--to=hhml@zweipol.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).