Unix signal interruption behavior in server contexts

An arrangement for handling a signal received at a server context via a remote procedure call, said signal representing a request to employ a kernel service associated with said server context on behalf of one of a calling application code associated with a different application context and a calling kernel service associated with said different server context, comprising:

• a pseudo-handler signal action vector (SAV), said pseudo-handler SAV including a file of signal numbers and corresponding pseudo-handlers, each of said pseudo-handlers mimicking a handler address without being corresponded to a meaningful address;
• and
• means for consulting said pseudo-handler SAV to ascertain whether said signal corresponds to a pseudo-handler of said pseudo-handlers and for aborting a wait state of said kernel service if said signal corresponds to said pseudo-handler in said pseudo-handler SAV.

An article of manufacture comprising a program storage medium having computer readable code embodied therein, said computer readable code being configured to handle a signal received at an application context, said application context employing a first remote kernel service implemented on a first server context different from said application context, comprising:

• computer readable code for receiving at said first remote kernel service from said application context a first signal ascertaining, using a first signal action vector file associated with said first server context, a first action code associated with said first signal;
• and
• computer readable code for aborting, if said first action code represents a pseudo-handler, said first remote kernel service.