If multiple management clients are used in the network and ptp4l
responded at least once over UDS, it will try to forward all management
responses received from network to the last UDS client. ptp4l doesn't
track the messages and doesn't know if they are responses to the UDS
client or other clients in the network. If the UDS client is no longer
running (receiving messages on its address), ptp4l logs "uds port:
management forward failed" error message. With frequent management
requests in the network this can lead to flooding of the system log.
Downgrade the error message to debug to disable it in the default log
level.
Signed-off-by: Miroslav Lichvar <mlich...@redhat.com>
---
clock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/clock.c b/clock.c
index 5a64613..74911fd 100644
--- a/clock.c
+++ b/clock.c
@@ -1585,7 +1585,7 @@ static void clock_forward_mgmt_msg(struct clock *c,
struct port *p, struct ptp_m
port_log_name(piter));
}
if (clock_do_forward_mgmt(c, p, c->uds_rw_port, msg,
&msg_ready))
- pr_err("uds port: management forward failed");
+ pr_debug("uds port: management forward failed");
if (msg_ready) {
msg_post_recv(msg, pdulen);
msg->management.boundaryHops++;
--
2.41.0
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
