[23095] | 1 | .TH MOIRAD 8 "30 Nov 1988" "Project Athena" |
---|
[24319] | 2 | \" RCSID: $HeadURL: svn+ssh://svn.mit.edu/moira/trunk/moira/man/moirad.8 $ $Id: moirad.8 3956 2010-01-05 20:56:56Z zacheiss $ |
---|
[23095] | 3 | .SH NAME |
---|
| 4 | moirad, startmoira \- Moira query daemon |
---|
| 5 | .SH SYNOPSIS |
---|
| 6 | .B moirad |
---|
| 7 | .br |
---|
| 8 | .B startmoira |
---|
| 9 | .SH DESCRIPTION |
---|
| 10 | The Moira server |
---|
| 11 | must be running on the machine hosting the Moira database for any of the |
---|
| 12 | Moira clients to function. Rather than invoke |
---|
| 13 | .B moirad |
---|
| 14 | directly, it is started by |
---|
| 15 | .B startmoira, |
---|
| 16 | which starts the daemon running in the proper working directory and |
---|
| 17 | captures logging messages. |
---|
| 18 | .PP |
---|
| 19 | Logging is done to standard output. |
---|
| 20 | If critical errors are detected, they are logged to |
---|
| 21 | .B /moira/critical.log |
---|
| 22 | and in a zephyrgram to class |
---|
| 23 | .B MOIRA |
---|
| 24 | instance |
---|
| 25 | .B MOIRA |
---|
| 26 | in addition to standard output. |
---|
| 27 | Also, a journal file is kept in |
---|
| 28 | .B /moira/journal |
---|
| 29 | logging every successful change of the database in a format that can |
---|
| 30 | be replayed by |
---|
| 31 | .I mrtest(8). |
---|
| 32 | For the server to be able to function properly, it must be run as root |
---|
| 33 | and root must have access to the tables in the DBMS. |
---|
| 34 | .PP |
---|
| 35 | It is possible to shut down the database side of the server when it is |
---|
| 36 | necessary to lock out clients. In this state the server will only |
---|
| 37 | respond to noop and motd requests. When the file |
---|
| 38 | .B /etc/smsdown |
---|
| 39 | exists, the server will close the database the next time there are no |
---|
| 40 | clients using it. To force the server to close down the database as |
---|
| 41 | soon as any active operation is finished, send it a USR1 signal. The |
---|
| 42 | first time a new client connects after the |
---|
| 43 | .B /etc/smsdown |
---|
| 44 | file is removed, the database will be re-opened. To force an |
---|
| 45 | immediate reopening, send the server a USR2 signal. The contents of |
---|
| 46 | the |
---|
| 47 | .B /etc/smsdown |
---|
| 48 | file are returned as the Moira motd. |
---|
| 49 | .PP |
---|
| 50 | .B startmoira |
---|
| 51 | sets its working directory to /, disconnects from the terminal |
---|
| 52 | and puts itself in the background. It then starts |
---|
| 53 | .B /moira/bin/moirad, |
---|
| 54 | and will capture lines the server writes to standard output and log them |
---|
| 55 | in |
---|
| 56 | .B /moira/moira.log |
---|
| 57 | along with a timestamp. |
---|
| 58 | .B startmoira |
---|
| 59 | will also log the exit status of the |
---|
| 60 | .B moirad |
---|
| 61 | if it is non-zero. |
---|
| 62 | .SH FILES |
---|
| 63 | /moira/moira.log |
---|
| 64 | .br |
---|
| 65 | /moira/critical.log |
---|
| 66 | .br |
---|
| 67 | /moira/journal |
---|
| 68 | .br |
---|
| 69 | /etc/smsdown |
---|
| 70 | .br |
---|
| 71 | /etc/athena/srvtab \- The server must be able to get Kerberos tickets for |
---|
| 72 | "moira.[servername]". |
---|
| 73 | .SH "SEE ALSO" |
---|
| 74 | The Project Athena Technical Plan section on Moira. |
---|