Re: Persistence of file implemented objects

2012-07-02 Thread Corinna Vinschen
On Jul 1 19:17, 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. AF_UNIX/AF_LOCAL sockets are implemented on filesystem level as well

Re: Persistence of file implemented objects

2012-07-01 Thread Christopher Faylor
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 t

Re: Persistence of file implemented objects

2012-07-01 Thread Richard H Lee
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

Re: Persistence of file implemented objects

2012-06-30 Thread Christopher Faylor
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 t

Persistence of file implemented objects

2012-06-30 Thread Richard H Lee
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