From: Richard H Lee <ricardohenrylee@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Persistence of file implemented objects
Date: Sun, 01 Jul 2012 18:17:00 -0000 [thread overview]
Message-ID: <4FF0942B.1030201@gmail.com> (raw)
In-Reply-To: <20120701003530.GA5390@ednor.casa.cgf.cx>
> 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
next prev parent reply other threads:[~2012-07-01 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 22:29 Richard H Lee
2012-07-01 0:35 ` Christopher Faylor
2012-07-01 18:17 ` Richard H Lee [this message]
2012-07-01 23:35 ` Christopher Faylor
2012-07-02 8:03 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FF0942B.1030201@gmail.com \
--to=ricardohenrylee@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).