Restartable processes, just like traditional ChorusOS processes, are identified in the system by a unique capability and PID. Restartable processes also run in a user group (with a user ID) like traditional ChorusOS processes. The life of each of these credentials is the same as the life of a specific run-time instance of the process -- when a restartable process is restarted, it is given a new capability, PID and user ID.
Hot restartable processes also have two additional credentials which persist across a process restart, and characterize the processes in the Hot Restart Controller:
Each restartable process has a unique name.
The maximum number of restartable processes (unique names) that can be registered
in the Hot Restart Controller is fixed by the hrCtrl.maxprocesses
system parameter.
It is the programmer's responsibility to ensure that each process running in the system uses a unique name because this is not checked by the system. Attempting to run two processes that use the same name will cause unpredictable results.
Each restartable process is a member of a restart group. A restart group is uniquely identified in the system by an integer (known as the group's ID). The maximum number of group IDs in a system is fixed by the hrCtrl.maxGroups parameter.