From: "Yakov Lerner" <iler.ml@gmail.com>
To: "Kernel Linux" <linux-kernel@vger.kernel.org>
Subject: fork manpage wrt file locks
Date: Wed, 21 Nov 2007 14:23:56 +0200 [thread overview]
Message-ID: <f36b08ee0711210423nf2832a7w56cba9252a1df830@mail.gmail.com> (raw)
Manpage 'man 2 fork' says:
'File locks ... are not inherited.'
This is true for POSIX locks, but not for flock-type locks.
This phrase comes directly from posix fork manpage,
which is not aware of flock-style locks.
Maybe fork manpage should rather say:
... POSIX file locks are not inherited (fcntl(2)).
Flock-style locks are inherited (see flock(2)) ...
?
Yakov
reply other threads:[~2007-11-21 12:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f36b08ee0711210423nf2832a7w56cba9252a1df830@mail.gmail.com \
--to=iler.ml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®