Bug 717419 - Provide native systemd unit file
Provide native systemd unit file
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: gpsd (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Douglas E. Warner
Fedora Extras Quality Assurance
:
Depends On:
Blocks: SysVtoSystemd
  Show dependency treegraph
 
Reported: 2011-06-28 15:33 EDT by Jóhann B. Guðmundsson
Modified: 2011-07-26 12:03 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-07-26 11:57:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Native systemd service file for gpsd (283 bytes, text/plain)
2011-06-28 15:37 EDT, Jóhann B. Guðmundsson
no flags Details

  None (edit)
Description Jóhann B. Guðmundsson 2011-06-28 15:33:10 EDT
Description of problem:

https://fedoraproject.org/wiki/Features/SysVtoSystemd


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jóhann B. Guðmundsson 2011-06-28 15:37:31 EDT
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

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....
Comment 2 Miroslav Lichvar 2011-07-26 11:57:22 EDT
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.
Comment 3 Jóhann B. Guðmundsson 2011-07-26 12:03:34 EDT
Yeah something like he did for cups.

http://0pointer.de/blog/projects/socket-activation2.html

Note You need to log in before you can comment on or make changes to this bug.