Jiri Benc <jb...@redhat.com> writes:
> pmc is different. It's not tied to the service start time, it's used by > administrators and by various scripts from varying environment. While > you can reasonably expect that ptp4l and phc2sys will be run in the > same name space, it's not necessarily the case for pmc. Hmm, and as an end user I can't do `ip netns identify $(pidof ptp4l)` even if I know about this issue. Maybe ptp4l could include the namespace name in the VLA response. Are the messages considered a stable API? Alternatively I might mention the issue in the man page. Not being able to tell which of the PTP port identifiers represents which actual interface is something of a problem if you have more than about two of them. _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
