> You can do that now, a few distros even do that. Except, as James > pointed out, it is chronyd/ntpd that creates the UNIX socket.
That seems backwards to me. I think of gpsd as a server that can support multiple clients. Normally, the client makes the connection to the server. > How does that solve the problem of ntpd/chronyd knowing it is connected > to a true gpsd server? Root or non-root? ntpd/chronyd would be trusting the admin to set things up right. If the file protection works as I expect, then a random hacker with a shell account on that system can't sneak in and grab the connection when gpsd or ntpd/chronyd is getting restarted. -- These are my opinions. I hate spam.
