From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 237373858408; Mon, 8 Apr 2024 15:30:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 237373858408 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1712590231; bh=9mIL9/6WlN6EV0/BfU7P5UR9QPoyTTctk8X2epIYkV0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Vd8syphWHJDOhsrZSK0ZG1Z7cXjgVU7Z1WPVMVcpS/A109SQmFsm1RBmmHR/vnIz1 AgbL+G1U1ZuKdX21GIS0fPY+vkwHb5JOzR6kRvCMjaXWLbmjZec4xuv8awm0SgIun5 VehoNvGf13EPvzJloRBZSzhQFeoUVx4u3Gdi+mmY= From: "eblake at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/22099] getconf help info Date: Mon, 08 Apr 2024 15:30:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.23 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: eblake at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D22099 Eric Blake changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eblake at redhat dot com --- Comment #1 from Eric Blake --- This came up in the Austin Group meeting today: https://austingroupbugs.net/view.php?id=3D1808 POSIX is considering standardizing 'getconf -a'; so the inconsistency betw= een '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 f= ile 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 n= ot 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). --=20 You are receiving this mail because: You are on the CC list for the bug.=