I think the existing gpsd.service has a bug in that it states
After=chronyd.service when the correct service is chrony.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771080
Title:
gpsd shoul
Hi Mark,
today I'm not answering on my own, instead the Debian maintainer Vincent Blut
already contacted me on this bug (as he has issues with Launchpad to answer on
his own), so I'm forwarding his message:
"The fact that the gpsd.service mentions “After=chronyd.service” should
not be an issue b
** Changed in: gpsd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: chrony (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771080
Title:
gp
Thanks Mark, I have seen your discussions on #systemd about it - perfect
understatement of your skills :-).
Don't be afraid, I'm not tracking you, but among other IRC highlights, one on
"chrony" helps me to ensure our users are good with it :-)
I find it puzzling as well why it should be "differ
I have an odd behaviour in that gpsd starts on one machine but not on
the other. I think this is just me being new to systemd, please let's
close this bug as invalid until I have a deeper root cause. Thanks for
the help!
status invalid
--
You received this bug notification because you are a mem
On 05/17/2018 06:52 AM, Christian Ehrhardt wrote:
> GPSD calls systemd helpers for the service which will end up in *inst
> maintainer scripts.
> in d/rules are:
> dh_systemd_enable -pgpsd
>
> dh_installinit
