This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: sysconf & AIO_LISTIO_MAX


Andreas Jaeger <aj@suse.de> writes:

|> >>>>> Andreas Schwab writes:
|> 
|>  > Neale.Ferguson@SoftwareAG-USA.com writes:
|>  > |> On Linux, how do I interpret getting a -1 value from
|>  > |> sysconf(_SC_AIO_LISTIO_MAX) with a ERRNO of 0 (i.e. successful)? Does that
|>  > |> mean Linux has no limit?
|> 
|>  > It means that it is not supported.  From SUS2
|>  > (http://www.unix-systems.org/onlinepubs/007908799/xsh/sysconf.html):
|> 
|>  >  RETURN VALUE
|> 
|>  >      If name is an invalid value, sysconf() returns -1 and sets errno to
|>  >      indicate the error. If the variable corresponding to name is
|>  >      associated with functionality that is not supported by the system,
|>  >      sysconf() returns -1 without changing the value of errno.
|> 
|> Is the glibc manual correct here?  It confuses me:

I think they can be regarded as equivalent.  "Not supported functionality"
probably includes the case of "no limit imposed".

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]