From 87b0284327e34a4b96c22085fa2cdb3219294991 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Tue, 28 Jan 2014 18:23:38 -0500 Subject: Get rid of write_safe Current glibc implementation is safe. Kernel does this atomically, and write is actually implemented through writev. So if write is async-signal-safe, than writev pretty much must be too. --- src/journal/journal-send.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/journal') diff --git a/src/journal/journal-send.c b/src/journal/journal-send.c index 960c5776b0..ca9199f718 100644 --- a/src/journal/journal-send.c +++ b/src/journal/journal-send.c @@ -314,7 +314,7 @@ _public_ int sd_journal_sendv(const struct iovec *iov, int n) { if (buffer_fd < 0) return buffer_fd; - n = writev_safe(buffer_fd, w, j); + n = writev(buffer_fd, w, j); if (n < 0) { close_nointr_nofail(buffer_fd); return -errno; -- cgit v1.2.3-54-g00ecf