On Thu, 9 Jan 2020 at 12:56, Joerg Sonnenberger <[email protected]> wrote: > > On Thu, Jan 09, 2020 at 12:42:29PM +0000, Chavdar Ivanov wrote: > > In order to get the above running on -current (yes, it is this way > > hardcoded in the package). If 3404 is some magic number required, then > > perhaps the package should be patched to run under -current (or, > > perhaps, the released and beta versions, I haven't tried). sysctl > > wouldn't matter, as it is per process, as far as I understand it; also > > /etc/login.conf openfile-cur does not make any difference. > > kern.maxfiles?
Upon seeing this, my first though was that I have overlooked something obvious; kern.maxfiles is indeed 3404 by default. However, even one can increase it - e.g. to 4096 - this does not change the behaviour with respect to the other: ... # sysctl kern.maxfiles kern.maxfiles = 4096 # sysctl proc.curproc.rlimit.descriptors proc.curproc.rlimit.descriptors.soft = 1024 proc.curproc.rlimit.descriptors.hard = 3404 # sysctl -w proc.curproc.rlimit.descriptors.hard=4096 proc.curproc.rlimit.descriptors.hard: 3404 -> 4096 # sysctl -w proc.curproc.rlimit.descriptors.soft=4096 sysctl: proc.curproc.rlimit.descriptors.soft: Invalid argument # sysctl -w proc.curproc.rlimit.descriptors.soft=3404 proc.curproc.rlimit.descriptors.soft: 1024 -> 3404 # sysctl proc.curproc.rlimit.descriptors proc.curproc.rlimit.descriptors.soft = 1024 proc.curproc.rlimit.descriptors.hard = 3404 .... 'jupyter-3.7 notebook-3.7' fails if I change the hardcoded value to anything above 3404; it works with 3404. > > Joerg -- ----
