|
|
|
standard/satread(2) -- read a block of audit record data
|
|
satread attempts to read nbytes bytes from the security audit trail record queue into the buffer pointed to by buffer. satread destroys the data that has been read. A subsequent satread call will read new and different data. |
|
standard/satwrite(2) -- write a block of audit record data
|
|
satwrite writes nbytes bytes to the security audit trail record queue from the buffer pointed to by buffer. satvwrite is a more convenient libc interface for generating audit records, which are generally text strings. Format is a printf-like format string, followed by a variable number of arguments. See printf(3S) for more information on the possible formatting characters. Event must be equal to one of the SAT record type constants for administrative events, as defined in /usr/include/sys/sat.h.... |
|
|
standard/schedctl(2) -- scheduler control call
|
|
This system call is used to alter scheduling parameters of either individual processes or of the system as a whole. The following commands are supported: |
|
standard/sched_getparam(2) -- get the scheduling parameters of a process
|
|
The sched_getparam system call is used to get the scheduling parameters for the process specified by pid. If pid is set to zero, then the scheduling parameters of the calling process will be obtained. A process may obtain the scheduling parameters of itself and any process sharing the same real user ID [see getuid(2)]. To obtain the scheduling parameters of an unrelated process, the calling process must have the CAP_SCHED_MGT capability [s... |
|
standard/sched_getscheduler(2) -- get the scheduling policy of a process
|
|
The sched_getscheduler system call is used to get the scheduling policy of the process specified by pid. If pid is set to zero, then the scheduling policy of the caller is returned. A process may obtain the scheduling policy of itself and any process sharing the same real user ID [see getuid(2)]. To obtain the scheduling policy of an unrelated process, the calling process must have the CAP_SCHED_MGT capability [see capability].... |
|
standard/sched_get_priority_max(2) -- get scheduling policy priority range
|
|
sched_get_priority_max and sched_get_priority_min return the maximum and minimum priority values, respectively, for the specified scheduling policy: |
|
standard/sched_rr_get_interval(2) -- get round robin scheduling interval
|
|
sched_rr_get_interval stores the round robin scheduling interval at address interval for the process named by pid. If pid is set to zero, then sched_rr_get_interval obtains the interval for the calling process. sched_rr_get_interval will fail if one or more of the following are true: [EFAULT] The address specified by interval is outside... |
|
standard/sched_setparam(2) -- set the scheduling parameters of a process
|
|
The sched_setparam system call is used to set the scheduling policy parameters for the process specified by pid. If pid is set to zero, then the scheduling parameters of the calling process will be affected. The scheduling parameters of pid are specified by the parameter structure at address param. The priority of the target process may be modified by setting the desired priority value in the sched_priority field of the param structure. Unlike IRIX 6.2 and ... |
|
standard/sched_setscheduler(2) -- set the scheduling policy of a process
|
|
The sched_setscheduler system call is used to set the scheduling policy and related parameters for the process specified by pid. If pid is set to zero, then the scheduling policy and parameters of the calling process will be affected. The policy parameter is used to select one of the following scheduling policies: |
|
standard/sched_yield(2) -- yield the processor
|
|
The sched_yield system call causes the calling process to relinquish the processor to a runnable process of higher or equal priority. In the event a higher or equal priority process is not available, the calling process reacquires control of the processor. |
|
standard/select(2) -- synchronous I/O multiplexing
|
|
Select examines the I/O descriptor sets whose addresses are passed in readfds, writefds, and exceptfds to see if some of their descriptors are ready for reading, are ready for writing, or have an exceptional condition pending, respectively. The first nfds file descriptors are checked in each set; i.e. the file descriptors from 0 through nfds - 1 will be examined (see getdtablehi(3) for largest open descriptor). On return, select replaces the given descriptor sets... |
|
standard/semctl(2) -- semaphore control operations
|
|
semctl provides a variety of semaphore control operations as specified by cmd. The following cmds are executed with respect to the semaphore specified by semid and semnum: GETVAL Return the value of semval [see intro(2)]. {READ} SETVAL Set the value of semval to arg.val. {ALTER}. When this command is successfully executed, the semadj value corresponding to the speci... |
|
standard/semget(2) -- get set of semaphores
|
|
semget returns the semaphore identifier associated with key. A semaphore identifier and associated data structure and set containing nsems semaphores [see intro(2)] are created for key if one of the following is true: key is equal to IPC_PRIVATE. key does not already have a semaphore identifier associated with it, and (semflg&IPC_CREAT) is true. On creation, the data structure associated with the new semaph... |
|
standard/semop(2) -- semaphore operations
|
|
semop is used to perform atomically an array of semaphore operations on the set of semaphores associated with the semaphore identifier specified by semid. sops is a pointer to the array of semaphore-operation structures. nsops is the number of such structures in the array. The contents of each structure includes the following members: short sem_num; /* semaphore number */ shor<... |
|
standard/send(2) -- send a message from a socket
|
|
Send, sendto, and sendmsg are used to transmit a message to another socket. Send may be used only when the socket is in a connected state, while sendto and sendmsg may be used when the socket is unconnected. The address of the target is given by to with tolen specifying its size. The length of the message is given by len. If the message is too long to pass atomically through the underlying protocol, then the error EMSGSIZE is returned, and the message is not transmitted. Usually no indication of... |
