From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9248 invoked by alias); 30 Jun 2012 22:29:28 -0000 Received: (qmail 9238 invoked by uid 22791); 30 Jun 2012 22:29:27 -0000 X-SWARE-Spam-Status: No, hits=-4.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-we0-f171.google.com (HELO mail-we0-f171.google.com) (74.125.82.171) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 30 Jun 2012 22:29:15 +0000 Received: by wejx9 with SMTP id x9so3142469wej.2 for ; Sat, 30 Jun 2012 15:29:14 -0700 (PDT) Received: by 10.180.104.168 with SMTP id gf8mr7049165wib.12.1341095353929; Sat, 30 Jun 2012 15:29:13 -0700 (PDT) Received: from [192.168.1.136] (87-194-63-158.bethere.co.uk. [87.194.63.158]) by mx.google.com with ESMTPS id eu4sm14888792wib.2.2012.06.30.15.29.12 (version=SSLv3 cipher=OTHER); Sat, 30 Jun 2012 15:29:13 -0700 (PDT) Message-ID: <4FEF7DB6.6040101@gmail.com> Date: Sat, 30 Jun 2012 22:29:00 -0000 From: Richard H Lee User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Persistence of file implemented objects Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-06/txt/msg00579.txt.bz2 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. If there anyway to clear out orphaned objects or to make sure they are released in the event of an abnormal termination? Does the POSIX specification even require the release of these objects in these situations? -- 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