Bug 1479834
Summary: | Multiple ptp4l use same /var/run/ptp4l | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Beat Rubischon <brubisch> |
Component: | linuxptp | Assignee: | Miroslav Lichvar <mlichvar> |
Status: | CLOSED WONTFIX | QA Contact: | Qiao Zhao <qzhao> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.4 | CC: | thozza, xiawu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-17 09:09:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1549614 |
Description
Beat Rubischon
2017-08-09 13:59:28 UTC
I think one way to solve this would be to modify ptp4l to not try to remove the socket on start. If binding to the socket fails, ptp4l will work without the UDS transport, or perhaps it could be handled as a fatal error. The question is if it would be acceptable behavior in case the socket was left there due to ptp4l terminating in an abnormal way (e.g. crash). The user would have to manually remove the socket in order to get phc2sys working. It will change the user experience. FWIW, an RFC patch was posted for this on the upstream list https://www.mail-archive.com/linuxptp-devel@lists.sourceforge.net/msg02103.html As this would change the behavior of ptp4l in case of an existing socket (from existing or crashed ptp4l instance), I think it would rather be a candidate for the next major RHEL release instead of minor release. Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. |