On Fri, Mar 31, 2006 at 06:28:14AM -0500, sean finney wrote:
> On Fri, Mar 31, 2006 at 09:47:59AM +0200, Wouter Verhelst wrote:
> > What I'm suggesting is, actually, the reverse of a pidfile, in some way.
> > You'd still have your /var/run/syslogd.pid; but, assuming that file
> > contained the PID
pe, 2006-03-31 kello 13:07 +0100, Stephen Gran kirjoitti:
> This one time, at band camp, Frank Küster said:
> > sean finney <[EMAIL PROTECTED]> wrote:
> >
> > > sysloginits="inetutils-syslogd metalog socklog-run sysklogd syslog-ng"
> > > for s in $sysloginits; do
> > > test -x /etc/init.d/$s &&
This one time, at band camp, Frank Küster said:
> sean finney <[EMAIL PROTECTED]> wrote:
>
> > sysloginits="inetutils-syslogd metalog socklog-run sysklogd syslog-ng"
> > for s in $sysloginits; do
> > test -x /etc/init.d/$s && invoke-rc.d $s restart || true
> > done
>
> Well, that would try to
sean finney <[EMAIL PROTECTED]> wrote:
> sysloginits="inetutils-syslogd metalog socklog-run sysklogd syslog-ng"
> for s in $sysloginits; do
> test -x /etc/init.d/$s && invoke-rc.d $s restart || true
> done
Well, that would try to start each installed service, even if that is
not intended by
On Fri, Mar 31, 2006 at 09:47:59AM +0200, Wouter Verhelst wrote:
> What I'm suggesting is, actually, the reverse of a pidfile, in some way.
> You'd still have your /var/run/syslogd.pid; but, assuming that file
> contained the PID "2722" (as it currently does on my system), you'd also
> have a file
On Fri, Mar 31, 2006 at 07:17:27AM +0200, Mike Hommey wrote:
> On Thu, Mar 30, 2006 at 10:51:03PM +0200, Wouter Verhelst <[EMAIL PROTECTED]>
> wrote:
> > On Thu, Mar 30, 2006 at 06:22:23PM +0100, Rich Walker wrote:
> > > Sam Morris <[EMAIL PROTECTED]> writes:
> > >
> > > >
> > > > That much is ea
On Thu, Mar 30, 2006 at 10:51:03PM +0200, Wouter Verhelst <[EMAIL PROTECTED]>
wrote:
> On Thu, Mar 30, 2006 at 06:22:23PM +0100, Rich Walker wrote:
> > Sam Morris <[EMAIL PROTECTED]> writes:
> >
> > >
> > > That much is easy, but how do you turn a process ID into a script that
> > > can be invoke
On Thu, Mar 30, 2006 at 06:22:23PM +0100, Rich Walker wrote:
> Sam Morris <[EMAIL PROTECTED]> writes:
>
> >
> > That much is easy, but how do you turn a process ID into a script that
> > can be invoke-rc.d'd?
>
> Make it part of the Debian spec?
>
> define a known script name (logging-daemon) th
On Mar 30, Peter Palfrader <[EMAIL PROTECTED]> wrote:
> A common interface for adding additional locations of logging sockets
> would also be nice. So that packages could tell the local syslogd to
> please create a socket in /chroots/bind/dev/log and then chroot by
> default.
*Many* years ago I o
Sam Morris <[EMAIL PROTECTED]> writes:
>
> That much is easy, but how do you turn a process ID into a script that
> can be invoke-rc.d'd?
Make it part of the Debian spec?
define a known script name (logging-daemon) that must exist in
/etc/init.d/ and can be a symlink to another one.
submit a sm
On Thu, 2006-03-30 at 18:22 +0200, Adrian von Bidder wrote:
>
> (Taking advantage of the fact that IIRC processes printing log messages open
> and close the socket for every messages, so looking a few times until
> abs(the intersection of all processes on that socket) == 1 should be safe.
It's
On Tuesday 28 March 2006 18:15, Marco d'Itri wrote:
On Mar 28, Gabor Gombas <[EMAIL PROTECTED]> wrote:
How about restarting syslog (or it's equivalent) after relocating the
old /dev? glibc already has infrastructure for restarting services on
upgrade, maybe udev can borrow that.
Harder than it
On 3/30/06, Adrian von Bidder <[EMAIL PROTECTED]> wrote:
> On Tuesday 28 March 2006 18:15, Marco d'Itri wrote:
> > On Mar 28, Gabor Gombas <[EMAIL PROTECTED]> wrote:
> > > How about restarting syslog (or it's equivalent) after relocating the
> > > old /dev? glibc already has infrastructure for rest
On Tuesday 28 March 2006 18:15, Marco d'Itri wrote:
> On Mar 28, Gabor Gombas <[EMAIL PROTECTED]> wrote:
> > How about restarting syslog (or it's equivalent) after relocating the
> > old /dev? glibc already has infrastructure for restarting services on
> > upgrade, maybe udev can borrow that.
>
> H
Peter Palfrader <[EMAIL PROTECTED]> writes:
> A common interface for adding additional locations of logging sockets
> would also be nice. So that packages could tell the local syslogd to
> please create a socket in /chroots/bind/dev/log and then chroot by
> default.
In this case, one way of doin
On Wed, 29 Mar 2006, Marc Haber wrote:
> On Tue, 28 Mar 2006 18:15:27 +0200, [EMAIL PROTECTED] (Marco d'Itri) wrote:
> >On Mar 28, Gabor Gombas <[EMAIL PROTECTED]> wrote:
> >> How about restarting syslog (or it's equivalent) after relocating the
> >> old /dev? glibc already has infrastructure for
On Tue, 28 Mar 2006 18:15:27 +0200, [EMAIL PROTECTED] (Marco d'Itri) wrote:
>On Mar 28, Gabor Gombas <[EMAIL PROTECTED]> wrote:
>> How about restarting syslog (or it's equivalent) after relocating the
>> old /dev? glibc already has infrastructure for restarting services on
>> upgrade, maybe udev ca
On Tue, Mar 28, 2006 at 06:15:27PM +0200, Marco d'Itri wrote:
> Harder than it looks. There are multiple syslog daemons, how can the
> package know which one is installed and needs to be restarted?
glibc already checks for more than 40 packages and restarts only those
that are installed. I doubt
"Olaf van der Spek" <[EMAIL PROTECTED]> writes:
> On 3/28/06, sean finney <[EMAIL PROTECTED]> wrote:
>> On Tue, Mar 28, 2006 at 06:15:27PM +0200, Marco d'Itri wrote:
>> > Harder than it looks. There are multiple syslog daemons, how can the
>> > package know which one is installed and needs to be r
On 3/28/06, sean finney <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 28, 2006 at 06:15:27PM +0200, Marco d'Itri wrote:
> > Harder than it looks. There are multiple syslog daemons, how can the
> > package know which one is installed and needs to be restarted?
>
> are there really that many syslog daemon
On Tue, Mar 28, 2006 at 06:15:27PM +0200, Marco d'Itri wrote:
> Harder than it looks. There are multiple syslog daemons, how can the
> package know which one is installed and needs to be restarted?
are there really that many syslog daemons (my count is 5)? why not make
a list, fire off invoke-rc.
On Mar 28, Gabor Gombas <[EMAIL PROTECTED]> wrote:
> How about restarting syslog (or it's equivalent) after relocating the
> old /dev? glibc already has infrastructure for restarting services on
> upgrade, maybe udev can borrow that.
Harder than it looks. There are multiple syslog daemons, how can
On Tue, Mar 28, 2006 at 12:57:24PM +0200, Marco d'Itri wrote:
> Does anybody have an opinion about this?
> When udev is installed for the first time on a running system the
> current /dev/log socket ends up in /dev/.static/ (which is not
> world-readable) until the next reboot.
How about restarti
Does anybody have an opinion about this?
When udev is installed for the first time on a running system the
current /dev/log socket ends up in /dev/.static/ (which is not
world-readable) until the next reboot.
On Mar 19, Marco d'Itri <[EMAIL PROTECTED]> wrote:
> On Mar 19, Richard Kettlewell <[EMA
24 matches
Mail list logo
