|
|
|
standard/accept(2) -- accept a connection on a socket
|
|
The argument s is a socket that has been created with socket(2), bound to an address with bind(2), and is listening for connections after a listen(2). Accept extracts the first connection on the queue of pending connections, creates a new socket with the same properties of s and allocates a new file descriptor for the socket. If no pending connections are present on the queue, and the socket is not marked as non-blocking, accept blocks the caller until a connection is present. If the socket is m... |
|
standard/access(2) -- determine accessibility of a file
|
|
path points to a path name naming a file. access checks the named file for accessibility according to the bit pattern contained in amode, using the real user ID in place of the effective user ID and the real group ID in place of the effective group ID. The bit pattern contained in amode is constructed by an OR of the following constants (defined in <unistd.h>): R_OK test for read permission W_OK test for write permission X_OK t... |
|
|
standard/acct(2) -- enable or disable process accounting
|
|
acct enables or disables the system process accounting routine. If the routine is enabled, an accounting record will be written in an accounting file for each process that terminates. The termination of a process can be caused by one of two things: an exit call or a signal [see exit(2) and signal(2)]. The calling process must have the capability CAP_ACCT_MGT (see capabilities(4) ) in its effective set to en... |
|
standard/adjtime(2) -- correct the time to allow synchronization of the system clock
|
|
adjtime adjusts the system's notion of the current time, as returned by gettimeofday(3C), advancing or retarding it by the amount of time specified in the struct timeval pointed to by delta. The adjustment is effected by speeding up (if that amount of time is positive) or slowing down (if that amount of time is negative) the system's clock by some small percentage, generally a fraction of one percen... |
|
standard/alarm(2) -- set a process alarm clock
|
|
alarm instructs the alarm clock of the calling process to send the signal SIGALRM to the calling process after the number of real time seconds specified by sec have elapsed [see signal(2)]. Alarm requests are not stacked; successive calls reset the alarm clock of the calling process. If sec is 0, any previously made alarm request is canceled. fork sets the alarm clock of a new process to 0 [see fork(2)]. A process crea... |
|
standard/arsctl(2) -- modify the behavior of array sessions
|
|
The arsctl function queries and/or modifies some aspect of the behavior of array sessions on the currently running system. Most of the array session control operations take some sort of argument. A pointer to the argument is passed as bufptr, and the length of the argument is specified with buflen. The particular operation to be performed is identified by the function code func, which is defined in . Available array session control operations include:... |
|
standard/arsop(2) -- perform an operation on an array session
|
|
The arsop function performs an operation on the array session identified by the handle ash. If ash is less than 0, then the operation is performed on the array session that is associated with the calling process. Most array session operations take some sort of argument. A pointer to the argument is passed as bufptr, and the length of the argument is specified with buflen. The particular operation to be performed is identified by the function code func, which is defined in . Availab... |
|
standard/attr_get(2) -- get the value of a user attribute of a filesystem object
|
|
The attr group of system calls implement the ability for a user to attach name/value pairs to objects within the filesystem. They could be used to store meta-information about the file. For example "character-set=kanji" could tell a document browser to use the Kanji character set when displaying that document and "thumbnail=..." could provide a reduced resolution overview of a high resolution graphic image. The names can be up to MAXNAMELEN bytes in length, terminated by the first 0 byte. Th... |
|
standard/attr_list(2) -- list the names of the user attributes of a filesystem object
|
|
The attr group of system calls implement the ability for a user to attach name/value pairs to objects within the filesystem. They could be used to store meta-information about the file. For example "character-set=kanji" could tell a document browser to use the Kanji character set when displaying that document and "thumbnail=..." could provide a reduced resolution overview of a high resolution graphic image. The names can be up to MAXNAMELEN bytes in length, terminated by the first 0 byte. Th... |
|
standard/attr_multi(2) -- manipulate multiple user attributes on a filesystem object at once
|
|
The attr group of system calls implement the ability for a user to attach name/value pairs to objects within the filesystem. They could be used to store meta-information about the file. For example "character-set=kanji" could tell a document browser to use the Kanji character set when displaying that document and "thumbnail=..." could provide a reduced resolution overview of a high resolution graphic image. The names can be up to MAXNAMELEN bytes in length, terminated by the first 0 byte. Th... |
|
standard/attr_remove(2) -- remove a user attribute of a filesystem object
|
|
The attr group of system calls implement the ability for a user to attach name/value pairs to objects within the filesystem. They could be used to store meta-information about the file. For example "character-set=kanji" could tell a document browser to use the Kanji character set when displaying that document and "thumbnail=..." could provide a reduced resolution overview of a high resolution graphic image. The names can be up to MAXNAMELEN bytes in length, terminated by the first 0 byte. Th... |
|
standard/attr_set(2) -- set the value of a user attribute of a filesystem object
|
|
The attr group of system calls implement the ability for a user to attach name/value pairs to objects within the filesystem. They could be used to store meta-information about the file. For example "character-set=kanji" could tell a document browser to use the Kanji character set when displaying that document and "thumbnail=..." could provide a reduced resolution overview of a high resolution graphic image. The names can be up to MAXNAMELEN bytes in length, terminated by the first 0 byte. Th... |
|
standard/bind(2) -- bind a name to a socket
|
|
Bind assigns a name to an unnamed socket. When a socket is created with socket(2) it exists in a name space (address family) but has no name assigned. Bind requests that name be assigned to the socket. The rules used in name binding vary between communication domains. Consult the protocol manual entries in section 7 for detailed information. |
|
standard/blockproc(2) -- routines to block/unblock processes
|
|
These routines provide a complete set of blocking/unblocking capabilities for processes. Blocking is implemented with a counting semaphore in the kernel. Each call to blockproc decrements the count. When the count becomes negative, the process is suspended. When unblockproc is called, the count is incremented. If the count becomes non-negative (>= 0), the process is restarted. This provides both a simple, race free synchronization ability between two processes and a much more powerful capability... |
|
standard/brk(2) -- change data segment space allocation
|
|
brk and sbrk are used to change dynamically the amount of space allocated for the calling process's data segment [see exec(2)]. The change is made by resetting the process's break value and allocating the appropriate amount of space. The break value is the address of the first location beyond the end of the data segment. The amount of allocated space increases as the break value increases. Newly allocated space is set to zero. If, however, the same memory space... |
