SYNOPSIS

       faild  [βˆβˆ’c communityfile] [βˆβˆ’s statefile] [βˆβˆ’r pidfile] [βˆβˆ’d facility] [βˆβˆ’u
       uid] [βˆβˆ’FipTUV]

DESCRIPTION

       Faild keeps state information about services the host it runs  on  pro‐
       vides.   The  failstat(l)  an failc(l) clients can be used to query and
       change state information, and the failsh(l) will update the information
       automatically.

       The  daemon  can  store  an  arbitrary  number  of  states, so only one
       instance of it is necessary per server. As the  daemon  never  performs
       any actions, it is not critical to run it as root on a privileged port.
       However, this isn’t necessary either, as there are  options  to  change
       the runtime uid.

OPTIONS

       βˆβˆ’dfacility
              increment  debug  level for facility facility.  See faildebug(l)
              for a list of available facilities.

       βˆβˆ’ccommunityfile
              Read community information from  the  text  file  communityfile.
              This  file  consists  of line containing three white space sepa‐
              rated fields.  The first field is the name of the service or  an
              asterisk  *  if  the  line  applies to all services.  The second
              field contains a community string, and the third field is either
              RO,  in  which  case  only read access to the service is allowed
              with this community string, or  RW,  in  which  case  read/write
              access is granted.

       βˆβˆ’F     Stay  in the foreground. Useful when running faild from init(8).

       βˆβˆ’m     prevent pages of faild from being  paged  out.  Avoids  problems
              with  failover occuring when the faild cannot reply fast enough.
              Not available on FreeBSD.

       βˆβˆ’nnonnice
              Decrese the nice number of the process  by  nonice.   This  only
              works if faild was started as a superuser.

       βˆβˆ’rpidfile
              write  the  process  id  the  given  file instead of the default
              /var/run/faild.pid.

       βˆβˆ’U     use a UDP socket  to  publish  state  information  (the  monitor
              always connects through TCP).

       βˆβˆ’T     use a TCP socket for failover shells to connect.

       βˆβˆ’pport use this port instead of the default port of 1291 (or some other
              port if you changed the default during the configuration step of

AUTHOR

       Andreas F. Muller <andreas.mueller@othello.ch>



Failover Utilities                 03/12/04                           FAILD(L)