ifdata(1) [debian man page]

ifdata(1)																 ifdata(1)

NAME

       ifdata - get network interface info without parsing ifconfig output

SYNOPSIS

       ifdata [options] {iface}

DESCRIPTION

       ifdata can be used to check for the existence of a network interface, or to get information abut the interface, such as its IP address. Un-
       like ifconfig or ip, ifdata has simple to parse output that is designed to be easily used by a shell script.

OPTIONS

       -h     Print out a help summary.

       -e     Test to see if the interface exists, exit nonzero if it does not.

       -p     Prints out the whole configuration of the interface.

       -pe    Prints "yes" or "no" if the interface exists or not.

       -pa    Prints the IPv4 address of the interface.

       -pn    Prints the netmask of the interface.

       -pN    Prints the network address of the interface.

       -pb    Prints the broadcast address of the interface.

       -pm    Prints the MTU of the interface.

       Following options are Linux only.

       -ph    Prints the hardware address of the interface.

       -pf    Prints the flags of the interface.

       -si    Prints out all the input statistics of the interface.

       -sip   Prints the number of input packets.

       -sib   Prints the number of input bytes.

       -sie   Prints the number of input errors.

       -sid   Prints the number of dropped input packets.

       -sif   Prints the number of input fifo overruns.

       -sic   Print the number of compressed input packets.

       -sim   Prints the number of input multicast packets.

       -so    Prints out all the output statistics of the interface.

       -sop   Prints the number of output packets.

       -sob   Prints the number of output bytes.

       -soe   Prints the number of output errors.

       -sod   Prints the number of dropped output packets.

       -sof   Prints the number of output fifo overruns.

       -sox   Print the number of output collisions.

       -soc   Prints the number of output carrier losses.

       -som   Prints the number of output multicast packets.

       -bips  Prints the number of bytes of incoming traffic measured in one second.

       -bops  Prints the number of bytes of outgoing traffic measured in one second.

AUTHOR

       Benjamin BAYART

								    2006-03-07								 ifdata(1)

PTH-CONFIG(1)						       GNU Portable Threads						     PTH-CONFIG(1)

NAME

       pth-config - Pth library build utility

VERSION

       GNU Pth 2.0.7 (08-Jun-2006)

SYNOPSIS

       pth-config [--help] [--version] [--all] [--prefix] [--exec-prefix] [--bindir] [--libdir] [--includedir] [--mandir] [--datadir] [--acdir]
       [--cflags] [--ldflags] [--libs]

DESCRIPTION

       The pth-config program is a little helper utility for easy configuring and building applications based on the pth(3) library.  It can be
       used to query the C compiler and linker flags which are required to correctly compile and link the application against the pth(3) library.

OPTIONS

       pth-config accepts the following options:

       --help
	   Prints the short usage information.

       --version
	   Prints the version number and date of the installed pth(3) library.

       --all
	   Forces the output of all flags, that is, including extra flags which are not Pth specific.

       --prefix
	   Prints the installation prefix of architecture independent files

       --exec-prefix
	   Prints the installation prefix of architecture dependent files.

       --bindir
	   Prints the installation directory of binaries.

       --libdir
	   Prints the installation directory of libraries.

       --includedir
	   Prints the installation directory of include headers.

       --mandir
	   Prints the installation directory of manual pages.

       --datadir
	   Prints the installation directory of shared data.

       --acdir
	   Prints the installation directory of autoconf data.

       --cflags
	   Prints the C compiler flags which are needed to compile the pth(3)-based application. The output is usually added to the "CFLAGS" vari-
	   able of the applications "Makefile".

       --ldflags
	   Prints the linker flags ("-L") which are needed to link the application with the pth(3) library. The output is usually added to the
	   "LDFLAGS" variable of the applications "Makefile".

       --libs
	   Prints the library flags ("-l") which are needed to link the application with the pth(3) library. The output is usually added to the
	   "LIBS" variable of the applications "Makefile".

EXAMPLE

	CC	= cc
	CFLAGS	= -O `pth-config --cflags`
	LDFLAGS = `pth-config --ldflags`
	LIBS	= -lm `pth-config --libs`

	all: foo
	foo: foo.o
	    $(CC) $(LDFLAGS) -o foo foo.o $(LIBS)
	foo.o: foo.c
	    $(CC) $(CFLAGS) -c foo.c

SEE ALSO

       pth(3), cc(1).

AUTHOR

	Ralf S. Engelschall
	rse@engelschall.com
	www.engelschall.com

08-Jun-2006							   GNU Pth 2.0.7						     PTH-CONFIG(1)