Xinu7/contrib/distodt/man/bed.doc
BED(1) UNIX Programmer's Manual BED(1)
NNNNAAAAMMMMEEEE
bed - backend daemon process that runs on frontend machine
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
bbbbeeeedddd
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
_B_e_d is the BBBBackEEEEnd DDDDaemon that runs on the frontend machine.
It accepts status, odt, and download requests from other
frontends and then services these requests. It reads the
configuration of the backend machines it needs to service
from a _M_a_c_h_i_n_e_s _d_a_t_a_b_a_s_e, and it keeps lock files for each
reserved backend machine.
_B_e_d can be run by anyone - it is not a setuid program. It
runs in the background, so after typing _b_e_d it returns
immediately. _B_e_d actually starts 2 processes running in the
background, a parent process and one child process. The
parent process simply starts the child process and then
waits for it to die. The child process is the _r_e_a_l BED pro-
cess. It is the one that services requests from other fron-
tends. If for some reason the child process dies the parent
detects it and restarts a new child process as the BED pro-
cess. This insures that the BED process will always be run-
ning.
_S_t_a_t_u_s requests are replied to immediately, but _o_d_t and
_d_o_w_n_l_o_a_d requests cause a new process to be forked off to
handle the request. Currently the _o_d_t and _d_o_w_n_l_o_a_d built
into the BED only work when connected to a backend SSSSUUUUNNNN.
Thus the BED process should only be run on frontends that
have a SSSSUUUUNNNN as one of the backends.
FFFFIIIILLLLEEEESSSS
/usr/xinu/database/machine Backend machines database
/tmp/xinu/* Backend reservation lock files
SSSSEEEEEEEE AAAALLLLSSSSOOOO
bedkill(1), bedreboot(1)
BBBBUUUUGGGGSSSS
Currently the _o_d_t and _d_o_w_n_l_o_a_d built into the BED only work
when connected to a backend SSSSUUUUNNNN. Thus the BED process
should only be run on frontends that have a SSSSUUUUNNNN as one of
the backends.
Printed 6/11/88 1