My apologies, I think I was unclear on one crucial point. I am specifically talking about the chrony sockets, eg the ones at @RUNDIR@/chrony.XXX.sock. These are made by the ntp daemon wanting to receive the gps data, and it is one such a daemon I primarily work on. We prefer strongly to run that daemon with non-root privileges, which makes creating these sockets in @RUNDIR@ directly a bit of a hastle, and it would therefore be useful to be able to move gpsd's idea of where they might be. This would not involve moving any socket gpsd itself creates.
As for changing compile time options, most of my users use gpsd from their distribution, and getting them to recompile is likely out of the question. Also, that would move gpsd's own sockets, which they might not want to do. On Thu, 3 Jul 2025 at 15:17, James Browning <[email protected]> wrote: > ::snip:: > As someone whose opinion and twenty bucks will get you a a side of fries, > I > suggest the third. > > III) Start gpsd as an non-privileged user of a group that can read/write > the > serial and PPS devices. > > IIRC it requires some added capability on Linux to generate the PPS device > node; other systems need not apply. > > Your proposals are anathema to the brittle nature of gpsd > James, I am not sure what you mean with your third option, could you clarify what you mean? I am not clear on how changing the privilege level of the gpsd daemon would affect where it looks for the chrony sockets, or what permissions an ntp daemon would need to create those sockets. Kind regards, David Venhoek
