Command line printer manipulation client, and build goo.

[moira.git] / man / reg_svr.8

diff --git a/man/reg_svr.8 b/man/reg_svr.8
index 7bc5cf5f68f735017db26b83199789bfa1311762..44b0e651bb915417bd7cdb253181871ce7bcf8fe 100644 (file)
--- a/man/reg_svr.8
+++ b/man/reg_svr.8
@@ -19,45 +19,45 @@ captures logging messages.
 .PP
 Logging is done to standard output.
 If critical errors are detected, they are logged to
-.B /u1/sms/critical.log
+.B /moira/critical.log
 and in a zephyrgram to class
 .B MOIRA
 instance
 .B REG_SVR
 in addition to standard output.
 Also, a journal file is kept in
-.B /u1/sms/journal.reg
+.B /moira/journal.reg
 logging every successful change of the database in a format that can
 be replayed by
 .I mrtest(8).
 For the server to be able to function properly, if must be run as root
-and root must have access to the tables through RTI Ingres.  Also,
+and root must have access to the tables in the DBMS.  Also,
 Kerberos principal "moira.[servername]" must be on the Kerberos admin
 server ACL to create new principals and set their passwords.
 .PP
 .B startreg
 sets its working directory to the root, disconnects from the terminal
 and puts itself in the background.  It then starts
-.B /u1/sms/bin/reg_svr,
+.B /moira/bin/reg_svr,
 and will capture lines the server writes to standard output and log them
 in
-.B /u1/sms/reg_svr.log
+.B /moira/reg_svr.log
 along with a timestamp.
 .B startreg
 will also log the exit status of the
 .B reg_svr
 if it is non-zero.
 .SH FILES
-/u1/sms/reg_svr.log
+/moira/reg_svr.log
 .br
-/u1/sms/critical.log
+/moira/critical.log
 .br
-/u1/sms/journal.reg
+/moira/journal.reg
 .br
 .br
 /tmp/tkt_ureg \- temporary Kerberos ticket storage.
 .br
-/etc/srvtab \- The dcm must be able to get Kerberos tickets for
+/etc/athena/srvtab \- The reg_svr must be able to get Kerberos tickets for
 "moira.[hostname]".
 .SH AUTHORS
 Jay Berkenbilt, Bill Sommerfeld