ISCOVE%UTOROCI.bitnet@ugw.utcs.utoronto.ca (12/01/90)
Is there some undocumented feature of Exec or DOS which might remove a message port whose parent process has exited? I have tried the following: Process A creates a named public port (MP_FLAGS = PA_IGNORE, MP_SIGTASK = Process A or 0), attaches a message to it (MN_REPLYPORT = 0), and then exits back to the CLI without removing the port. Process B is then run from the CLI, looks for the named port (Forbid - FindPort - Permit), retrieves the message (WaitPort), uses the information, and then exits. Process B can be run repeatedly. Basically, this seems to work, except that after running B a few times from the CLI, then doing something else from the CLI such as listing a floppy directory, then running Process B again, it now fails to find the named port, requiring Process A to re-install it. Anyone know what's going on? Norman Iscove iscove@utoroci.bitnet