|
|
|
usnewsema(3p) -- allocate and initialize a semaphore
|
|
usnewsema allocates a semaphore and initializes its count to the value specified by val. Initially, metering and debugging are off (and can be turned on through a call to usctlsema(3P)) and the history logging mechanism is set according to the global setting (see usconfig(3P)). The semaphore is allocated from the shared arena designated by handle as returned from usinit(3P). A semaphore allocated via usnewsema is a blocking semaphore - if the semaphore is unavailable, the caller will block. A po... |
|
usopenpollsema(3p) -- attach a file descriptor to a pollable semaphore
|
|
usopenpollsema attaches a file descriptor to a pollable semaphore. The returned file descriptor is used when calling poll(2) or select(2) to acquire the semaphore after an unsuccessful uspsema(3P). If the caller is the first process to call usopenpollsema on sema then a new semaphore device is allocated (see usema(7M)). The user and group id of the semaphore device take on the effective user/group id of the caller. The access mode is set to acc(see chmod(2)). Calls to usopenpollsema on the same ... |
|
|
uspsema(3p) -- acquire a semaphore
|
|
uspsema decrements the count of the previously allocated semaphore specified by sema. If the count is then negative, the semaphore will logically block the calling process until the count is incremented due to a usvsema(3P) call made by another process. The count can be interpreted in the following way: if it is greater than zero, there are 'count' resources available, namely 'count' processes can call uspsema and not block; if the count is negative then the absolute value of count is the nu... |
|
ftn/ussetlock(3p) -- spinlock routines
|
|
This set of routines provide a standard test and set facility. If the lock is free then it is atomically locked, and control is returned to the caller. If the lock is already locked, the caller either spins waiting for the lock or gets queued. The locks are based in user address space thus avoiding any system call overhead in the case where the lock is available. The actual algorithm used to implement these functions depends on whether the system is a multiprocessor or a single processor. In the... |
|
ussetlock(3p) -- spinlock routines
|
|
This set of routines provide a standard test and set facility. If the lock is free then it is atomically locked, and control is returned to the caller. If the lock is already locked, the caller either spins waiting for the lock or gets queued. The locks are based in user address space thus avoiding any system call overhead in the case where the lock is available. The actual algorithm used to implement these functions depends on whether the system is a multiprocessor or a single processor. In the... |
|
ustestsema(3p) -- return the value of a semaphore
|
|
ustestsema returns the current value of the semaphore specified by sema. This should be viewed as a snapshot only, useful for debugging. |
|
usvsema(3p) -- release a semaphore
|
|
usvsema increments the count associated with sema. If there are any processes queued waiting for the semaphore the first one is awakened. usvsema uses the usema(7M) device to reactivate a suspended process. If the process to be awoken is no longer alive, usvsema will automatically attempt to awaken the next process waiting for the semaphore. In order to use a semaphore, the caller must have joined the shared arena out of which the semaphore is allocated (via usinit(3P)), and have a file descript... |
|
utimes(3c) -- set file times
|
|
The utimes call uses the "accessed" and "updated" times in that order from the tvp vector to set the corresponding recorded times for file. The caller must be the owner of the file or the super-user. The "inodechanged" time of the file is set to the current time. This routine emulates the 4.3BSD utimes system call. |
|
uuid(3c) -- Universal Unique Identifier functions
|
|
Universal Unique Identifiers are bit strings that may be generated independently on separate nodes (hosts) such that globally unique strings result without requiring the hosts to be in communication with each other to ensure uniqueness. They are a component of DCE that have been independently reimplemented in IRIX, but is in accordance with the DCE specification. This implementation is API compatible with the DCE implementation. The status parameter in all functions is set to uuid_s_ok if the fu... |
|
standard/v(3) -- transfers a
|
|
vector expects a 2, 3, or 4 element array, depending on whether you call the v2, v3, or v4 version of the routine. The elements of the array are the coordinates of the vertex (point) that you want to transfer to the graphics pipe. Put the x coordinate in element 0, the y coordinate in element 1, the z coordinate in element 2 (for v3 and v4), and the w coordinate in element 3 (for v4). |
|
validateproj(3c) -- validate a project name for a user
|
|
The validateproj function checks to see if user user is authorized for project proj. If so, the project ID corresponding to proj is returned. The fvalidateproj function is a variant of validateproj that uses a PROJ token to make it more efficient for repeated use. Otherwise its operation is identical. For more details on creating a PROJ token, see openproj(3C). |
|
ftn/varargs(3) -- allow variable number of arguments in argument list
|
|
These utilities are used to provide f77 support for subroutines with variable number of arguments. In order to use these utilities, all variable argument subroutines must be declared in each source file before they are referenced or defined. This is done by adding a $varargs compiler directive at the beginning of the source file. For example: $varargs vasub1 vasub2 vasub3 where vasub1, vasub2, and vasub3 are the names of the variable argument subroutines which are referenced or defined in the cu... |
|
perl5/vars(3) -- Perl pragma to predeclare global variable names
|
|
This will predeclare all the variables whose names are in the list, allowing you to use them under "use strict", and disabling any typo warnings. Unlike pragmas that affect the $^H hints variable, the use vars and use subs declarations are not BLOCK-scoped. They are thus effective for the entire file in which they appear. You may not rescind such declarations with no vars or no subs. Packages such as the AutoLoader and SelfLoader that delay loading of subroutines within packages can create pro... |
|
f90/verify(3) -- Verifies that a set of characters contains all characters in a string
|
|
UNICOS, UNICOS/mk, and IRIX systems |
|
standard/videocmd(3) -- initiates a command transfer sequence on a video peripheral
|
|
cmd expects a command value which initiates a command transfer sequence on a video peripheral. The valid command tokens are: VP_INITNTSC_COMP initialize the Live Video Digitizer for a composite NTSC video source. VP_INITNTSC_RGB initialize the Live Video Digitizer for a RGB NTSC video source. VP_INITPAL_COMP initialize the Live Video Digitizer for a composite PAL video source. VP_INITPAL_RGB initialize the Live Video Digitizer for a RGB PAL video source.... |
