public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eblake at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/22099] getconf help info
Date: Mon, 08 Apr 2024 15:30:30 +0000	[thread overview]
Message-ID: <bug-22099-131-h8gk8pt150@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22099-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=22099

Eric Blake <eblake at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eblake at redhat dot com

--- Comment #1 from Eric Blake <eblake at redhat dot com> ---
This came up in the Austin Group meeting today:
https://austingroupbugs.net/view.php?id=1808

POSIX is considering standardizing 'getconf -a'; so the inconsistency  between
'getconf' stating that -a is supported, and 'getconf --help' not mentioning it,
should be fixed.

It was also uncertain whether 'getconf -a /some/file' can ever have output
different than 'getconf -a'.  The former should list values specific to
fpathconf for /some/file, that may have different values depending on the file
system underlying that file, while the latter should list values specific to
getconf; however, the Austin Group noted that at least 'getconf -a | grep
NAME_MAX' vs. 'getconf -a . | grep NAME_MAX' gave the same input, but I'm not
sure if there is an easy way to trigger a given file name that would
demonstrate a path-specific result from fpathconf.

BSD also has 'getconf -l' which lists the names (but not results) of the
various getconf/fpathconf constants (useful since some of the results can be
strings that might include a newline, rendering the output of -a ambiguous).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

       reply	other threads:[~2024-04-08 15:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-22099-131@http.sourceware.org/bugzilla/>
2024-04-08 15:30 ` eblake at redhat dot com [this message]
2024-04-11 15:14 ` eblake at redhat dot com
2024-04-13 18:35 ` fweimer at redhat dot com
2024-04-15 12:34 ` eblake at redhat dot com
2024-04-15 12:46 ` eblake at redhat dot com
2024-04-17 17:11 ` fweimer at redhat dot com
2024-04-17 19:25 ` eblake 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-22099-131-h8gk8pt150@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).