Re: gpsd and systemd on buster
On Fri, 20 Sep 2019 09:05:57 +0200
john doe <johndoe65534@mail.com> wrote:
> On 9/19/2019 9:13 PM, Charles Curley wrote:
> > On Thu, 19 Sep 2019 20:27:22 +0200
> > john doe <johndoe65534@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.
>
>
>
> 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.
>
> Also from one of your link:
>
> "# /etc/systemd/system/gpsd.socket.d/socket.conf
> [Socket]
> # First blank ListenStream clears the system defaults
> ListenStream=
> ListenStream=2947
> ListenStream=/var/run/gpsd.sock"
>
> That is don't touch '/lib/systemd/system/gpsd.socket' but add in
> '/etc/systemd/system/gpsd.socket.d/socket.conf' only what need to be
> changed.
Thanks. I already knew that, but it doesn't hurt to say it again.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Reply to: