On Fri, 20 Jun 2014 09:52:49 +0200, Miroslav Lichvar wrote: > I think a combination of ptp4l sending notification on exit and > phc2sys timing out when no reply is received in the pmc update > interval (1 minute) would be good enough.
Except when ptp4l is killed/crashes and is restarted. That's something that wouldn't be caught by this and would create quite a messy situation, especially when it's restarted automatically by system startup scripts (e.g. systemd). > Switching to the SEQPACKET socket seems like a lot of work and it > wouldn't detect unresponsive ptp4l, which might be a useful thing to > have (the same applies to the process monitoring). I don't think that unresponsive ptp4l is a likely state. How could this happen, sans a horrible bug? Jiri -- Jiri Benc ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
