Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

fair.conf(5) [debian man page]

fair.conf(5)						      BSD File Formats Manual						      fair.conf(5)

NAME
fair.conf -- configuration file for the carrousel and transponder daemons DESCRIPTION
Debug (bool, false) Runs the program in debug mode: it will not detach, it will print status updates very frequently, it will print extra diagnostic mes- sages to stderr. DropPrivs (bool, true) The program will switch to a different uid/gid after obtaining root-only resources. See also the UserID and GroupID variables. WorkerService (string, smtp) * This is the service on which the worker nodes offer the service that is being balanced. Typically this is the service of another dae- mon, e.g. Postfix. The transponder daemon also uses this as the datagram source service for its status updates. BalancerService (string, smtp) * The stream service on which the carrousel daemon listens for incoming connections. These connections will be put through to one of the worker nodes. TransponderService (string, rlp) * The carrousel daemon listens on this service for status update datagrams from the transponders. See also the AllowUDP variable. PingInterval (time, 0.1 seconds) How often the transponder sends an update to each carrousel. So, if two carrousels are configured and the interval is 0.1 seconds, that transponder sends 20 packets every second. PingTimeout (time, 0.5 seconds) After this period has elapsed without receiving any status update packets from the transponder, this host is considered dead. IdleTimeout (time, 600.0 seconds) The connection is terminated if neither party has sent something for this many seconds. For SMTP connections this would have to be at least 600.0 seconds, see RFC 2821 section 4.5.3.2. ConnectTimeout (time, 1.0 seconds) When connecting to a worker node, abort after this many seconds have elapsed and no connection is established. ConnectAttempts (integer, 3) When putting through a connection fails, the carrousel will attempt to contact other worker nodes. It will give up after this many tries. BenchPeriod (time, 5.0 seconds) If a connection to a worker node fails it is excluded from new connections for this many seconds. TrailPeriod (time, 60.0 seconds) When a connection is finished, pretend it lasted this many seconds more for load calculation purposes. Hysteresis (integer, 0) Add an advantage to the last used worker node so that it gets selected in preference of others. MaxCapacity (integer, 100) When sending update packets, the capacity of the worker node measured in terms of concurrent connections. This number is adjusted for the current load average before sending it to the carrousel nodes. MaxBurst (integer, 65536) Ringbuffer size for load balancer nodes. MinBurst (integer, 1450) If fewer than this many bytes are available in the ring buffer, do not read anything but try to free up space first. LocalTCP (bool, yes) Only allow connections over the loopback interface. If this option is set to "no", connections will be accepted on any interface and on any address. AllowUDP (extended regexp, ^) Only datagram status packets that match this extended regular expression are accepted. All other datagram packets are logged and silently dropped. Once UDP packets are accepted from a certain source, they are never matched against this regexp again. SEE ALSO
carrousel(8), transponder(8) Debian GNU/Linux June 1, 2019 Debian GNU/Linux

Check Out this Related Man Page

PMCD_WAIT(1)						      General Commands Manual						      PMCD_WAIT(1)

NAME
pmcd_wait - wait for PMCD to accept client connections SYNOPSIS
$PCP_BINADM_DIR/pmcd_wait [-h host] [-t interval] [-v] DESCRIPTION
pmcd_wait waits for the Performance Metrics Collector Daemon (PMCD) to be running and accepting client connections. Unless directed to another host by the -h option, pmcd_wait will try to contact pmcd(1) on the local host. pmcd_wait will timeout and abandon the attempt to connect to pmcd after 60 seconds. This default timeout interval may be changed using the -t option, where the interval argument follows the syntax described in PCPIntro(1) and in the simplest form may be an unsigned integer (the implied units in this case are seconds). On successful connection to pmcd an exit status of zero is returned. If an error or timeout occurs, then a non-zero exit status is returned as described below. The other options are as follows: -v This option turns the verbose mode on. With the verbose mode off (which is the default), no output will be generated. With verbose mode on, error messages will be output on stderr. PCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. On each installation, the file /etc/pcp.conf contains the local values for these variables. The $PCP_CONF variable may be used to specify an alternative configura- tion file, as described in pcp.conf(5). SEE ALSO
PCPIntro(1), pmcd(1), pcp.conf(5) and pcp.env(5). DIAGNOSTICS
Error messages will be output to stderr only if the verbose mode is on. The following exit status codes are returned: 0 pmcd_wait was able to successfully connect to pmcd within the timeout period. 1 A usage error occurred, use -v for more details. 2 No connection was made in the timeout interval. This will happen if pmcd is running but takes too long to complete the client con- nection, or if pmcd is not running and all connection attempts in the timeout interval failed with the error ECONNREFUSED. 3 A UNIX error occurred, use -v for more details. 4 A PCP error occurred, use -v for more details. Performance Co-Pilot PCP PMCD_WAIT(1)
Man Page