Re: socket activation and -n?

On Wed, 12 Feb 2020 at 16:09, Russell Nelson <address@hidden> wrote:

That doesn't help because of "socket activation." I've resorted to using the hack of `sh.nc(0, 2947, _in="/dev/null", _out="/dev/null")` . Maybe some systemd expert will tell me how to avoid using socket activation at all?
On Wed, Feb 12, 2020 at 3:11 PM Dominic Amann <address@hidden> wrote:
I am certainly no systemd expert - its just installed on our base system and I end up having to deal with it. That's why I run devuan at home.

It sounds like the client connection unit needs to have a "Before" dependency on gpsd (and so gpsd would need to be started by systemd for systemd to be aware of it).

On Wed, 12 Feb 2020 at 14:37, Gary E. Miller <address@hidden> wrote:
Yo Dominic!

On Wed, 12 Feb 2020 14:18:24 -0500
Dominic Amann <address@hidden> wrote:

> Not a systemd user by choice.

Some may be stuck wuth systemd, but they are never stuck running gpsd
under systemd. The later is a choice.

> Did you run sytemctl daemon-reload after changing anything (removing
> script etc)?

The problem is that systemd does not start gpssd before a client connects,
so the "-n" has no practical effect.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
address@hidden Tel:+1 541 382 8588

Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin

--
Dominic Amann
M 416-270-4587

From:	Dominic Amann
Subject:	Re: socket activation and -n?
Date:	Wed, 12 Feb 2020 16:19:08 -0500