GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||
GeezerVison is showing keith.github.io — GETCONF(1)
NAME
SYNOPSIS
DESCRIPTIONThe The first form of the command displays all of the path or system configuration variables to standard output. If file is provided, all path configuration variables are reported for file using pathconf(2). Otherwise, all system configuration variables are reported using confstr(3) and sysconf(3). The second form of the command, with two mandatory arguments,
retrieves file- and file system-specific configuration variables using
pathconf(2). The third form, with a single argument,
retrieves system configuration variables using confstr(3)
and sysconf(3), depending on the type of variable. As an
extension, the second form can also be used to query static limits from
All sysconf(3) and pathconf(2)
variables use the same name as the manifest constants defined in the
relevant standard C-language bindings, including any leading underscore or
prefix. That is to say, system_var might be
Programming EnvironmentsThe The standard programming environments are as follows:
The command: getconf
POSIX_V6_WIDTH_RESTRICTED_ENVSreturns a newline-separated list of environments in which the width of certain fundamental types is no greater than the width of the native C type long. At present, all programming environments supported by FreeBSD have this property. Several of the confstr(3) variables provide information on the necessary compiler and linker flags to use the standard programming environments described above. Many of these values are also available through the sysctl(8) mechanism. EXIT STATUSThe EXAMPLESThe command: getconf PATHwill display the system default setting for the
The command: getconf NAME_MAX /tmpwill display the maximum length of a filename in the /tmp directory. The command: getconf -v POSIX_V6_LPBIG_OFFBIG
LONG_MAXwill display the maximum value of the C type
long in the
DIAGNOSTICSUse of a system_var or
path_var which is completely unrecognized is
considered an error, causing a diagnostic message to be written to standard
error. One which is known but merely undefined does not result in an error
indication. The SEE ALSOpathconf(2), confstr(3), sysconf(3), sysctl(8) STANDARDSThe HISTORYThe AUTHORSGarrett A. Wollman <[email protected]>
| |||||||||||
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |