Red Hat Bugzilla – Bug 717419
Provide native systemd unit file
Last modified: 2011-07-26 12:03:34 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 510353 [details]
Native systemd service file for gpsd
Just out of curiosity is this service applicant for hardware activation unfortunately our guidelines are a bit short
on how to do that
Hardware activation occurs when a service is installed but only turns on if a
certain type of hardware is installed. Enabling of the service is normally done
with a udev rule. At this time we do not have further guidance on how to write
those udev rules. The service itself installs its .service files in the normal
places and are installed by the normal systemd scriptlets. These services
should never be enabled by the package as they will be enabled by udev. "
But you can read man systemd.device and look at the bluetooth service which is
doing that I believe that is if it's relevant....
Thanks. It's included in gpsd-2.95-7.fc16.
Hardware activation is possible only with USB devices, with serial port a normal service is still needed.
The udev rules start the gpsd daemon directly which I suspect will cause systemd to not see the process.
The upstream git now supports socket activation. It would be cool to combine the two and start the daemon only when a GPS is connected to USB and a gpsd client is trying to connect to gpsd.
Yeah something like he did for cups.