Your message dated Tue, 23 Jun 2009 00:53:59 +0200
with message-id <[email protected]>
and subject line Fixed in 2.39-2
has caused the Debian Bug report #495842,
regarding Starting gpsd on hotplug seems broken
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
495842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495842
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gpsd
Version: 2.37-6
Severity: normal
Please forgive me if I have misunderstood how this is supposed
to work.
I want gpsd to start when I plug in the USB device.
debconf asks me this question:
Start gpsd automatically on boot?
This isn't what I want so I say no. It asks no other questions
and saves this in /etc/default/gpsd:
START_DAEMON="false"
USBAUTO="false"
As expected, /etc/init.d/gpsd looks at this and doesn't start
gpsd at boot.
When I hotplug the device, /lib/udev/gpsd.hotplug.wrapper is
called and does this:
[ "$START_DAEMON" = "true" ] || exit 0
Since START_DAEMON is false, it exits.
So I think there are two problems here. Firstly, if I say "no"
to starting on boot, debconf should ask me about hotplugging and
set USBAUTO based on my answer. Secondly,
/lib/udev/gpsd.hotplug.wrapper should not exit immediately when
START_DAEMON is false (I'm unsure whether the rest of the hotplug
script should or shouldn't run in the case when the daemon was
started at boot).
I have tested this on my system by (a) editting /etc/default/gpsd
to set START_DAEMON=false and USBAUTO=true and (b) reversing the
sense of the test in /lib/udev/gpsd.hotplug.wrapper, and it now
seems to do what I wanted.
Regards, Phil.
--- End Message ---
--- Begin Message ---
Version: 2.39-2
Hi,
thanks for the report. The bug was fixed in 2.39-2, butI forgot to close it in
the changelog unfortunately.
Cheers,
Bernd
--
Bernd Zeimetz Debian GNU/Linux Developer
GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
--- End Message ---
