On Wed, 2009-09-02 at 16:10 +0200, Gabor Gombas wrote:
On Wed, Sep 02, 2009 at 02:30:11PM +0100, Colin Watson wrote:
Maybe a better option would be to let rsyslog automatically create the
directory for the socket if it is missing?
If it created the socket itself as well, then that
Package: openssh-server
Version: 1:5.1p1-7
Severity: wishlist
Hi,
Now that the default syslog daemon is rsyslog, openssh-server could ship
a configure snippet in /etc/rsyslog.d/openssh-server.conf that contains:
$$AddUnixListenSocket /var/run/sshd/dev/log
And probably the issue should be
On Wed, Sep 02, 2009 at 11:03:24AM +0200, Gábor Gombás wrote:
Now that the default syslog daemon is rsyslog, openssh-server could ship
a configure snippet in /etc/rsyslog.d/openssh-server.conf that contains:
$$AddUnixListenSocket /var/run/sshd/dev/log
And probably the issue should be
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
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
sorry, looks like I forgot the CCs on my previous message. Context given
in quote...
On Wed, 2009-09-02 at 13:07 +0100, Colin Watson wrote:
The problem here is that HUP is either one of the two. So if openssh's
init needs a restart type HUP, rsyslogd must be configured to use
restart-type
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
On Wed, 2009-09-02 at 14:46 +0200, Gabor Gombas wrote:
Maybe a better option would be to let rsyslog automatically create the
directory for the socket if it is missing?
ahhh - so trivial :) If that helps, that would, I think, not be a big
deal. I would still appreciate some feedback on my
On Wed, 2009-09-02 at 12:15 +0100, Colin Watson wrote:
I can't say I'm keen on an arbitrary delay either. inotify would be
better, but until rsyslog can use it perhaps
I have checked the code now. What I can do with relative ease is re-try
opening failed sockets. However, this would create a
On Wed, Sep 02, 2009 at 02:46:34PM +0200, Gabor Gombas wrote:
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.
On Wed, Sep 02, 2009 at 02:30:11PM +0100, Colin Watson wrote:
Maybe a better option would be to let rsyslog automatically create the
directory for the socket if it is missing?
If it created the socket itself as well, then that might do the job.
We'd need to make sure permissions were
11 matches
Mail list logo
