From nobody@FreeBSD.ORG Fri Mar 12 07:12:04 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id E0F56152AC; Fri, 12 Mar 1999 07:12:03 -0800 (PST)
Message-Id: <19990312151203.E0F56152AC@hub.freebsd.org>
Date: Fri, 12 Mar 1999 07:12:03 -0800 (PST)
From: jarvis@guru.wow.aust.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: can't run multiple instances of wine 310199
X-Send-Pr-Version: www-1.0

>Number:         10558
>Category:       ports
>Synopsis:       can't run multiple instances of wine 310199
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 12 07:20:00 PST 1999
>Closed-Date:    Sun Mar 14 16:47:18 PST 1999
>Last-Modified:  Sun Mar 14 16:50:25 PST 1999
>Originator:     Jarvis Cochrane
>Release:        2.2.7-RELEASE
>Organization:
Murdoch University
>Environment:
FreeBSD regpc30.murdoch.edu.au 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Wed Jan 1
3 17:28:08 WST 1999     root@regpc30.murdoch.edu.au:/usr/src/sys/compile/centrif
uge  i386
>Description:
One instance of a 'vanilla' build of the wine port runs fine.
When a second instance is started, the first instance exits - usually cleanly, and the second instance - usually- continues to run.
Have talked to Ulrich - one of the wine coders - about this, but he could not pin the problem down. 
He suggested that there might be an issue with IPC ( a semget - no space on device) message, or an (impossible!) issue with 2 user land processes interacting...
>How-To-Repeat:
Start a windows application under wine.
Start another (or the same) windows application under wine
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Sun Mar 14 16:47:18 PST 1999 
State-Changed-Why:  
I'm afraid since the maintainer of this port is on extended leave from the 
project we're not going to be able to fix this one without a patch.  I see 
that you talked to wine's authors which is where a fix is likely to come 
from if you don't work up a patch yourself.  If this is really an IPC problem 
this is not a ports-related issue. 
>Unformatted:
