From: Ian Stokes-Rees <i.stokes-rees1@physics.ox.ac.uk>
Cc: supervision@list.skarnet.org
Subject: Re: svlogd -tt
Date: Fri, 23 Jul 2004 12:30:31 +0200 [thread overview]
Message-ID: <4100E8C7.2060102@physics.ox.ac.uk> (raw)
In-Reply-To: <20040723102024.28233.qmail@67ec0c2e018e31.315fe32.mid.smarden.org>
Ian.
It is a bit hard to see at a glance what the file names mean for log
files. Maybe a sym link to the existing files with the sym link having
a more descriptive name?
Ian
Gerrit Pape wrote:
> On Tue, Jul 20, 2004 at 09:00:06PM +0200, Henrik Heil wrote:
>
>>i read the thread about the svlogd -t switches some weeks ago and though
>> i am using -tt (UTC) happily i am missing the feature to have the
>>rotated logfiles with UTC-names instead of @TAI-names.
>>
>>Is there a drawback to make this an option?
>>The order of the logfiles would be preserved, selecting logfiles with
>>wildcards would be easy.
>>
>>I cannot comment on pro/contra TAI itsself but i think one who decides
>>not to have TAI-timestamps in the logfiles would prefer UTC-filenames
>>for the rotated files too.
>>
>>What do you think?
>
>
> When making it a runtime option, there must be a decision whether svlogd
> shall maintain two different sets of files in the log directory, or
> filename conversion should be done.
>
> I'm not eager to add this option to svlogd, but would be interested in
> the opinion of other people, and maybe a patch, though.
>
> Regards, Gerrit.
--
Ian Stokes-Rees i.stokes-rees1@physics.ox.ac.uk
Particle Physics, Oxford http://www-pnp.physics.ox.ac.uk/~stokes
next prev parent reply other threads:[~2004-07-23 10:30 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 [this message]
2004-07-26 18:39 ` Henrik Heil
2004-07-27 11:28 ` Gerrit Pape
2004-07-27 12:31 ` Henrik Heil
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=4100E8C7.2060102@physics.ox.ac.uk \
--to=i.stokes-rees1@physics.ox.ac.uk \
--cc=supervision@list.skarnet.org \
/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).