Re: svlogd -tt

[Henrik Heil <hhml@zweipol.net>]

>>I know that i can use the mtime to select the logfiles.
>>Thanks for the examples anyway. I still think that this is kind of a 
>>workaround.
>>With the mtime approach you could argue that there is no need for a 
>>timestamp in the filenames at all. Even without mtime you could do a 
>>script that looks in all the files to select ranges.
>>In my opinion a log processor program would the preferable solution and 
>>fit well in the runit-suite.
> 
> Hmm... how about this idea for log processor program:
> 1) svlogd execute processor which just fork in background and return log file
>    without changes back to svlogd
> 2) svlogd remove old TAI-logfile and create new TAI-logfile
> 3) processor (forked in background) notice log rotation is done (how?) and then:
>     1) execute 'ln newTAIlogfile newLOCALTIMElogfile' to create hard linked file
>     2) search for some oldLOCALTIMElogfile with only one hardlink to it (because
>        oldTAIlogfile which was hardlinked to it was just removed by svlogd) and
>        remove it too
>     3) exit
> 
> Maybe it's better to do this work in cron-script instead of log processor.

Sorry for my ambiguous writing -- i meant the "svlogp" program that 
Gerrit mentioned and described like this:

> I've been thinking about a "svlogp" program (svlog processor, or pager)
> for some time, which should be able to select log message by pattern or
> time, to merge logs from multiple log directories, and maybe to
> transform timestamps and more.

With svlogp the format of filenames and timestamps wouldn't matter 
anymore. You could for example [my interpretation] specify one or more 
logdir(s), your favorite timeformat, from-date and to-date (in that 
timeformat) on the command line and get the merged logmessages for that 
range on stdout, lines prefixed with a timestamp in the given format.

Best regards,
Henrik

-- 
Henrik Heil, zweipol Coy & Heil GbR
http://www.zweipol.net/