chiark / gitweb /
~ianmdlvl / elogind.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 7b36bf8) | patch
Get rid of write_safe
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Tue, 28 Jan 2014 23:23:38 +0000 (18:23 -0500)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Wed, 29 Jan 2014 00:07:12 +0000 (19:07 -0500)
commit87b0284327e34a4b96c22085fa2cdb3219294991
tree3dfa856eb4ee93e6e7808f442a7dd14daff00d8etree | snapshot
parent7b36bf82c4deeadef6d914cef750b4a51ff2ed48commit | diff
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 diff | blob | history
src/shared/util.c diff | blob | history
src/test/test-util.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.