[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] Best way to avoid systemd woes for NTP?
From: |
Greg Troxel |
Subject: |
Re: [gpsd-dev] Best way to avoid systemd woes for NTP? |
Date: |
Mon, 06 May 2019 20:06:43 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix) |
"Gary E. Miller" <address@hidden> writes:
>> >> 5) I don't follow how the default setup works, in that the hotplug
>> >> script should run on insert, and then gpsd only started when
>> >> someone starts a client. So with the following sequence:
>> >>
>> >> 1) boot
>> >> 2) systemd starts listening on 2947, no gpsd
>> >> 3) USB GPS mouse inserted
>> >> 4) user runs xgps
>> >> 5) systemd receives connection, starts up gpsd
>> >
>> > Step 3a) systemd starts gpsd.
>>
>> Because of some hotplug stuff? So systemed starts gpsd on either a
>> hotplug insert, or on a connection to 2947?
>
> No, because you use -n and have systemd start gpsd on insert.
I meant: when this is set up without -n, and without changing systemd
config files. So that it works as OS default:
on boot, systemd listens on 2947, no gpsd
usb gps mouse inserted : ???
user runs xgps - systemd starts gpsd and hands it the socket
> I assume when you understand it, you'll document it for your HAM
> friends. Please also send that to us.
More or less, yes. My immediate goal is one reliable setup for Field
Day.
[gpsd-dev] Best way to avoid systemd woes for NTP?, Greg Troxel, 2019/05/05