Date: Fri, 5 Jan 2001 20:20:51 +0000 From: void <float@firedrake.org> To: Alfred Perlstein <bright@wintelcom.net> Cc: questions@FreeBSD.ORG Subject: Re: semsys(2) and undeletable semaphores Message-ID: <20010105202051.A27501@firedrake.org> In-Reply-To: <20010105121550.G15744@fw.wintelcom.net>; from bright@wintelcom.net on Fri, Jan 05, 2001 at 12:15:50PM -0800 References: <20010105183035.A23040@firedrake.org> <20010105104911.E15744@fw.wintelcom.net> <20010105195910.A27037@firedrake.org> <20010105121550.G15744@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 05, 2001 at 12:15:50PM -0800, Alfred Perlstein wrote: > > hmm, are you sure you have permission to do this? I'm root. > is 'username' your username? I tried su'ing to him, too. > What's the output of 'sysctl -a | grep sem'? # sysctl -a | grep sem kern.ipc.semmap: 31 kern.ipc.semmni: 200 kern.ipc.semmns: 600 kern.ipc.semmnu: 31 kern.ipc.semmsl: 150 kern.ipc.semopm: 101 kern.ipc.semume: 11 kern.ipc.semusz: 100 kern.ipc.semvmx: 32767 kern.ipc.semaem: 16384 p1003_1b.semaphores: 0 p1003_1b.sem_nsems_max: 0 p1003_1b.sem_value_max: 0 Here's another data point: the user just informed me that he's been deleting the shared memory segments in which the semaphores live *before* deleting the semaphores. Could this be the root of the problem? It seems like a silly thing to do, but at the same time, it probably shouldn't result in undeleteable semaphores. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010105202051.A27501>