Date: Sat, 30 Jun 2012 20:35:30 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Persistence of file implemented objects
Message-ID: <20120701003530.GA5390@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <4FEF7DB6.6040101@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4FEF7DB6.6040101@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 Sat, Jun 30, 2012 at 11:29:10PM +0100, Richard H Lee wrote:
>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.

Please be more precise about what you are talking about.

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.

cgf

--
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