| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
He says:
If you have just rebooted and not otherwise launched gpsd, plugging in a
gps creates the device file properly, but does not launch gpsd. The
problem is the test for ${GPSD_SOCKET} in line 35 of
gpsd.hotplug.wrapper. If you have just rebooted, the socket doesn't
exist, so the test fails.
My workaround is to remove the test.
It sucks that udev is such a moving target.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The wrapper doesn't seem to work when USBAUTO is not set, this is
because [ -n ] gives different result than [ -n "" ], addressed by
the attached patch.
It includes also the options remapping to be consistent with the rpm
init script and sysconfig file, and adds /usr/sbin to PATH which is
needed on some systems to find gpsd in the hotplug script.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
|
|
|
|
|
|
|
|
|
| |
Udev does not fork, so waiting for mountpoints to appear at boot time
will block the boot process until we run into the timeout. A proper
implementation would be to fork a process to wait in the background
or to handle the not-yet-added devices in the gpsd init script.
So this is more a quick fix then the proper solution.
See http://bugs.debian.org/591324 for details.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Debian bug #561574
Thanks to Luca Niccoli for the report.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This change should affect distributions which use /etc/default/gpsd
in a way similar to Debian.
|
|
|
|
| |
We reuse /etc/default/gpsd for that.
|
| |
|
| |
|
|
|
|
| |
First line where possible, second line for scripts called with #!
|
|
|