On Thu, 16 Nov 2006 08:36:00 -0500 James Carlson wrote:
> Glenn Fowler writes:
> > why would /usr/bin/getconf point away from itself?
> In other words, '/usr/bin/getconf PATH' is how you find the path
> required for the POSIX.2 standards-conforming environment. POSIX.2 is
> a subset of XPG4.
thanks
my befuddlement arises from
/usr/bin/getconf PATH -- xpg4 value
/usr/bin/getconf PASS_MAX -- not an xpg4 value
/usr/xpg4/bin/getconf PASS_MAX -- xpg4 value
/usr/bin/getconf somehow chooses between xpg4 and not
is PATH a special case?
put another way, if PASS_MAX can be not-xpg4, why couldn't PATH too?
also, on that solaris 11 machine, can you post what
confstr(_CS_PATH, ...)
returns for a test prog compiled with default options
this isn't a drop dead issue -- I'd just like to understand
the situation enough to be able to predict where
/usr/bin/getconf foo
pulls its data from
at this point n>1 getconf's, along with -v, and a dependence on
compile time -D's affecting <limits.h> and sysconf(_SC_*) etc.
values is making about as much sense as the registry
and that's scary
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
