Roland,
Yes. This is a bug in /usr/bin/getconf. I'll file a bug
report this afternoon.
- Don
>Date: Thu, 19 Apr 2007 04:33:01 +0200
>From: Roland Mainz <roland.mainz at nrubsig.org>
>
>Glenn Fowler wrote:
>>
>> there is an inconsistency in the implementation of
>> getconf SSIZE_MAX
>> vs other symbols like
>> getconf SIZE_MAX
>> getconf INT_MAX
>> getconf UINT_MAX
>>
>> the inconsistency is that
>> getconf SIZE_MAX
>> returns the actual largest value for size_t, whereas
>> getconf SSIZE_MAX
>> returns the _POSIX_SSIZE_MAX minmax value, as does
>> getconf _POSIX_SSIZE_MAX
>>
>> this shows that getconf is capable of distinguishing between
>> actual and minmax values:
>> getconf AIO_LISTIO_MAX => 4096
>> getconf _POSIX_AIO_LISTIO_MAX => 2 (the minmax value)
>>
>> man did not reveal a special case for SSIZE_MAX
>>
>> for consistency "getconf SSIZE_MAX" should return the
>> largest value for ssize_t
>>
>> any solaris rationale why it doesn't?
>
>CC:'ing Don Cragun&&April for help...
>
>Don/April: Is it possible that this is a bug in Solaris /usr/bin/getconf
>?
>
>----
>
>Bye,
>Roland
