On Wed, Jun 25, 2014 at 05:56:31PM +0200, Miroslav Lichvar wrote: > On Wed, Jun 25, 2014 at 04:53:26PM +0200, Richard Cochran wrote: > > Maybe it is better just to leave the uds path as is. After all, the > > user (and his scripts) can set the names freely, even with .domainName > > if desired. > > We'll still need to use different paths for the phc2sys and pmc > sockets or add new options to set them to allow running multiple > instances at the same time. Also, phc2sys currently doesn't even have > an option to set the ptp4l path.
BTW, is running two ptp4l instances in the same PTP domain a valid use case? Appending the number to the socket name would not help here. It looks like we might need a more general approach anyway. -- Miroslav Lichvar ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
