Bug#401558: ipw3945d: Binary userspace regulatory daemon starting twice on bootup

2006-12-12 Thread Jurij Smakov
Hi Dieter, I've prepared a new ipw3945d package with a new workaround. Now the init script just checks for a situation when the daemon is running, but the pid file is not present, and stops it before doing anything, if that's the case. It's not very elegant, but probably most robust way to

Bug#401558: ipw3945d: Binary userspace regulatory daemon starting twice

2006-12-09 Thread Jurij Smakov
On Sat, Dec 09, 2006 at 01:26:05PM +0100, Dieter Roels wrote: Jurij, I am sorry to tell you, but when I turned my portable on this morning the daemon was started twice again :( Well, when you said that you did not have a /lib/init/rw directory, I sort of expected this to happen. The point

Bug#401558: ipw3945d: Binary userspace regulatory daemon starting twice

2006-12-07 Thread Jurij Smakov
Hi Dieter, Can you please try an ipw394d package from http://www.wooyd.org/debian/ipw3945d I reworked the init script, which should now correctly detect whether we are starting early by udev, and not invoking the daemon in that case. Best regards, -- Jurij Smakov

Bug#401558: ipw3945d: Binary userspace regulatory daemon starting twice on bootup

2006-12-06 Thread Dieter Roels
Jurij Smakov wrote: No, I don't think its bootlogd. According to /etc/rcS.d/S02mountkernfs.sh it is possible for /var/run to be mounted on tmpfs (and it would become writeable before the udev is run in that case) by setting RAMRUN=yes in /etc/default/rcS. Can you post the output of 'mount' on

Bug#401558: ipw3945d: Binary userspace regulatory daemon starting twice on bootup

2006-12-05 Thread Jurij Smakov
On Tue, Dec 05, 2006 at 04:55:31PM +0100, Dieter Roels wrote: Jurij, You are right, /var is writeable when the daemon is started from udev. But i have no idea why... As far as I know, I'm running a standard debian testing (except kernel). The only thing I could think of that's not

Bug#401558: ipw3945d: Binary userspace regulatory daemon starting twice on bootup

2006-12-05 Thread Dieter Roels
Jurij Smakov wrote: The thing you describe may happen if your /var/run/ipw3945d directory is writeable already when udev starts the daemon. Then it is started early, but later /etc/rcS.d/S36mountall-bootclean.sh is run, which cleans out the /var/run directory. So the pid file gets lost, and

Bug#401558: ipw3945d: Binary userspace regulatory daemon starting twice on bootup

2006-12-04 Thread Dieter Roels
Package: ipw3945d Version: 1.7.22-2 On bootup the daemon is started by modprobe when the ipw3945 module is loaded. A few seconds later the daemon is started again from /etc/init.d/ipw3945d. The strange thing is the daemon is in fact started twice. As there are 2 daemons fighting for the

Bug#401558: ipw3945d: Binary userspace regulatory daemon starting twice on bootup

2006-12-04 Thread Jurij Smakov
On Mon, Dec 04, 2006 at 03:39:51PM +0100, Dieter Roels wrote: Package: ipw3945d Version: 1.7.22-2 On bootup the daemon is started by modprobe when the ipw3945 module is loaded. A few seconds later the daemon is started again from /etc/init.d/ipw3945d. The strange thing is the daemon is