gpsd always runs in 'non-daemonised' or not at all

Bug #1581272 reported by wadda
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gpsd (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

The systemd unit file

/lib/systemd/system/gpsd.service

starts gpsd with the '-N' flag for a non-daemonised instance.

Removing the flag prevents systemd from calling the gpsd at all.

The service needs the removal of the '-N' flag so the gpsd can fully function, and insertion of 'Type=forking' to enable it to read its own configuration file '/etc/default/gpsd'

Attached is a patch, if I've done it correctly.

Revision history for this message
wadda (a-moe) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "allow systemd to control gpsd" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Bernd Zeimetz (bzed) wrote :

Your description is wrong - systemd happily handles a running gpsd in fireground mode.
Also /etc/default/gpsd is not read by gpsd, but by systemd and the options are passed to gpsd.

Whatever the problem is you are having, your change is not the fix for it.

Please not that gpsd - by default - will not start automatically. Its start is triggered by systemd socket activation. You'll have to add an appropriate systemd config file if you want to change that - for example if you need to have systemd running at system boot.

Changed in gpsd (Ubuntu):
status: New → Incomplete
Revision history for this message
wadda (a-moe) wrote : Re: [Bug 1581272] Re: gpsd always runs in 'non-daemonised' or not at all

On Fri, 13 May 2016 10:15:01 -0000
Bernd Zeimetz <email address hidden> wrote:

> systemd happily handles a running gpsd in fireground mode.

Sure, the -N flag is to run gpsd in the foregound.

But if you want gpsd to run as a daemon, it cannot with the current configuration.

If you remove the -N flag it will not function at all.

Moreover, modifications to the "EnvironmentFile=-/etc/default/gpsd are never read.

Try it. Modify the options, change the device....nothing.

Make the change to the unit file, *that is consistent* with dealing with unix style daemons, such as gpsd, and all these problems go away.

--
Moe <email address hidden>

Revision history for this message
wadda (a-moe) wrote :

I'll back-peddle on the EnvironmentFile. I reverted the unit file and voila. Modification in /etc/default/gpsd manifest. It will go down as mystery.

The running in foreground, or not at all still hold.

Revision history for this message
Bernd Zeimetz (bzed) wrote :

> The running in foreground, or not at all still hold.

-N works perfectly well, systemd was made exactly for that.
Youll still have to figure out what else is wrong.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gpsd (Ubuntu) because there has been no activity for 60 days.]

Changed in gpsd (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.