pathconf(2) _PC_NO_TRUNC wrong description ?

[Nicolas Joly <njoly%pasteur.fr@localhost>]

Hi,

It seems that _PC_NO_TRUNC description from pathconf(2) man page is
wrong/inverted:

     _PC_NO_TRUNC
             Return 1 if filenames longer than {NAME_MAX} are truncated.

While most our filesystems do return 1 in that case, they do not
truncate the offending file name, but fail with ENAMETOOLONG instead.
This looks like the expected behaviour as the variable name suggest.

And 0 would mean that too long file names are truncated to the max
allowed value for the filesystem. Actually, only sysvbfs follow this
case (but seems to have a bug preventing correct behaviour).

Could someone confirm that the man page is wrong ?

Thanks.

-- 
Nicolas Joly

Biological Software and Databanks.
Institut Pasteur, Paris.