From 947ecb08122c0337d0ec22b315182e2559f9d2cb Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 16 Jan 2026 21:47:12 +0100 Subject: [PATCH] socket: turn of loud logging when setting up sockopts in container fails due to privs Various socktops will fail if we run in a container, due to lack of privs (for example SO_RECVFORCE as used by the journald sockets). That's typically not a big issue. Hence downgrade the log level. Follow-up for: f7df0eab8d9520f37a2feaecf532d78de6ab6b7d --- src/core/socket.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/core/socket.c b/src/core/socket.c index 6ce307a00f..0ca9d80e04 100644 --- a/src/core/socket.c +++ b/src/core/socket.c @@ -1031,7 +1031,8 @@ DEFINE_TRIVIAL_CLEANUP_FUNC_FULL(Socket*, socket_close_fds, NULL); int _e_ = (e); \ log_unit_full_errno( \ UNIT(s), \ - ERRNO_IS_NOT_SUPPORTED(_e_) ? LOG_DEBUG : LOG_WARNING, \ + ERRNO_IS_NOT_SUPPORTED(_e_) || \ + ERRNO_IS_PRIVILEGE(_e_) ? LOG_DEBUG : LOG_WARNING, \ _e_, \ "Failed to set %s socket option, ignoring: %m", \ option); \