* fsync(2) EINVAL example, fifo(7) read-only
@ 2011-01-23 9:08 Georg Sauthoff
0 siblings, 0 replies; only message in thread
From: Georg Sauthoff @ 2011-01-23 9:08 UTC (permalink / raw)
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w; +Cc: linux-man-u79uwXL29TY76Z2rM5mHXA
Hi,
just small stuff:
from the ERRORS section of fsync(2):
'EROFS, EINVAL
fd is bound to a special file which does not support
synchronization.
'
Consider adding an example of an file which does not support
synchronization, i.e. a note that doing fsync on a fifo yields EINVAL.
from fifo(7):
'A process can open a FIFO in nonblocking mode. In this case, opening for read
only will succeed even if no-one has opened on the write side yet, opening for
write only will fail with ENXIO (no such device or address) unless the other
end has already been opened.
'
IMHO it would be easier to parse, if 'read only'/'write only' would be
substituted with 'read-only'/'write-only'.
Best regards
Georg
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-01-23 9:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-23 9:08 fsync(2) EINVAL example, fifo(7) read-only Georg Sauthoff
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox