AST/ksh93 getconf builtin does not support XATTR_EXISTS and other ACL/SACL/XATTR keys

[cedricblancher]

AST/ksh93 getconf builtin does not support XATTR_EXISTS and other ACL/SACL/XATTR keys

Example (on Solaris 11.4):

builtin getconf
getconf XATTR_EXISTS .
getconf: Invalid argument (XATTR_EXISTS)

The following fpathconf() keys should be supported (remove "PC" to get the string for getconf's argument):
_PC_XATTR_EXISTS
_PC_XATTR_ENABLED
_PC_SATTR_ENABLED
_PC_SATTR_EXISTS

[McDutchie]

What is the ksh version you're testing (output of echo ${.sh.version})? Support for XATTR_ENABLED, XATTR_EXISTS and SATTR_ENABLED should have been added in e183319, although that commit didn't add SATTR_EXISTS.

[cedricblancher]

What is the ksh version you're testing (output of echo ${.sh.version})? Support for XATTR_ENABLED, XATTR_EXISTS and SATTR_ENABLED should have been added in e183319, although that commit didn't add SATTR_EXISTS.

ksh93 --version
version sh (AT&T Research) 93u+m/1.0.10 2024-08-01

If a newer release has these keys, then please just add SATTR_EXISTS

[McDutchie]

Those three are in the 1.0.10 release, backported from the AT&T 93v- beta. So if they're not working, there is something else wrong.

[McDutchie]

OK, so I'm testing it on a VM with an evaluation version of Solaris 11.4 now, and I'm a little confused. The system's getconf command at /usr/xpg6/bin/getconf doesn't seem to support these four keys either, as it gives identical results: "Invalid argument". What gives?

[McDutchie]

Alright, so now I'm even more confused: I cannot reproduce your problem. While the external getconf command does not seem to support these keys, I can get the getconf builtin to use them just fine -- all four of them, on version 93u+m/1.0.10 as released.

However, I can reproduce your problem on the AT&T ksh 93u+ 2012-08-01 that comes with the system. Its getconf builtin indeed does not seem to support these keys. Are you sure you weren't testing that instead of the current 93u+m release?

[McDutchie]

Note: the best way to make sure you're using the version of ksh that you just built, is the bin/package use command.

[McDutchie]

So, the explanation for the fact that all four worked, though one is missing from conf.tab, is that conf.sh automatically detects them as well. conftab.c is the file generated by it:

$ grep -n '[SX]ATTR_' arch/sol11.i386-64/src/lib/libast/conftab.c              
322:{ "SATTR_ENABLED", { 0UL, 0 }, { 0UL, 0 }, 0, CONF_SUN, 1, CONF_pathconf, _PC_SATTR_ENABLED },
323:{ "SATTR_EXISTS", { 0UL, 0 }, { 0UL, 0 }, CONF_FEATURE|CONF_UNDERSCORE, CONF_POSIX, 1, CONF_pathconf, _PC_SATTR_EXISTS },
483:{ "XATTR_ENABLED", { 0UL, 0 }, { 0UL, 0 }, 0, CONF_SUN, 1, CONF_pathconf, _PC_XATTR_ENABLED },
484:{ "XATTR_EXISTS", { 0UL, 0 }, { 0UL, 0 }, 0, CONF_SUN, 1, CONF_pathconf, _PC_XATTR_EXISTS },

Note how SATTR_EXISTS has different flags, though it still works.

So, I'll add it to conf.tab to correct that.

As for your reproducer, I can only conclude you must have been testing the wrong ksh version. If you can show otherwise, please comment here and I'll reopen the issue.