X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org X-Mail-Handler: MailHop Outbound by DynDNS X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18AVDiOFX2dwBO35cGZtb3/ Date: Sat, 30 Jun 2012 20:35:30 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Persistence of file implemented objects Message-ID: <20120701003530.GA5390@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4FEF7DB6 DOT 6040101 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FEF7DB6.6040101@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Sat, Jun 30, 2012 at 11:29:10PM +0100, Richard H Lee wrote: >Various objects like fifo pipes, POSIX IPC shared memory and semaphores >that are implemented through the filesystem in cygwin persist when the >program abnornally terminates. They also persist through reboots, which >is different to the behaviour on linux. This is also different with the >case of sysV IPC + cygserver on cygwin which clears after reboots. Please be more precise about what you are talking about. Fifos persist on reboot on Linux or Cygwin. They live on the filesystem. I don't see how POSIX IPC shared memory and semaphores could persist. cgf -- 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