| Skip Navigation Links | |
| Exit Print View | |
 | man pages section 3: Library Interfaces and Headers Oracle Solaris 11 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
| man pages section 3: Library Interfaces and Headers Oracle Solaris 11 Information Library |
Library Interfaces and Headers
SMHBA_GetAdapterAttributes(3LIB)
SMHBA_GetAdapterPortAttributes(3LIB)
SMHBA_GetBindingCapability(3LIB)
SMHBA_GetDiscoveredPortAttributes(3LIB)
SMHBA_GetFCPhyAttributes(3LIB)
SMHBA_GetPersistentBinding(3LIB)
SMHBA_GetPortAttributesByWWN(3LIB)
SMHBA_GetProtocolStatistics(3LIB)
SMHBA_GetSASPhyAttributes(3LIB)
SMHBA_GetVendorLibraryAttributes(3LIB)
SMHBA_GetWrapperLibraryAttributes(3LIB)
SMHBA_RegisterForAdapterAddEvents(3LIB)
SMHBA_RegisterForAdapterEvents(3LIB)
SMHBA_RegisterForAdapterPhyStatEvents(3LIB)
SMHBA_RegisterForAdapterPortEvents(3LIB)
SMHBA_RegisterForAdapterPortStatEvents(3LIB)
SMHBA_RegisterForTargetEvents(3LIB)
SMHBA_RemoveAllPersistentBindings(3LIB)
SMHBA_RemovePersistentBinding(3LIB)
- implementation-defined constants
#include <limits.h>
The <limits.h> header defines various symbolic names. Different categories of names aredescribed below.
The names represent various limits on resources that the implementation imposes onapplications. Symbolic constant names beginning with _POSIX can be found inunistd.h(3HEAD).
Applications should not assume any particular value for a limit. An applicationwishing to avail itself of the full amount of a resource availableon an implementation can make use of the value given in limits.hon that particular implementation by using the symbolic names listed below. Manyof the listed limits are not invariant, and at runtime, the value ofthe limit might differ from those given in this header, for thefollowing reasons:
The limit is pathname-dependent.
The limit differs between the compile and runtime machines.
For these reasons, an application can use thefpathconf(2),pathconf(2), andsysconf(3C)functions to determine the actual value of a limit at runtime.
Maximum number of I/O operations in a single list I/O call supported by the implementation.
Maximum number of outstanding asynchronous I/O operations supported by the implementation.
The maximum amount by which a process can decrease its asynchronous I/O priority level from its own scheduling priority.
Maximum length of argument to theexec(2) functions including environment data.
Maximum number of functions that can be registered withatexit(3C).
Maximum number of simultaneous processes per real user ID.
Number of clock ticks per second returned by thetimes(2) function.
Maximum number of timer expiration overruns.
Maximum length of a host name (not including the terminating null) as returned from thegethostname(3C) function.
Maximum number ofiovec structures that one process has available for use withread(2) orwrite(2).
Maximum length of a login name.
The maximum number of open message queue descriptors a process is allowed to hold.
Maximum length of a login name.
The maximum number of open message queue descriptors a process is allowed to hold.
The maximum number of message priorities supported by the implementation.
Maximum number of files that one process can have open at any one time.
Size in bytes of a page.
Equivalent toPAGESIZE. If eitherPAGESIZE orPAGE_SIZE is defined, the other is defined with the same value.
The maximum number of significant bytes in a password, not including the terminating null.
Maximum number of attempts made to destroy a thread's thread-specific data values on thread exit.
Maximum number of data keys that can be created by a process.
Minimum size in bytes of thread stack storage.
Maximum number of threads that can be created per process.
The number of repeated occurrences of a BRE permitted by theregexec(3C) andregcomp(3C) functions when using the interval notation {\(m,n\}.
Maximum number of realtime signals reserved for application use in this implementation.
Maximum number of semaphores that a process can have.
The maximum value a semaphore can have.
Maximum number of queued signals that a process can send and have pending at the receiver(s) at any time.
The maximum number of replenishment operations that may be simultaneously pending for a particular sporadic server scheduler.
The number of streams that one process can have open at one time. If defined, it has the same value asFOPEN_MAX.
Maximum number of symbolic links that can be reliably traversed in the resolution of a pathname in the absence of a loop.
Maximum number of timers per process supported by the implementation.
Maximum length of the trace event name.
Maximum length of the trace generation version string or of the trace stream name.
Maximum number of trace streams that may simultaneously exist in the system.
Maximum number of user trace event type identifiers that may simultaneously exist in a traced process, including the predefined user trace eventPOSIX_TRACE_UNNAMED_USER_EVENT.
Maximum length of terminal device name.
Maximum number of bytes supported for the name of a timezone (not of the TZ variable).
The values in the following list can be constants within an implementationor can vary from one pathname to another. For example, file systemsor directories can have different characteristics. The value supported for a specificpathname is provided by thepathconf(2) function.
Minimum number of bits needed to represent, as a signed integer value, the maximum size of a regular file allowed in the specified directory.
Maximum number of links to a single file.
Maximum number of bytes in a terminal canonical input line.
Minimum number of bytes for which space is available in a terminal input queue; therefore, the maximum number of bytes a conforming application may require to be typed as input before reading them.
Maximum number of bytes in a filename (not including terminating null).
Maximum number of bytes in a pathname, including the terminating null character.
Maximum number of bytes that is guaranteed to be atomic when writing to a pipe.
Minimum number of bytes of storage actually allocated for any portion of a file.
Recommended increment for file transfer sizes between thePOSIX_REC_MIN_XFER_SIZE andPOSIX_REC_MAX_XFER_SIZE values.
Maximum recommended file transfer size.
Minimum recommended file transfer size.
Recommended file transfer buffer alignment.
Maximum number of bytes in a symbolic link.
The magnitude limitations in the following list are fixed by specific implementations.An application should assume that the value supplied by <limits.h> in aspecific implementation is the minimum that pertains whenever the application is rununder that implementation. A specific instance of a specific implementation can increase thevalue relative to that supplied by <limits.h> for that implementation. The actualvalue supported by a specific instance is provided by thesysconf(3C) function.
Maximum obase values allowed by thebc(1) utility.
Maximum number of elements permitted in an array by thebc utility.
Maximum scale value allowed by thebc utility.
Maximum length of a string constant accepted by thebc utility.
Maximum number of bytes in a character class name.
Maximum number of weights that can be assigned to an entry of theLC_COLLATE order keyword in the locale definition file.
Maximum number of expressions that can be nested within parentheses by theexpr(1) utility.
Maximum number of expressions that can be nested within parentheses by theexpr utility.
Unless otherwise noted, the maximum length, in bytes, of a utility's input line (either standard input or another file), when the utility is described as processing text files. The length includes room for the trailing <newline>.
Maximum number of simultaneous supplementary group IDs per process.
Maximum number of repeated occurrences of a regular expression permitted when using the interval notation \{m,n\}.
The symbolic constants in the following list are symbolic names for themost restrictive value for certain features on an implementation supporting the POSIXTimers option.
The resolution of theCLOCK_REALTIME clock, in nanoseconds.
The symbolic constants in the following list are symbolic names for themost restrictive value for certain features on an implementation conforming to variousPOSIX and Single Unix Specification requirements. Seestandards(5).
The number of I/O operations that can be specified in a list I/O call.
The number of outstanding asynchronous I/O operations.
Maximum length of argument to theexec(2) functions including environment data.
Maximum number of simultaneous processes per real user ID.
The number of timer expiration overruns.
Maximum length of a host name (not including the terminating null) as returned from thegethostname(3C) function.
Maximum number of links to a single file.
The size of the storage required for a login name, in bytes, including the terminating null.
Maximum number of bytes in a terminal canonical input queue.
Maximum number of bytes allowed in a terminal input queue.
The number of message queues that can be open for a single process.
The maximum number of message priorities supported by the implementation.
Maximum number of bytes in a filename (not including terminating null).
Maximum number of simultaneous supplementary group IDs per process.
Maximum number of files that one process can have open at any one time.
Maximum number of bytes in a pathname.
Maximum number of bytes that is guaranteed to be atomic when writing to a pipe.
The number of repeated occurrences of a BRE permitted by theregexec() andregcomp() functions when using the interval notation {\(m,n\}
The number of realtime signal numbers reserved for application use.
The number of semaphores that a process can have.
The maximum value a semaphore can have.
The number of queued signals that a process can send and have pending at the receiver(s) at any time.
The value that can be stored in an object of typessize_t.
The number of streams that one process can have open at one time.
The number of replenishment operations that can be simultaneously pending for a particular sporadic server scheduler.
The number of bytes in a symbolic link.
The number of symbolic links that can be traversed in the resolution of a pathname in the absence of a loop.
The number of attempts made to destroy a thread's thread-specific data values on thread exit.
The number of data keys per process.
The number of threads per process.
The per-process number of timers.
The length in bytes of a trace event name.
The length in bytes of a trace generation version string or a trace stream name.
The number of trace streams that can simultaneously exist in the system.
The number of user trace event type identifiers that may simultaneously exist in a traced process, including the predefined user trace eventPOSIX_TRACE_UNNAMED_USER_EVENT.
The size of the storage required for a terminal device name, in bytes, including the terminating null.
Maximum number of bytes supported for the name of a timezone (not of the TZ variable).
Maximum obase values allowed by thebc utility.
Maximum number of elements permitted in an array by thebc utility.
Maximum scale value allowed by thebc utility.
Maximum length of a string constant accepted by thebc utility.
Maximum number of bytes in a character class name.
Maximum number of weights that can be assigned to an entry of theLC_COLLATE order keyword in the locale definition file.
Maximum number of expressions that can be nested within parentheses by theexpr utility.
Unless otherwise noted, the maximum length, in bytes, of a utility's input line (either standard input or another file), when the utility is described as processing text files. The length includes room for the trailing <newline>.
Maximum number of repeated occurrences of a regular expression permitted when using the interval notation \{m,n\}.
Maximum number ofiovec structures that one process has available for use withread(2) orwrite(2).
Maximum number of bytes in a filename (not including the terminating null).
Maximum number of bytes in a pathname.
The values in the following lists shall be defined in <limits.h> andare constant expressions suitable for use in#if preprocessing directives. Moreover, exceptforCHAR_BIT,DBL_DIG,DBL_MAX,FLT_DIG,FLT_MAX,LONG_BIT,WORD_BIT, andMB_LEN_MAX, the symbolicnames are defined as expressions of the correct type.
If the value of an object of typechar is treated asa signed integer when used in an expression, the value ofCHAR_MINis the same as that ofSCHAR_MIN and the value ofCHAR_MAXis the same as that ofSCHAR_MAX. Otherwise, the value ofCHAR_MINis 0 and the value ofCHAR_MAX is the same as thatofUCHAR_MAX.
Number of bits in a typechar.
Maximum value of typechar.
Minimum value of typechar.
Digits of precision of typedouble.
Maximum decimal value of adouble.
Minimum decimal value of adouble.
Digits of precision of typefloat.
Maximum decimal value of afloat.
Minimum decimal value of afloat.
Minimum value of typeint.
Maximum value of anint.
Minimum value of typelong long.
Maximum value of typelong long.
Number of bits in along.
Minimum value of typelong.
Maximum value of along.
Maximum number of bytes in a character, for any supported locale.
Minimum value of typesigned char.
Maximum value of typesigned char.
Minimum value of typeshort.
Maximum value of typeshort.
Maximum value of an object of typessize_t.
Minimum number of unique filename generated bytmpnam(3C). Maximum number of times an application can calltmpnam() reliably.
Maximum value of typeunsigned char.
Maximum value of typeunsigned.
Maximum value of type unsignedlong long.
Maximum value of typeunsigned long.
Maximum value for a typeunsigned short.
Number of bits in a word or typeint.
The following constants are defined in <limits.h>.
Maximum number of bytes in a character class name.
The maximum number of bytes supported in a user's login name.
Maximum value of digit in calls to theprintf(3C) andscanf(3C) functions.
Maximum number of bytes in aLANG name.
Maximum message number.
Maximum number of bytes in an N-to-1 collation mapping.
Maximum set number.
Maximum number of bytes in a message string.
Default process priority.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.Legal Notices |   |