From owner-freebsd-hackers Wed Feb 10 22:28:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29933 for freebsd-hackers-outgoing; Wed, 10 Feb 1999 22:28:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29928 for ; Wed, 10 Feb 1999 22:27:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id WAA88637; Wed, 10 Feb 1999 22:26:56 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Feb 1999 22:26:56 -0800 (PST) From: Matthew Dillon Message-Id: <199902110626.WAA88637@apollo.backplane.com> To: Peter Jeremy Cc: tlambert@primenet.com, hackers@FreeBSD.ORG Subject: Re: portability of shm, mmap, pipes and socket IPC References: <99Feb11.122748est.40371@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :they have on applications using SysV semaphores. : :I have an application (running on 3.0-RELEASE) that relies on the :kernel correctly tracking SEM_UNDO's. (Basically I have a wrapper :that seizes a semaphore with sem_op = -1, sem_flg = SEM_UNDO and then :execs a process that knows nothing about the semaphores.) I was :seeing some wierd behaviour, but I thought that was a (now fixed) bug :in the kernel handling of SEMUME and SEMUSZ (see PR kern/9068). : :Peter I think the key issue here is to be able to reproduce the weird behavior deterministically. If that can be done, the problem can be fixed fairly easily. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message