On 12-04-2020 17:25, ASSI via devel wrote: >> # ppswatch /chroot/ntpd/dev/pps0 >> (shows similar output) > > Good, but does ntpd see the same?
Well, devices look like this: # ls -l /dev/*ps* lrwxrwxrwx 1 root root 5 Apr 12 16:54 /dev/gps0 -> ttyS0 lrwxrwxrwx 1 root root 4 Apr 12 16:54 /dev/gpspps0 -> pps0 crw-rw---- 1 root ntp 253, 0 Apr 12 16:54 /dev/pps0 # ls -l /dev/ttyS0 crw-rw---- 1 root ntp 4, 64 Apr 12 16:54 /dev/ttyS0 # ls -l /chroot/ntpd/dev/ total 0 lrwxrwxrwx 1 root root 5 Mar 9 2018 gps0 -> ttyS0 lrwxrwxrwx 1 root root 4 Mar 9 2018 gpspps0 -> pps0 srw-rw-rw- 1 root root 0 Apr 12 16:39 log crw-r--r-- 1 ntp ntp 1, 3 Mar 9 2018 null crw-r--r-- 1 ntp ntp 253, 0 Nov 3 17:15 pps0 crw-r--r-- 1 ntp ntp 4, 64 Mar 9 2018 ttyS0 So a process running as ntp could access the necessary device files. What else could be in the way of ntpd 'seeing' things? Udo _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
