Re: [gpsd-users] gpsd always starting in foregound (a systemd solution)

[Bernd Zeimetz]

On 05/12/2016 05:48 PM, Moe wrote:
> Adding to my bad advice, and following up my own post.
> 
> Fixing the gpsd/systemd troubles in
> 
> /lib/systemd/system/gpsd.service

You should never modify this file.
Use /etc/systemd/system for customization.

> PIDFile=/var/run/gpsd.pid
> 
> Is not required, as previously claimed.
> 
> Type=forking, is required...but someone thought -N was required too.

As I told you in your ubuntu bug report, Type=forking is the
wrong way to work with systemd.

Unfortunately I still fail to find a real proper description of the
problem you are having. All I can find are pieces of
'you have to change that' ...

Please write what you are trying to do (like run chrony with
gpsd), which packages you've installed, which version of the packages,
what is the content of all config files, and what the problem is what
you are seeing in your opinion and how you found out about it.


My wild guess is that something is talking to the gpsd socket and so
stopping gpsd.service will not help you as the gpsd.socket unit will
just start it again.
I assume that by modifying gpsd.service to fork gpsd you are breaking
the way systemd passes the open socket to gpsd, so it will actually stop
when your stop the service...



-- 
 Bernd Zeimetz                            Debian GNU/Linux Developer
 http://bzed.de                                http://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F