On Wed, Sep 02, 2009 at 12:07:58PM +0200, Rainer Gerhards wrote:
> 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.
That would mean losing logs in the first 1 minute after boot. If that's
tolerable, then it would be much easier to just modify the order of the
init scripts, and start ssh _before_ the syslog daemon. That way the
amount of lost logs is much smaller.
Maybe a better option would be to let rsyslog automatically create the
directory for the socket if it is missing?
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
