linux-kernel - fork manpage wrt file locks

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>] [day] [month] [year] [list]

Message-ID: <f36b08ee0711210423nf2832a7w56cba9252a1df830@mail.gmail.com>
Date:	Wed, 21 Nov 2007 14:23:56 +0200
From:	"Yakov Lerner" <iler.ml@...il.com>
To:	"Kernel Linux" <linux-kernel@...r.kernel.org>
Subject: fork manpage wrt file locks

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
-
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/