From 69f0081748fb4be1b7b772815e5c4202cdb88d3d Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 24 Oct 2014 18:32:30 +0200 Subject: timesyncd: the IP_TOS sockopt is really just an optimization, we shouldn't fail if we can't set it This partially undos 2f905e821e0342c36f5a5d3a51d53aabccc800bd --- src/timesync/timesyncd-manager.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'src') diff --git a/src/timesync/timesyncd-manager.c b/src/timesync/timesyncd-manager.c index e5b156b7dd..3ae01eb8fc 100644 --- a/src/timesync/timesyncd-manager.c +++ b/src/timesync/timesyncd-manager.c @@ -720,9 +720,7 @@ static int manager_listen_setup(Manager *m) { if (r < 0) return -errno; - r = setsockopt(m->server_socket, IPPROTO_IP, IP_TOS, &tos, sizeof(tos)); - if (r < 0) - return -errno; + (void) setsockopt(m->server_socket, IPPROTO_IP, IP_TOS, &tos, sizeof(tos)); return sd_event_add_io(m->event, &m->event_receive, m->server_socket, EPOLLIN, manager_receive_response, m); } -- cgit v1.2.3-54-g00ecf