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   44335 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

powerman.conf(5)		   powerman		      powerman.conf(5)

NAME
       powerman.conf - configuration file for PowerMan

DESCRIPTION
       The  powerman.conf  file	 typically  includes one or more of the remote
       power controller (RPC) device files provided in the /usr/local/etc/pow‐
       erman  directory;  sets	a few global options; instantiates RPC devices
       with unique names, hostnames, and ports; and maps node names  to	 RPC's
       and plug numbers.

       Network-attached RPC's are instantiated with device lines of the form:

	      device "name" "type" "host:port"

       Serial-attached RPC's are instantiated with device lines of the form:

	      device "name" "type" "special file" "flags"

       where  special  file  is	 the full path to a tty device, and flags is a
       serial parameter specification in a form similar to that used by	 lilo,
       e.g.   "9600,8n1".  RPC's that are accessed via coprocesses are instan‐
       tiated as follows:

	      device "name" "type" "process |&"

       where process is the full path to a process whose standard  output  and
       input  will be controlled by powerman, e.g. "/usr/bin/conman -Q -j rpc0
       |&".

EXAMPLE
       The following example is a 16-node cluster that uses two 8-plug Baytech
       RPC-3 remote power controllers.

       include "/usr/local/etc/powerman/baytech.dev"  # include def for "baytech" RPC

       tcpwrappers yes			    # enable TCP wrappers

       # listen "0.0.0.0:10101"		    # uncomment to listen on all interfaces

       # Alias example - alias can be used in target specifications
       alias "pengra_service" "pengra[0-1]"
       alias "pengra_compute" "pengra[2-15]"

       # Power controller: device <name> <type> <hostname:port> [<flags>]
       device "pow0" "baytech" "pow0:23"  # instantiate pow0
       device "pow1" "baytech" "pow1:23"  # instantiate pow1

       # Plugs: node <name> <device> [<plug>]
       node "pengra[0-7]" "pow0" "[1-8]"  # map pengra0...pengra7 to pow0 plug 1-8
       node "pengra[8-15]" "pow1" "[1-8]" # map pengra8...pengra15 to pow1 plug 1-8

FILES
       /usr/local/etc/powerman/powerman.conf
       /usr/local/etc/powerman/*.dev

ORIGIN
       PowerMan	 was  originally  developed  by Andrew Uselton on LLNL's Linux
       clusters.  This software is open source and distributed under the terms
       of the GNU GPL.

SEE ALSO
       powerman(1),  powermand(8),  httppower(8), plmpower(8), vpcd(8), power‐
       man.conf(5), powerman.dev(5).

       http://code.google.com/p/powerman

powerman-2.3.20			  2014-08-26		      powerman.conf(5)

Vote for polarhome