|
|
|
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... |
|
standard/cachectl(2) -- mark pages cacheable or uncacheable
|
|
The cachectl system call allows a process to make ranges of its address space cacheable or uncacheable. Initially, a process's entire address space is cacheable. The op parameter may be one of: CACHEABLE Make the indicated pages cacheable UNCACHEABLE Make the indicated pages uncacheable The CACHEABLE and UNCACHEABLE op's affect the address range indicated by addr and nbytes. addr must be page aligned and nbytes must be a multiple of the page size. Changing a page from UNCACHEABLE state to CACH... |
|
standard/cacheflush(2) -- flush contents of instruction and/or data cache
|
|
cacheflush and _flush_cache are different names for the same function. They flush the contents of the indicated cache(s) for user addresses in the range addr to (addr+nbytes-1). The cache parameter may be one of: ICACHE Flush only the instruction cache DCACHE Flush only the data cache BCACHE Flush both the instruction and the data cache |
|
standard/chdir(2) -- change working directory
|
|
chdir and fchdir cause a directory pointed to by path or fildes to become the current working directory, the starting point for path searches for path names not beginning with /. path points to the path name of a directory. The fildes argument to fchdir is an open file descriptor of a directory. In order for a directory to become the current directory, a process must have execute (search) access to the directory. chdir will fai... |
|
standard/chmod(2) -- change mode of file
|
|
chmod and fchmod set the access permission portion of the mode of the file whose name is given by path or referenced by the descriptor fildes to the bit pattern contained in mode. If path or fildes are symbolic links, the access permissions of the target of the symbolic links are set. Access permission bits are interpreted as follows: S_ISUID 04000 Set user ID on execution. S_ISGID 020#0 Set group ID on execution if # is 7, ... |
