This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Persistence of file implemented objects


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.

If there anyway to clear out orphaned objects or to make sure they are released in the event of an abnormal termination?

Does the POSIX specification even require the release of these objects in these situations?

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]