Subject: Re: kern/25118: semop() fails with EINVAL even when SEMUME is increased
To: Simon Burge <email@example.com>
From: enami tsugutomo <firstname.lastname@example.org>
Date: 04/10/2004 13:12:22
> It appears that seminfo.semume isn't changable (unless you mean changing
> it with say gdb --write). I think the original patch in the PR has the
> right effect otherwise. That said, it looks like changing SEMU to use
> seminfo.semume instead of SEMUME would be a good idea.
Simply sysv_sem.c wasn't recompiled since it doesn't include
opt_sysvparam.h, was it?