Bug#569032: Sends SIGUSR1 to init unconditionally, conflicts with upstart

2010-03-21 Thread Michael Biebl
Hi Petter! On 21.03.2010 16:14, Petter Reinholdtsen wrote: > [Petter Reinholdtsen] >> I see the point of only signaling init when the socket changed, but >> am unsure if we want to look for upstart specific binaries in the >> generic scripts. Is there still a bug with upstart if this change >> is

Bug#569032: Sends SIGUSR1 to init unconditionally, conflicts with upstart

2010-03-21 Thread Petter Reinholdtsen
[Petter Reinholdtsen] > I see the point of only signaling init when the socket changed, but > am unsure if we want to look for upstart specific binaries in the > generic scripts. Is there still a bug with upstart if this change > is implemented instead? I commited and uploaded the change to move

Bug#569032: Sends SIGUSR1 to init unconditionally, conflicts with upstart

2010-03-20 Thread Petter Reinholdtsen
[Michael Biebl] > There was a bug in my previous patch (a missing '!'), noticed it > after hitting the send button. > > Please find attached an updated patch. I see the point of only signaling init when the socket changed, but am unsure if we want to look for upstart specific binaries in the gene

Bug#569032: Sends SIGUSR1 to init unconditionally, conflicts with upstart

2010-02-09 Thread Michael Biebl
Package: initscripts Version: 2.87dsf-8 Severity: important File: /etc/init.d/mountall.sh Tags: patch Hi, mountall.sh contains this code: # # We might have mounted something over /dev, see if # /dev/initctl is there. # if [ ! -p $INITCTL ] then