INN 2.5, inn-CURRENT-20090103 Issues

[Jeffrey M. Vinocur]

On Thu, 8 Jan 2009, [iso-8859-1] Julien ÉLIE wrote:

> > Just to clarify for the record, running ctlinnd like that does not result
> > in innfeed being totally restarted -- it's still the same instance (same
> > process ID for example) just refresing its internal config.
> 
> ctlinnd flush
>     Flushing the innfeed channel feed is the recommended method of restarting
>     innfeed to pick up new configuration.  innd will spawn a new innfeed process
>     while the old process shuts down cleanly.
> 
> It seems to be the case.
> And that's why it is strange that innfeed was not seen as the new binary.

Huh!

Sorry for the mixup -- I was thinking about the behavior of `kill -HUP` 
rather than `ctlinnd flush`!  Indeed, ctlinnd flush should respawn a new 
process and pick up the new binary (if it was indeed moved into the 
correct location).


-- 
Jeffrey M. Vinocur
jeff at litech.org