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

CPUT(1)			     BSD Reference Manual		       CPUT(1)

NAME
     cput - print capabilities from data bases

SYNOPSIS
     cput [-f database] [-l] entry [capability [type]]

DESCRIPTION
     The cput utility lets you print information from capability data base
     files like /etc/ppp.sys and /etc/login.conf. It provides a command line
     interface for the getcap(3) library routines.

     Cput supports the following options:

     -f database
		 Add the given database to the list of database files to
		 search.  You can specify multiple -f options to search multi-
		 ple database files.

     -l		 Print the literal field; do not interpret strings or numbers.
		 Without this flag, cput decodes the cgetstr(3) character es-
		 capes in strings, and prints numeric fields (with type `#')
		 in decimal.  See getcap(3) for details about the encoding.

     If the environment variable CPUTPATH is set to a colon-separated list of
     database file names, cput adds the databases to its list.	Cput first
     searches database files specified using -f (going left to right), then
     database files specified using CPUTPATH (again going left to right).

     The entry name is required.  If no capability name is provided, cput
     prints the entire entry on a line.	 Strings and numbers are not inter-
     preted.

     If you provide a capability name, cput looks up the capability in the
     given entry.  If the capability has a value, cput prints it; if it is a
     boolean capability, then cput prints the name of the capability instead.

     If you provide a capability type, then cput only matches capabilities
     with the given type.  A capability type is a single character that sepa-
     rates a capability name from its value.  A type of `=' matches string ca-
     pabilities, while `#' matches numeric capabilities and the special type
     `:' matches boolean capabilities.	If you don't provide an explicit capa-
     bility type, then cput tries `=', `#' and `:'.

     Cput exits with status 0 if it matches an entry, or both the entry and
     the capability when both values are given.	 If it can't find a match, it
     exits silently with status 1.  If some other error occurs, cput prints an
     error message and exits with status 2.

SEE ALSO
     ttydesc(1),  getcap(3)

BUGS
     When printing complete entries, cput doesn't remove empty capabilities.

BSDI BSD/OS			April 27, 1998				     1

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

Vote for polarhome