Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 1 Feb 2002 20:49:12 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygipc shmat bug Message-ID: <20020202014912.GC6842@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3C5937FE DOT C87567DD AT salomon DOT at> <3C59465A DOT 65EBEF58 AT salomon DOT at> <024e01c1ab6e$2a04e280$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <024e01c1ab6e$2a04e280$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Sat, Feb 02, 2002 at 09:16:57AM +1100, Robert Collins wrote: >From: "Michael Haubenwallner" >>The problem is, that the pid-numbering of Windows is quite "confuse" (i >>don't know any better word), meaning that a later ipctest.exe gets the >>same pid as before, while the attach before with the same pid is not >>removed from the list yet. > >So don't test by PID, test by handle. IIRC I've already suggested >that. Also, IIRC (Chris, Corinna you may have encountered evidence >about this) if you have a handle open for a process, it's PID isn't >recycled until all the handles have been closed). That's correct. Cygwin relies on that behavior, in fact. In case it isn't obvious, Cygwin uses windows pids, which can be recycled rapidly. Relying on any specific behavior for PID numbers is really not a good idea, even on UNIX. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/