public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmbeer2 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29445] New: Error in the documentation
Date: Thu, 04 Aug 2022 00:37:36 +0000 [thread overview]
Message-ID: <bug-29445-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29445
Bug ID: 29445
Summary: Error in the documentation
Product: glibc
Version: 2.35
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: rmbeer2 at gmail dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
After reading and doing some tests to be sure, I have verified that the
documentation of open (man 2 open) is not correct.
- Make read only (O_RDONLY) don't give read and write mode (O_RDWR).
- Using O_CREAT don't modify again the modes of the file after being created.
- Omit the third parameter, the mode get any garbage is make for the file.
- Write mode only work in the first time where the file is create, don't matter
if the file are create in no write mode.
I'm not sure how it should be fixed, or if any standard should be followed.
Perhaps only the modification of the operating details in the documentation is
needed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-08-04 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 0:37 rmbeer2 at gmail dot com [this message]
2022-08-04 0:39 ` [Bug libc/29445] Error in the documentation of OPEN rmbeer2 at gmail dot com
2022-08-04 8:01 ` fweimer at redhat dot com
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=bug-29445-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).