From a64a045d1dbff2a5776f411eaf58c4a40c067e67 Mon Sep 17 00:00:00 2001 From: Rich Felker Date: Fri, 11 Jul 2014 21:56:50 -0400 Subject: suppress early syslog return when log socket cannot be opened this behavior is no longer valid in general, and was never necessary. if the LOG_PERROR option is set, output to stderr could still succeed. also, when the LOG_CONS option is added, it will need syslog to proceed even if opening the log socket fails. --- src/misc/syslog.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/misc/syslog.c b/src/misc/syslog.c index eb782984..6d2a864a 100644 --- a/src/misc/syslog.c +++ b/src/misc/syslog.c @@ -82,10 +82,7 @@ static void _vsyslog(int priority, const char *message, va_list ap) int l, l2; int hlen; - if (log_fd < 0) { - __openlog(); - if (log_fd < 0) return; - } + if (log_fd < 0) __openlog(); if (!(priority & LOG_FACMASK)) priority |= log_facility; -- cgit v1.2.3-70-g09d2