On Wed, Jul 26, 2017 at 01:13:43PM +0200, Miroslav Lichvar wrote: > An unrelated issue I noticed is that restarting ptp4l which is > compiled/configured with an incorrect offset when phc2sys was already > running and its pmc update happens before ptp4l gets the correct > offset from its master causes phc2sys to use the incorrect offset > until next pmc update. Would the fix require modifying ptp4l to send > an update to subscribed clients when it's terminating, so phc2sys > stops updating the clock and starts again only when it has correct UTC > offset?
Yeah, I noticed that too. However, I think the current behavior is reasonable. For re-starting the services, there are two options. 1. Always start and stop ptp4l and phc2sys in concert. 2. Run phc2sys with '-S 1.0' to allow jumps. Maybe there are ways to make all of this more robust, but please remember the simply use case of an isolated LAN without any offset information and the operator doesn't care. Thanks, Richard ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
