Hi Jeff, I'll follow up on your reply in a moment. But, in the meantime, you missed a question of mine: >>> +.TP >>> +.BR F_OFD_SETLK " (\fIstruct flock *\fP)" >>> +Acquire an open file description lock (when >>> +.I l_type >>> +is >>> +.B F_RDLCK >>> +or >>> +.BR F_WRLCK ) >>> +or release an open file description lock (when >>> +.I l_type >>> +is >>> +.BR F_UNLCK ) >>> +on the bytes specified by the >>> +.IR l_whence ", " l_start ", and " l_len >>> +fields of >>> +.IR lock . >>> +If a conflicting lock is held by another process, >>> +this call returns \-1 and sets >>> +.I errno >>> +to >>> +.B EACCES >>> +or >>> +.BR EAGAIN . >> >> The "EACCES or EAGAIN" thing comes from POSIX, because different >> implementations of tradition record locks returned one of these errors. >> So, portable applications using traditional locks must handle either >> possibility. However, that argument doesn't apply for these new locks. >> Surely, we just want to say "set errno to EAGAIN" for this case? Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
