As provided by the fcntl() operations F_OFD_SETLK,
F_OFD_SETLKW, and F_OFD_GETLK
Signed-off-by: Jeff Layton <jlayton@poochiereds.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Jeff Layton:
The difference here is subtle. The gracetime is how long after a reboot
should knfsd allow clients to reclaim state (and deny the creation of
new locks and opens). The leasetime is how long the NFSv4 lease period
is. There is a relationship between the two that's illustrated in the
comments above write_gracetime:
/**
* write_gracetime - Set or report current NFSv4 grace period time
*
* As above, but sets the time of the NFSv4 grace period.
*
* Note this should never be set to less than the *previous*
* lease-period time, but we don't try to enforce this. (In the common
* case (a new boot), we don't know what the previous lease time was
* anyway.)
*/
The value you're interested in here is the nfsv4leasetime. If the
client doesn't renew its lease within that period, then it's subject to
the server giving up on it and dropping any state that it holds on that
clients' behalf.
Note that this is not a firm timeout. The server runs a job
periodically to clean out expired stateful objects, and it's likely
that there is some time (maybe even up to another whole lease period)
between when the timeout expires and the job actually runs. If the
client gets a RENEW in there within that window, its lease will be
renewed and its state preserved.
Reported-by: Jeff Layton <jlayton@poochiereds.net>
Cowritten-by: Jeff Layton <jlayton@poochiereds.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Jeff Layton confirmed that the bug remains even in modern kernels.
Reviewed-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions basename() and dirname() are thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
charmap(5) was outdated, bring it to closer to reality by fixing
syntax descriptions to match current glibc code and practices,
adding missing options, removing obsolete comments and references,
and removing now incorrect examples.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
And restore a piece about Biblical Hebrew that was
inadvertently deleted by Marko Myllynen's patch.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Rewrite the introduction to make Unicode's prominence more obvious.
Reformulate parts of the text to reflect current Unicode world.
Minor clarification for ASCII/ISO sections, some other minor fixes.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions mq_send() and mq_timedsend() are thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions mq_receive() and mq_timedreceive() are thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The function posix_fallocate() is thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
localedef(1) complains if really undefined, should be empty instead.
Also: add some SEE ALSO references.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Michael Kerrisk