Consider the following issues when writing your application:
The resource control block is opaque. The control block must be dynamically allocated.
If a basic resource control with local signal action is established on a process or task by setrctl, the process that established this resource control becomes the recipient process, unless the caller set it explicitly by rctlblk_set_recipient_pid. The signal action for this resource control block is applied to the recipient PID (observer). However, some resources cannot be observed in this way.
For more information, see the description for the flag RCTL_GLOBAL_UNOBSERVABLE in the rctlblk_set_value(3C) man page.
Only the basic rctl with local signal action has a recipient process.
If a privileged resource control is set, no recipient PID process exists. However, any process that violates the limit becomes the subject of the resource control action.
Only one basic rctl is allowed per process or task per resource control.