On Sun Nov 15 10:23:43 2015, ntyni@iki.fi wrote:
Show quoted text> On Sun, Nov 15, 2015 at 08:13:10AM -0500, Jarkko_Hietaniemi via RT
> wrote:
> >
> > What operating system is this?
>
> Debian unstable, amd64.
>
> > That it would be only those two constants and not the others added in
> > 1.2908 would be strange, since all of them were added using the same
> > pattern. (Which is the same pattern used before.)
>
> Sure it applies to all the new ones, those two were just examples.
> Sorry
> for being unclear.
>
> % perl -MBSD::Resource -le 'my $r = get_rlimits(); for my $res (keys
> %$r) { my $val = eval "&BSD::Resource::${res}()"; print "$res $r-
> >{$res} <$val>" }'
> RLIMIT_FSIZE 1 <1>
> RLIMIT_RTTIME 15 <>
> RLIMIT_SIGPENDING 11 <>
> RLIMIT_OFILE 7 <7>
> RLIMIT_VMEM 9 <9>
> RLIMIT_RSS 5 <5>
> RLIMIT_LOCKS 10 <10>
> RLIMIT_CORE 4 <4>
> RLIMIT_DATA 2 <2>
> RLIMIT_OPEN_MAX 7 <7>
> RLIMIT_RTPRIO 14 <>
> RLIMIT_AS 9 <9>
> RLIMIT_NICE 13 <>
> RLIMIT_NPROC 6 <6>
> RLIMIT_CPU 0 <0>
> RLIMIT_STACK 3 <3>
> RLIMIT_NOFILE 7 <7>
> RLIMIT_MEMLOCK 8 <8>
> RLIMIT_MSGQUEUE 12 <>
Hmm. In this case it smells like the t/modules/apache_resource.t needs some looking into. What is it actually trying to test?
And what does "man getrlimit" say about those missing constants? What it now looks like is that those constants are defined in the system headers (since they get compiled in) but then ... they do not work?