Abstract: A method, system, and computer program product for implementing inter-process integrity serialization services is provided. The method includes enabling process states including a must-stay-controlled (MSC) state and an extended must-stay-controlled (EMSC) state for an invoking process when it is determined that only programs designated as controlled, if any, have been loaded for the invoking process. The invoking process requests loading of a target program into temporary storage for performing a security service. Based upon a control indicator of the target program, the MSC state, and the EMSC state, the method includes controlling one or more activities within the temporary storage. The activities include loading the target program into the temporary storage, executing a main program in the temporary storage, and resetting the MSC state and the EMSC state across execution of the main program during the lifetime of the invoking process.

Abstract: A multi-identity security environment is created for use in controlling access to resources. The multi-identity security environment enables one process that is spawned by another process to access resources security accessible to the one process, as well as resources security accessible to the another process. The multi-identity security environment includes an identity of the one process and an identity of the another process.

Abstract: A method, system, and computer program product for implementing inter-process integrity serialization services is provided. The method includes enabling process states including a must-stay-controlled (MSC) state and an extended must-stay-controlled (EMSC) state for an invoking process when it is determined that only programs designated as controlled, if any, have been loaded for the invoking process. The invoking process requests loading of a target program into temporary storage for performing a security service. Based upon a control indicator of the target program, the MSC state, and the EMSC state, the method includes controlling one or more activities within the temporary storage. The activities include loading the target program into the temporary storage, executing a main program in the temporary storage, and resetting the MSC state and the EMSC state across execution of the main program during the lifetime of the invoking process.

Abstract: A method for managing the suspension and resumption of threads on an individual basis in an information handling system having an operating system (OS) kernel and a user process having multiple threads of execution. An originating thread issues a pthread_kill( ) service request to the OS kernel to send a specified signal (thread-stop or thread-continue) to a specified target thread within the same process to suspend or resume execution of the target thread. More particularly, in response to a request from a thread to suspend the execution of the target thread, the OS kernel sends a thread-stop signal (SIGTHSTOP) to the target thread, transferring control within the target thread from a normally executing program portion to a signal interrupt routine. Upon gaining control, the signal interrupt routine issues a service request to the kernel to stop the target thread.

Abstract: A method and apparatus for ensuring that a process interacting with a failing process is notified of the failure of that process. Each process has a unique process identifier (PID) associated with it. Each process optionally has an affinity list containing one or more entries, each of which contains the identifier of a process that is to be notified when the process fails. A process updates the affinity list of a target process (either itself or another process) by calling an affinity service of the operating system (OS) kernel, specifying the type of operation (add or delete), the identifier of the target process, the identifier of the process that is to notified, and the type of event that is to be generated for the process that is to be notified. When a process fails, a process termination service of the OS kernel examines the affinity list of the failing process and, for each entry in the list, generates an event of the specified type for the process specified as to be notified.

Abstract: A method for managing the suspension and resumption of threads on an individual basis in an information handling system having an operating system (OS) kernel and a user process having multiple threads of execution. An originating thread issues a pthread_kill( ) service request to the OS kernel to send a specified signal (thread-stop or thread-continue) to a specified target thread within the same process to suspend or resume execution of the target thread. More particularly, in response to a request from a thread to suspend the execution of the target thread, the OS kernel sends a thread-stop signal (SIGTHSTOP) to the target thread, transferring control within the target thread from a normally executing program portion to a signal interrupt routine. Upon gaining control, the signal interrupt routine issues a service request to the kernel to stop the target thread.

Abstract: A method and apparatus for managing a resource in an information handling system in which one or more processes are utilizing the resource. The current utilization of the resource is determined and compared with a predetermined maximum utilization set for the resource, either for the system as a whole or for a particular process executing on the system. A message is generated if the current utilization of the resource reaches any one of a plurality of predetermined fractional thresholds relative to the predetermined maximum utilization set for the resource. An operator command allows the messages to be displayed for all resources or just for system-wide resources, or to be suppressed entirely. Another operator command allows the operator to obtain a display of current resource utilization, the peak (“high water”) utilization since the last reset, and the maximum resource utilization, either for the system as a whole or for a particular process.

Abstract: In a client/server system, a method and apparatus for a listening daemon to distribute work and client connectivity across multiple processes each supporting multiple threads. Upon receiving a request from a client, a listening daemonaccepts the conversation, thus creating a socket. The listening daemon then does a putwork( ) call which places a work request on a system managed work queue. The work request behaves in a manner very similar to spawn in that it provides for parameters to be passed as well as transfer of ownership of the socket. In the meantime, server processes that are created either manually or by the operating system create multiple threads, which invoke a getwork( ) service to retrieve work requests created by the listening daemon. The getwork( ) service transfers the socket to the calling process and notifies the thread which file descriptors it has inherited.

Abstract: A method and apparatus for controlling the assignment of units of work to workload enclaves in a client/server system in which units of work are organized into enclaves with the units of work in each enclave being managed as a single entity. Incoming work requests are queued for processing by one or more worker threads of one or more server processes. In response to the receipt of an incoming work request, a putwork() service of the operating system kernel defines an workload enclave for the work request and adds the work request to a queue of incoming work requests to enqueue the request. In response to a request from a worker thread for more work, a getwork() service of the operating system kernel removes a work request from the queue to dequeue the request and associates the worker thread with the enclave defined for the request.

Abstract: A method of controlling the execution of the threads of a first application such as a user application from a second application such as a debugger application running in a different address space. After initializing trace mode for the user application, the debugger waits for an event to occur on one of the threads of the user application. Upon the occurrence of an event on one of the user application threads, an event handler obtains control of the thread execution. The event handler suspends execution of the remaining threads in the application, posts the debugger and then suspends its own execution. When the debugger application has completed its debugging operations, it posts the event handler, which resumes execution of the suspended threads and returns control to the thread on which the event occurred.

Abstract: A universal injection molding system has plural pairs of mold inserts that are engageable for mold cavities mounted on mold bases, respectively, on the relatively movable top clamp plate and base support plate of an injection molding machine. Rails on those bases hold the mold inserts in place in paired alignment. With the plates and bases closed to bring together respective mold insert pairs, the mold inserts are securely clamped in relatively fixed positions on the plates and bases. A multiple stage ejecting/stripping apparatus also is provided to strip parts from mold cavities, and a technique is provided to eject the sprue before the parts. Methods of facilitating set-up of an injection molding system and of injection molding also are disclosed.