Re: kern.maxlockf for byte range lock limit

[Joerg Sonnenberger <joerg%bec.de@localhost>]

On Tue, Jul 13, 2021 at 06:37:57AM +0000, Emmanuel Dreyfus wrote:
> On Tue, Jul 13, 2021 at 03:36:49AM +0000, David Holland wrote:
> > Well, that was the idea; make it some factor times the current open
> > file limit or something like that. Not sure why the existing limit is
> > apparently per-user rather than per-process or what that's supposed to
> > accomplish. These lock objects are not exactly large so it's not
> > necessary to be tightfisted with them.
> 
> Then we could just use maxfiles, coulnd't we? 

You should be able to have multiple locks per file, but the whole point
of the limit was that shouldn't be able to trivially exhaust kernel
memory.

Joerg