delorie.com/archives/browse.cgi | search |
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: | U2FsdGVkX1/W9QgUwx3mDLonUvJihSFu |
Date: | Sun, 1 Jul 2012 19:35:18 -0400 |
From: | Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Persistence of file implemented objects |
Message-ID: | <20120701233518.GB10276@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> <20120701003530 DOT GA5390 AT ednor DOT casa DOT cgf DOT cx> <4FF0942B DOT 1030201 AT gmail DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <4FF0942B.1030201@gmail.com> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
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 Sun, Jul 01, 2012 at 07:17:15PM +0100, Richard H Lee wrote: >> 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. ...which also persist on linux. >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. what specific interface are you talking about which creates physical files in /dev? -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |