On 9/22/2019 8:54 PM, Charles Curley wrote: > On Fri, 20 Sep 2019 09:05:57 +0200 > john doe <johndoe65...@mail.com> wrote: > >> On 9/19/2019 9:13 PM, Charles Curley wrote: >>> On Thu, 19 Sep 2019 20:27:22 +0200 >>> john doe <johndoe65...@mail.com> wrote: > >>> >>> OK. How do I stop it from running short of running 'disable' and >>> rebooting? >>> >> >> Sorry, didn't spot that you had chained command. >> >> You also need to 'stop' the socket to fully stop everything, you need >> to stop 'gpsd' and 'gpsd.socket'.: >> >> $ systemctl stop gpsd.service >> Warning: Stopping gpsd.service, but it can still be activated by: >> gpsd.socket >> $ systemctl stop gpsd.socket >> >> Or in one invocation: >> >> $ systemctl stop gpsd.socket gpsd > > Thank you. > > I gather that in this context "gpsd" is a nickname for "gpsd.service" > only. It does not include "gpsd.socket". Which explains the warning > above. > From (1):
"Parameter Syntax Unit commands listed above take either a single unit name (designated as UNIT), or multiple unit specifications (designated as PATTERN…). In the first case, the unit name with or without a suffix must be given. If the suffix is not specified (unit name is "abbreviated"), systemctl will append a suitable suffix, ".service" by default, and a type-specific suffix in case of commands which operate only on specific unit types." >> >> >> >> In the output that you have provided, an sysvinit script seems to be >> called but there is a systemd service file provided by Debian. > > Right. You can do some initialization in /etc/default/gpsd, provided by > the gpsd package. > Yes, the unit will also use that file! :) 1) https://www.freedesktop.org/software/systemd/man/systemctl.html -- John Doe
