[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fw: ✘3.23 is near. Systemd files

From: Carles Pina i Estany
Subject: Re: Fw: ✘3.23 is near. Systemd files
Date: Sat, 31 Jul 2021 09:10:11 +0200
User-agent: Mutt/1.10.1 (2018-07-13)


I'm just a gpsd recent new user, I landed here with different
problems. This is feedback from a user, maybe not the best time.

On Jul/31/2021, Bernd Zeimetz wrote:
> Hi,
> On Fri, 2021-07-30 at 15:38 -0700, Gary E. Miller wrote:
> > 
> > Do you have an opinion on the attached?
> > 
> yes. Basically shows that the creator failed to understand how systemd and
> socket activation works.
> - socket is provided by gpsd.socket
> - gpsd.service is started when something connects to the socket, the
> connection filehandle is passed to gpsd.
> - options should go into the environment file.
> - attache usb devices are handled by udev and gpsd is activated via the
> socket. There might be devices missing in the udev config.
> For those who don't like the automatic way, using a systemd override file is
> the best option as it keeps things aliged to what is shipped by upstream or
> packages.

when I was debugging my problems (on a Debian 10 and Raspbian 10): after
I "more or less understood" the socket activation (I haven't had to
debug problems on software that was managed by systemd's socket
activation before, so it was a bit confusing and I still feel that I
don't understand it well enough to be comfortable in a debugging
session): I wanted to disable systemd's managing gpsd, just to remove
one thing out of the way (debugging purposes).

All of this to say: could the "override file" be documented somewhere?
Either in Debian's /usr/share/gpsd or in gpsd's website.


Carles Pina i Estany

reply via email to

[Prev in Thread] Current Thread [Next in Thread]