On Wed, Dec 18, 2013 at 11:50:24AM -0800, Junio C Hamano wrote:
> -------------------------------- 8< ------------------------------
>
> static unsigned int get_max_fd_limit(void)
> {
> #ifdef RLIMIT_NOFILE
> struct rlimit lim;
>
> if (!getrlimit(RLIMIT_NOFILE, &lim))
> return lim.rlim_cur;
> #endif
>
> #if defined(_SC_OPEN_MAX)
> {
> long sc_open_max = sysconf(_SC_OPEN_MAX);
> if (0 < sc_open_max)
> return sc_open_max;
> }
>
> #if defined(OPEN_MAX)
> return OPEN_MAX;
> #else
> return 1; /* see the caller ;-) */
> #endif
> }
>
> -------------------------------- >8 ------------------------------
Yeah, with the #endif followup you posted, this is what I had in mind.
> But the sysconf part makes me wonder; here is what we see in
> http://pubs.opengroup.org/onlinepubs/9699919799/functions/sysconf.html
>
> If name is an invalid value, sysconf() shall return -1 and set errno
> to indicate the error. If the variable corresponding to name is
> described in <limits.h> as a maximum or minimum value and the
> variable has no limit, sysconf() shall return -1 without changing
> the value of errno. Note that indefinite limits do not imply
> infinite limits; see <limits.h>.
>
> For a broken system (like RLIMIT_NOFILE defined for the compiler,
> but the actual call returns a bogus error), the compiler may see the
> _SC_OPEN_MAX defined, while sysconf() may say "I've never heard of
> such a name" and return -1, or the system, whether broken or not,
> may want to say "Unlimited" and return -1. The caller takes
> anything unreasonable as a positive value capped to 25 or something,
> so there isn't a real harm if we returned a bogus value from here,
> but I am not sure what the safe default behaviour of this function
> should be to help such a broken system while not harming systems
> that are functioning correctly.
According to the POSIX quote above, it sounds like we could do:
#if defined (_SC_OPEN_MAX)
{
long max;
errno = 0;
max = sysconf(_SC_OPEN_MAX);
if (0 < max) /* got the limit */
return max;
else if (!errno) /* unlimited, cast to int-max */
return max;
/* otherwise, fall through */
}
#endif
Obviously you could collapse the two branches of the conditional, though
I think it deserves at least a comment to explain what is going on.
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
