From owner-freebsd-hackers Tue Jul 8 08:40:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22938 for hackers-outgoing; Tue, 8 Jul 1997 08:40:14 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA22927 for ; Tue, 8 Jul 1997 08:40:11 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id KAA04638; Tue, 8 Jul 1997 10:39:49 -0500 (EST) Date: Tue, 8 Jul 1997 10:39:49 -0500 (EST) From: John Fieber To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: <19970708091450.QL25215@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Jul 1997, J Wunsch wrote: > Even SYSVSEM is arguable, i think the only `canned' application that > uses them is PEX. (Who uses PEX, anyway? :) Wine seems to use them, and I think postgresql must because wine allocates bunches of semaphores but doesn't release them, and postgresql fails if wine has been run until you manually ipcrm the semaphors that wine left hanging around.... Postgresql definately uses SYSVSHM. -john