Pardon me if this is a duplicate. Had trouble posting to the forum.
I have a couple of systems successfully running Chrony and the LinuxPTP
package using the Timemaster service. These systems are Intel and ARM based
showing no issues and work well. A new embedded device that is ARM based is
in the process of bring up with a Yocto variant of Linux giving me an odd
error I have not seen before. Any thoughts as to what would cause a "Fatal
error : Unit socket path too long?". See the output below of running
timemaster from the command line as a root account. We have not set it to a
service yet.
root@mercury:~# timemaster -f /etc/linuxptp/timemaster.conf -m
timemaster[3696.243]: process 1396 started: /usr/sbin/chronyd -n -f
/run/timemaster/chrony.conf
timemaster[3696.244]: process 1397 started: /usr/sbin/ptp4l -l 5 -f
/run/timemaster/ptp4l.0.conf -H -i eth0
timemaster[3696.244]: process 1398 started: /usr/sbin/phc2sys -l 0 -a -r -R
4.00 -z /run/timemaster/ptp4l.0.socket -t [0:eth0] -n 0 -E ntpshm -M 0
Fatal error : Unix socket path too long
timemaster[3696.252]: received signal 17
timemaster[3696.252]: process 1396 terminated with status 1
timemaster[3696.252]: process 1398 terminated with status 255
timemaster[3696.255]: process 1397 terminated with status 0
timemaster[3696.256]: exiting
root@mercury:~# timemaster -v
1.92
root@mercury:~#
Thanks,
Jonathan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
