Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   6284 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

GETCONF(1)		     BSD Reference Manual		    GETCONF(1)

NAME
     getconf - get configuration values

SYNOPSIS
     getconf -a [path]
     getconf system_variable
     getconf path_variable path

DESCRIPTION
     This interface is defined by IEEE Std1003.2 (``POSIX''). A far more com-
     plete interface is available using sysctl(8).

     The getconf utility displays system configuration values.	The system
     configuration values that may be requested are those available from the
     underlying functions confstr(3),  pathconf(2) and sysconf(3).

     If a system_variable or a path_variable and path are specified as argu-
     ments to getconf, the requested configuration value will be written to
     standard output.  If the requested configuration value is valid but unde-
     fined for the system, the string ``undefined'' is written to the standard
     output instead.

     The following options are available:

     -a	     Write all currently available configuration values to the stan-
	     dard output, using the format:

		   value name = value

	     If path is specified, all file oriented values (e.g., values
	     available from the pathconf(2) function) will be based on the
	     specified file, otherwise, they will be based on the file /.

     The getconf utility exits 0 on success, and >0 if an error occurs.

EXAMPLES
     To retrieve the longest name supported by the /mnt/cdrom filesystem, one
     would use the following request:

	   getconf name_max /mnt/cdrom

     To determine if the system supports the POSIX FORTRAN Development Utili-
     ties Option, one would use the following request:

	   getconf posix2_fort_dev

     To retrieve the maximum input queue available for the current tty, one
     would use the following request:

	   getconf max_input `tty`

SEE ALSO
     pathconf(2),  confstr(3),	sysconf(3),  sysctl(8)

STANDARDS
     The getconf() utility conforms to IEEE Std1003.2 (``POSIX'').

BSDI BSD/OS		      September 16, 1996			     1

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome