RepoMirrors
/
musl
mirror of git://git.musl-libc.org/musl
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

remove useless SIGPIPE protection from syslog 

per the standard, SIGPIPE is not generated for SOCK_DGRAM.
This commit is contained in:
Rich Felker 2011-04-13 17:51:45 -04:00
parent a444ee3410
commit a77411a50d
1 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/misc/syslog.c
View File

@ -65,7 +65,6 @@ void openlog(const char *ident, int opt, int facility)
void syslog(int priority, const char *message, ...)
{
sigset_t set, oldset;
va_list ap;
char timebuf[16];
time_t now;
@ -83,10 +82,6 @@ void syslog(int priority, const char *message, ...)
return;
}
sigemptyset(&set);
sigaddset(&set, SIGPIPE);
pthread_sigmask(SIG_BLOCK, &set, &oldset);
now = time(NULL);
gmtime_r(&now, &tm);
strftime(timebuf, sizeof timebuf, "%b %e %T", &tm);
@ -105,9 +100,5 @@ void syslog(int priority, const char *message, ...)
// Note: LOG_CONS is not supported because it is annoying!!
// syslogd will send messages to console if it deems them appropriate!
/* Clear any possible SIGPIPE generated by the socket write. */
sigtimedwait(&set, 0, (struct timespec [1]){0}) || (perror("x"),1);
pthread_sigmask(SIG_SETMASK, &oldset, 0);
UNLOCK(&lock);
}