1 .TH MOIRAD 8 "30 Nov 1988" "Project Athena"
4 moirad, startmoira \- Moira query daemon
11 must be running on the machine hosting the Moira database for any of the
12 Moira clients to function. Rather than invoke
14 directly, it is started by
16 which starts the daemon running in the proper working directory and
17 captures logging messages.
19 Logging is done to standard output.
20 How much gets logged by
22 is controlled by the variable
24 which is compiled into the file
26 If critical errors are detected, they are logged to
27 .B /u1/sms/critical.log
28 and in a zephyrgram to class
32 in addition to standard output.
33 Also, a journal file is kept in
35 logging every successful change of the database in a format that can
38 For the server to be able to function properly, if must be run as root
39 and root must have access to the tables through RTI Ingres.
41 It is possible to shutdown the database side of the server when it is
42 necessary to lock out clients. In this state the server will only
43 respond to noop and motd requests. When the file
45 exists, the server will close the database the next time there are no
46 clients using it. To force the server to close down the database as
47 soon as any active operation is finished, send it a USR1 signal. The
48 first time a new client connects after the
50 file is removed, the database will be re-opened. To force an
51 immediate reopening, send the server a USR2 signal. The contents of
54 file are returned as the Moira motd.
57 sets its working directory to the root, disconnects from the terminal
58 and puts itself in the background. It then starts
59 .B /u1/sms/bin/moirad,
60 and will capture lines the server writes to standard output and log them
63 along with a timestamp.
65 will also log the exit status of the
77 /etc/srvtab \- The server must be able to get Kerberos tickets for
80 The Project Athena Technical Plan section on Moira.