X-Recipient: archive-cygwin AT delorie DOT com 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=phZvb86+OpUWxOjB11KJWgknfxemOs/dGQnxTofNjKX +5JP4bQVgnYUWpuc8rPL+0r42GtHY5T0PR2b/DxKPPPDxpXw8C2bMPMPsJuaSCqs XF5rHzPHw1J5xnNyhvG7TUi4vNFYOz4XtJC0+bxba+mqwbJqoG8tSBpdeXueXDFI = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=oHcny2ZxWd2Py+n16hCkrHzcpl4=; b=yqwu+hNfNC1zBry05 tXMd9o9LIlXHDP1TNhgAZPjNgGzGXdPU7rZJJwrVAbglJIHW6fmar3BIf+fS6vES po3lMJveXNQIMri3SzBkKYL0yUmr8rERKJ7JE7k9fC6rIl1k2ia0cL6h0TeeSgK6 Z3QQLJt5XI1+0+MEF5oFAoYM+8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-bk0-f43.google.com X-Received: by 10.205.17.1 with SMTP id qa1mr2291933bkb.34.1395434613921; Fri, 21 Mar 2014 13:43:33 -0700 (PDT) Message-ID: <532CA456.4090805@gmail.com> Date: Fri, 21 Mar 2014 21:43:02 +0100 From: Marco Atzeri User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Does shared memory support work on cyg64? References: <532C11F5 DOT 5070205 AT tlinx DOT org> <532C1EBA DOT 4040806 AT gmail DOT com> <532C7955 DOT 2000800 AT tlinx DOT org> <532C7BD2 DOT 5030800 AT gmail DOT com> <532CA0DC DOT 60005 AT tlinx DOT org> In-Reply-To: <532CA0DC.60005@tlinx.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 21/03/2014 21:28, Linda Walsh wrote: > Marco Atzeri wrote: > > >> $ cygrunsrv -LV command given in 64 bit space >> Service : cygserver (Installation path: E:\cygwin) reporting that the 32 bit one is installed in another path/root than "cygrunsrv" >> 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 No installation path, so same path/root of "cygrunsrv" command >> 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? the base path/root for the two installations is different -- 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