DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=snOpn79XJ6Iutyq47If8jC9jEpTKZxf0UGZFGi407PA
	rR9bzohDUOy9N4Uma0faX3YBg+YLvCems9CouZpvDyBtaipZ+losKAi4+HUMVn2a
	//gQi6eyRqysMHdQh2mghRCdqW1UsOFB+kOlUZTfw6SbsKiGXmmvVrIfCpvQh1mA
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <532CA0DC.60005@tlinx.org>
Date: Fri, 21 Mar 2014 13:28:12 -0700
From: Linda Walsh <cygwin@tlinx.org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Does shared memory support work on cyg64?
References: <532C11F5.5070205@tlinx.org> <532C1EBA.4040806@gmail.com> <532C7955.2000800@tlinx.org> <532C7BD2.5030800@gmail.com>
In-Reply-To: <532C7BD2.5030800@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Marco Atzeri wrote:
> as the script creates a service called "cygserver"
> running both the 32bit and the 64 bit scripts
> causes the second to overwrite/overlap the first.
> 
> On my system I manually renamed the 64 one
> to avoid collision and to allow to start them separately
----
Ahh...I see..

In my case, I'm not running them at the same time as I use
it to drive my X server -- and generally, I only have one of those
running at a time...

I guess what I don't know is how the Xserver -- especially in your
case, knows where to find the shared memory segment.


> $ cygrunsrv -LV
> Service             : cygserver           (Installation path: E:\cygwin)
> Display name        : CYGWIN cygserver
> Current State       : Stopped
> Command             : /usr/sbin/cygserver
> stdin path          : /dev/null
> stdout path         : /var/log/cygserver.log
> stderr path         : /var/log/cygserver.log
> Process Type        : Own Process
> Startup             : Manual
> Account             : LocalSystem
> 
> Service             : cygserver64
> Display name        : CYGWIN cygserver64
> Current State       : Running
> Controls Accepted   : Stop
> Command             : /usr/sbin/cygserver
> stdin path          : /dev/null
> stdout path         : /var/log/cygserver64.log
> stderr path         : /var/log/cygserver64.log
> Process Type        : Own Process
> Startup             : Manual
> Account             : LocalSystem
------
Now you have me curious -- how do you have the 1 cygrunsrv command
listing both a 32-bit version and a 64-bit version?

Wouldn't the cygrunsrv just list the the services in the same
bit-class?

So... just from the above -- it looks like your 32bit and 64-bit
are running the same binary -- i.e. from the view of
cygrunsrv....am I missing something?


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple