On Tue, Jul 13, 2021 at 06:37:57AM +, Emmanuel Dreyfus wrote:
> On Tue, Jul 13, 2021 at 03:36:49AM +, 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-use
On Tue, Jul 13, 2021 at 03:36:49AM +, 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 l
On Mon, Jul 12, 2021 at 08:03:54AM +, Emmanuel Dreyfus wrote:
> On Fri, Jul 09, 2021 at 08:52:08PM +, David Holland wrote:
> > This was discussed somewhere briefly (probably on chat) a couple weeks
> > ago, with the conclusion that we should just make the limit something
> > like twice
On Fri, Jul 09, 2021 at 08:52:08PM +, David Holland wrote:
> This was discussed somewhere briefly (probably on chat) a couple weeks
> ago, with the conclusion that we should just make the limit something
> like twice the maximum number of open files and forget about it. No
> real need to add mo
On Fri, Jul 09, 2021 at 03:27:57PM +, Emmanuel Dreyfus wrote:
> I recently hit a bug where mariadb import failed befause of
> maxlocksperuid limit:a
> http://mail-index.netbsd.org/netbsd-users/2021/07/09/msg027330.html
>
> Attached is a patch that documents ENOMEM for fcntl() and flock()
> @@ -146,8 +146,10 @@
> {
> extern int kern_logsigexit; /* defined in kern/kern_sig.c */
> extern fixpt_t ccpu;/* defined in kern/kern_synch.c */
> extern int dumponpanic; /* defined in kern/subr_prf.c */
> + extern int maxlocksperuid; /* defined
