Bug#429243: stopped working, SSH stopped logging failures!
On Wed, Sep 02, 2009 at 12:07:58PM +0200, Rainer Gerhards wrote:
> On Wed, 2009-09-02 at 10:51 +0100, Colin Watson wrote:
> > I definitely don't want to do this. Init script multiplication has a
> > slow but inexorable effect on boot time.
> >
> > Michael, is there a standard approach that packages can use to do this?
> > postfix doesn't seem to do anything particularly special.
>
> Some time ago, Michael and I briefly discussed the possibility that
> rsyslogd would defer some of its configuration statements to solve such
> split situations. Actually, what we discussed was more complex, but I
> wonder if a somewhat simpler solution might solve a practical need: What
> if we could instruct the socket listener to defer getting activated by
> some (fixed, but configurable) period. Something along the lines of
>
> $IMUXSockDelayListen 60
>
> to delay listening by 60 seconds after startup. I think I could quickly
> implement such a functionality (in v4-devel) if and only if the delay
> applies to all sockets. Not sure if that constraints renders the idea
> unusable.
I can't say I'm keen on an arbitrary delay either. inotify would be
better, but until rsyslog can use it perhaps it would be adequate to
just send it SIGHUP from openssh's init script; will that cause it to
reopen the output file?
Perhaps we could have a version of $AddUnixListenSocket that only adds
the socket if it exists on the filesystem. That would make it easy to
put all the bits together.
--
Colin Watson [cjwatson@debian.org]
Reply to: