We've deprecated our version of SNMP:
Use a third-party solution instead.
The ability to: | Is controlled by: |
---|---|
Map fixed addresses | PROCMGR_AID_MAP_FIXED |
Map physical memory | PROCMGR_AID_MEM_PHYS |
Map memory as executable | PROCMGR_AID_PROT_EXEC |
Note that the O_ASYNC flag isn't currently supported.
The ability to: | Is controlled by: |
---|---|
Spawn new processes | PROCMGR_AID_SPAWN |
Set the group ID of the child process | PROCMGR_AID_SPAWN_SETGID |
Set the user ID of the child process | PROCMGR_AID_SPAWN_SETUID |
Create a new application ID for the child process | PROCMGR_AID_CHILD_NEWAPP |
If procnto was started with a -P option ending with s or S, out-of-range priority requests by default "saturate" at the maximum allowed value.
If procnto was started with a -P option ending with s or S, out-of-range priority requests by default "saturate" at the maximum allowed value.
If procnto was started with a -P option ending with s or S, out-of-range priority requests by default "saturate" at the maximum allowed value.
If you're setting an expiration time (i.e., you didn't specify TIMER_TOLERANCE), you can OR in TIMER_PRECISE to override any default tolerance that was set for the process.
The following functions must have cancellation points but weren't marked as having them in the documentation:
The following functions are defined by POSIX, are not permitted by POSIX to be cancellation points, but were marked as such in the documentation:
The following functions have cancellation points:
dup_filedes = dup2( filedes, filedes2 );
isn't necessarily the same as:
close( filedes2 ); dup_filedes = fcntl( filedes, F_DUPFD, filedes2 );