On Wed, Jun 25, 2014 at 04:39:47PM +0200, Miroslav Lichvar wrote: > On Wed, Jun 25, 2014 at 06:04:46AM +0200, Richard Cochran wrote: > > On Mon, Jun 23, 2014 at 06:46:59PM +0200, Miroslav Lichvar wrote: > > > This allows running phc2sys and pmc in multiple PTP domains at the same > > > time. It also makes it easier to configure ptp4l, the uds_address > > > option doesn't need to be set if domainNumber is different from other > > > instances. > > > > This would make an small but incompatible, user visible change, for third > > party pmc clients. > > Hm, do we know if there are any? And do they have an option to set the > path to the socket?
Well, I have heard of at least two besides our own pmc, but I don't know the details of the implementation. The UDS is the RPC interface to the host, which might have something like a GPS program controlling the PHC. 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. 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. Thanks, Richard ------------------------------------------------------------------------------ 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
