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

cmappmgr(1m)															      cmappmgr(1m)

NAME
cmappmgr - launches and monitors an application process on a node SYNOPSIS
cmappmgr -node node_name [-cmappserver_timeout number_of_seconds] -service service_name DESCRIPTION
cmappmgr launches and monitors the specified application process on a specified node. The cmappserver(1m) daemon process must be running on the specified node, and there must be a routable TCP/IP network between the specified node and the local host where cmappmgr(1m) is run. cmappmgr exits when the application process exits. Options cmappmgr supports the following options: -node node_name Name of the node on which to launch the application process. -cmappserver_timeut number_of_seconds The number of seconds that must elapse before cmappmgr times out the connection with cmappserver on the specified node. This is optional. The default value is 10 seconds. The maximum value that can be specified is 600 seconds, and the mini- mum value is 1 second. -service service_name The full command line for the application or process to be launched. Note that -service must be the last argument speci- fied for cmappmgr as all strings following the argument are considered as part of the command line to launch the applica- tion process. Quotation marks ("") are not required. RETURN VALUE
cmappmgr returns the following value upon completion: 0 Successful completion. >= 1 One or more error conditions occurred. The value generally reflects the exit code of the process. If, for any reason, the process fails to launch on the specified node (for example, because of an error connecting to cmappserver), cmappmgr exits with 1. EXAMPLES
To launch an xclock application on the node v-smp1: cmappmgr -node v-smp1 -service /usr/bin/X11/xclock -display 16:89:255:19:0.0 AUTHOR
cmappmgr was developed by HP. SEE ALSO
cmappserver(1m). Designing high-availability solutions with HP Serviceguard and HP Integrity Virtual Machines Requires Optional Serviceguard Software cmappmgr(1m)
Man Page