[PATCH] innfeed does not reopen (rotated) log file
julien at trigofacile.com
Wed Jan 16 20:52:46 UTC 2013
>> Does anyone have any concerns about this and think we should add a
>> separate signal for log rotation?
> It's the same as what other daemons (e.g. apache2) do after log rotation
> / on SIGHUP, so it shouldn't come as too much of a surprise IMHO.
OK, thanks for having answered, Florian and Jeffrey.
> Related to the original issue, yesterday I noticed that ninpaths and
> controlchan have a deleted log/OLD/errlog on stdout and stderr. Perhaps
> 'ctlinnd flushlogs' as used in scanlogs should also cause flushing of
> all channel / exploder feeds?
Couldn't we just run
ctlinnd name ''
ctlinnd flush xxx
on every "proc" type entry returned by the command?
It would solve the problem you mention, and also the flush of innfeed
log files because all running innfeed would be restarted.
21:46 news at trigo ~% ctlinnd name ''
=> We would flush "controlchan!", "innfeed!", "source-archive!",
"nocem!" and "inpaths!".
> PS: insignificant typo:
> --- a/doc/pod/newsfeeds.pod
> +++ b/doc/pod/newsfeeds.pod
> @@ -638,7 +638,7 @@ at its leisure. File feeds are most frequently used in combination with
> A program feed (B<Tp>) spawns a given program for every article that the
> -site receives. The I<paramter> field must be the command line to execute,
> +site receives. The I<parameter> field must be the command line to execute,
> and should contain one instance of C<%s>, which will be replaced by the
> storage API token of the article (the actual article can be retrieved by
> the program using sm(8)). The program will not receive anything on
« Le beau est toujours bizarre. » (Baudelaire)
More information about the inn-workers