From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10427 invoked by alias); 1 Jul 2012 18:17:54 -0000 Received: (qmail 10418 invoked by uid 22791); 1 Jul 2012 18:17:53 -0000 X-SWARE-Spam-Status: No, hits=-5.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-ee0-f43.google.com (HELO mail-ee0-f43.google.com) (74.125.83.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 01 Jul 2012 18:17:21 +0000 Received: by eeke50 with SMTP id e50so1847458eek.2 for ; Sun, 01 Jul 2012 11:17:20 -0700 (PDT) Received: by 10.14.99.202 with SMTP id x50mr2350121eef.19.1341166640449; Sun, 01 Jul 2012 11:17:20 -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 x52sm27115330eea.11.2012.07.01.11.17.19 (version=SSLv3 cipher=OTHER); Sun, 01 Jul 2012 11:17:20 -0700 (PDT) Message-ID: <4FF0942B.1030201@gmail.com> Date: Sun, 01 Jul 2012 18:17: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: Re: Persistence of file implemented objects References: <4FEF7DB6.6040101@gmail.com> <20120701003530.GA5390@ednor.casa.cgf.cx> In-Reply-To: <20120701003530.GA5390@ednor.casa.cgf.cx> 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-07/txt/msg00003.txt.bz2 > 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. Sorry, I meant unix/bsd sockets. Regarding the POSIX IPC's, they are stored in /dev . In regular *nix, /dev do not represent "physical" files on the filesystem, hence they do not persist over boot. In cygwin, they actually do represent physical files. So if they are not freed correctly by the program, the persist over to the next boot. -- 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