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 "different" on both systems. I have seen you ended with wondering about what the packaging does about it, so I wanted to dump that here FYI. 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 dh_systemd_start -pgpsd --restart-after-upgrade That sequence should make it available and started after install in all cases. The only interesting bit, it seems to be actually socket activated. Therefore the "indirect" on gpsd, but you can check the socket via $ systemctl status gpsd.socket I hope that might shed some light onto your issue. -- 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 should start after chrony if they are being used together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1771080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
