From: Henrik Heil <hhml@zweipol.net>
Subject: Re: svlogd -tt
Date: Mon, 26 Jul 2004 20:39:39 +0200 [thread overview]
Message-ID: <41054FEB.2090305@zweipol.net> (raw)
In-Reply-To: <20040723102024.28233.qmail@67ec0c2e018e31.315fe32.mid.smarden.org>
>>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.
Thinking about these alternatives i must admit that both seem to have a
drawback -- and that i underestimated the complexity of switching the
formats.
Different sets (if i understood that right) means that it is not
intuitive what the maximum number of old log files from the config
means. It cannot mean num=TAI+UTC because in this case svlogd could not
rotate if the log directory would contain num logfiles of the other
format. If it means num*TAI + num*UTF the straightforward method to
calculate the maximum size of the log directory no longer works and
changing the format without moving the old files leads to a log
directory that occupies twice the disk space.
With filename conversion i am not shure if you mean renaming the
existing logfiles or properly calculating the oldest file from both
formats before deleting it. Unfortunatly i have no idea how complex any
of these two would be -- probably it's not worth the effort.
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 guess this would require a small patch and almost no overhead when
rotating the logfiles. I think there is nothing to gain by leaving the
old files in the log directory when switching the format.
Best regards,
Henrik
--
Henrik Heil, zweipol Coy & Heil GbR
http://www.zweipol.net/
next prev parent reply other threads:[~2004-07-26 18:39 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 [this message]
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=41054FEB.2090305@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).