linux-kernel - manual page 'ack to Inbox ArchiveReport SpamDelete More Actions 1 of 584 Older

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <f36b08ee0711190610g22b10551hb31b77e54fe46794@mail.gmail.com>
Date:	Mon, 19 Nov 2007 16:10:44 +0200
From:	"Yakov Lerner" <iler.ml@...il.com>
To:	"Kernel Linux" <linux-kernel@...r.kernel.org>
Subject: manual page 'ack to Inbox ArchiveReport SpamDelete More Actions 1 of 584 Older › manual page 'man 2 fork' wrt file locks

Manual page 'man 2 fork' says:
                  'File locks ... are not inherited.'
This is true for POSIX locks (fcntl-style locks).

But flock-style locks (aka bsd-style locks) are not inherited across
fork, correct ?

Would not it be more helpful if fork manpage said:

         POSIX file locks(fcntl(2)) are not inherited.
         flock-style locks are inherited (see flock(2))

?

Yakov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/