Date: Sun, 1 Jul 2012 19:35:18 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Persistence of file implemented objects
Message-ID: <20120701233518.GB10276@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <4FEF7DB6.6040101@gmail.com> <20120701003530.GA5390@ednor.casa.cgf.cx> <4FF0942B.1030201@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4FF0942B.1030201@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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