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/11/2004 08:42:05
> I thought about that too.
I was just wanted to know the original cause of bug.
> This gets back to the "do we want a somehow modified seminfo" to
> work (with "gdb --write" or a newly introduced system call or
> possibly a superuser-only semctl command)?
... or, want to remove static limit?