in reply to Re^8: Proposal how to make modules using fork more portable
in thread Proposal how to make modules using fork more portable

No, at least named pipes under \\.\pipe\... will get removed if the creating process exits. Or rather, the MSDN CreateNamedPipe documentation makes me hope so:

An instance of a named pipe is always deleted when the last handle to the instance of the named pipe is closed.

Together with the hope that the OS will clean up (and close) all handles created by a process, this means that a pipe should vanish once the creating process exits.

But other objects where the creator process is not the permanent owner will have that problem, yes.

Replies are listed 'Best First'.
Re^10: Proposal how to make modules using fork more portable
by BrowserUk (Patriarch) on Apr 02, 2011 at 12:27 UTC
    Together with the hope that the OS will clean up (and close) all handles created by a process, this means that a pipe should vanish once the creating process exits.

    Under normal operations, a named pipe server will DisconnectNamedPipe() any existing connections prior to exiting. If it doesn't do this because it is killed, then remote clients don't know the server has shut down and so may leave the connection open. Hence the pipe name will still exist in the namespace which can prevent the server restarting.

    At least that was the explanation given by a vendor for a product failure under NT4 several years ago. Dunno if it was an OS bug since fixed.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Meditations