On Wed, Jun 25, 2014 at 04:53:26PM +0200, Richard Cochran wrote: > Personally, as an end user, I find it really annoying when these > sorts of things change for no apparent reason. That is why I suggested > keeping the default socket name.
I agree, but I think this wouldn't be the first time the path to the socket was changed. :) > 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. Perhaps with scripts it doesn't matter much, but using the tools from command line will not be very comfortable with multiple PTP domains. Consider pmc -u -d 0 -s /var/run/ptp4l.0 -? /var/run/pmc.0 'GET TIME_STATUS_NP' pmc -u -d 1 -s /var/run/ptp4l.1 -? /var/run/pmc.1 'GET TIME_STATUS_NP' vs. pmc -u -d 0 'GET TIME_STATUS_NP' pmc -u -d 1 'GET TIME_STATUS_NP' -- 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
