Bug#429243: stopped working, SSH stopped logging failures!
On Wed, 2009-09-02 at 10:51 +0100, Colin Watson wrote:
> > Unfortunately it won't really help when /var/run is on tmpfs, because
> > the syslog daemon is started before the ssh init script has run. The
> > only proper solution I can think of right now is to split the ssh init
> > script in two:
> >
> > - the first part runs before any syslog daemon, and does nothing except
> > creating /var/run/sshd/dev directory if it is missing
> >
> > - the second part runs after the syslog daemon has started, and does the
> > rest.
>
> 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.
Rainer
Reply to: