Hello,
On Sat, Nov 14, 2020 at 07:43:14PM +0000, Michael van Elst wrote:
> tlaro...@polynum.com writes:
>
> >I have increased kern.maxfiles (the default of 956 being too low).
>
> >But how to increase proc.curproc.rlimit.descriptors.{hard,soft}?
> >Whatever I give to soft, sysctl refuses with "invalid argument".
>
> You set limits with 'ulimit' (or limit in csh) and programs started
> by the shell will inherit the limits.
>
But this is the problem: ulimit -n doesn't accept it either. So I
concluded that the limit set by the kernel imposes, logically, a limit.
So how can one increase the kernel limit so that ulimit -n can work with
a greater value? (it doesn't accept anything else but 956, despite
kern.maxfiles being increased).
And:
sysctl -a|grep descriptors
only return proc.curproc...
>
> >BTW, sysctl(7) still mentions proc.pid but this doesn't exist.
> >Apparently it is proc.curproc now.
>
> Maybe proc.$pid makes it easier to understand. The second label
> is the numeric PID of the process you want to look at or "curproc"
> for the process doing the query (usually the sysctl command itself).
Thanks! I thought "pid" was a bit strange so I should have guessed that
it was a variable...
Best,
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
http://kertex.kergis.com/
http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
