X-Recipient: archive-cygwin AT delorie DOT com 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 Message-ID: <4FF0942B.1030201@gmail.com> Date: Sun, 01 Jul 2012 19:17:15 +0100 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 AT cygwin DOT com Subject: Re: Persistence of file implemented objects References: <4FEF7DB6 DOT 6040101 AT gmail DOT com> <20120701003530 DOT GA5390 AT ednor DOT casa DOT cgf DOT 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 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 > 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