FDMANAGER(8)

NAME
fdmanager - manages set of FramerD servers

SYNOPSIS
fdmanager < master_control_file > [ pid_file ] [ status_file ]

DESCRIPTION
fdmanager manages a set of FramerD servers whose control files are listed in master_control_file The program will restart any servers which terminate and will take care of terminating the servers before it itself terminates. Servers managed by fdmanager will be launched from the directory in which their control file is found. The PID of the program is written to either the specified pid_file or the file master_control_file .pid A status report of the servers under the manager's control will be emitted to either status_file or the file master_control_file .status. This file contains process id's and network id's for managed processes, as well as the server control file which spawned them.

FILE FORMAT
The master_control_file consists of a series of entries describing individual servers. The format of an entry is: [wait= secs ] [dependent] < server_control_file > [ arguments for fdserver ] The wait period secs specifies how long fdmanager will wait for this server to start. (It knows that a server has started when it writes its .nid file (see fdserver(1) ). If the server has not started in that time, it outputs a warning (using syslog(3) and the standard error) and continues. The flag dependent indicates that the server is dependent on the server before it. In particular, if the preceding server terminates and is restarted, the dependent server is forced to terminate and restart.

OPTIONS
No options

FILES
/etc/init.d/fdservers
    this is the SYSV init script (used under many Unix systems) to start fdmanager
framerd_root/ servers
    This is the default master control file used by the SYSV init script.
master_control_file .pid
    contains the PID of the fdmanager process, unless otherwise specified.
master_control_file .status
    contains the status of the fdmanager's managed servers
server_control_file_base .ppid
    created in the directory where the server control files are found and contains the fdmanager's PID. E.G. if the server control file /data/brico/brico.fdz is specified in the manager's master_control_file, the file /data/brico/brico.ppid will contain the manager's PID.
server_control_file_base .sleep
    when a server terminates and this file is found in the server's directory, fdmanager will wait with restarting the server until the file has been removed. It does this by forking a call to sleep(1) whose interval is either 60 seconds or the integer found in the file server_control_file_base .sleep This allows a maintainer to temporarily suspend a single server without stopping fdmanager or its other servers. This is done by creating the .sleep file and then killing the server (with SIGTERM, so that it will save its pending state).

BUGS
None known.

Revision Info
$Id: fdmanager.8,v 1.3 2002/07/10 00:13:11 haase Exp $

AUTHOR
Ken Haase < kh@beingmeta.com >

SEE ALSO
framerd(7) fdserver(1)