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 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 da

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 sam