[moira.git] / man / reg_svr.8

.TH REG_SVR 8 "30 Nov 1988" "Project Athena"
\" RCSID: $Header$
.SH NAME
reg_svr, startreg \- SMS account registration server
.SH SYNOPSIS
.B reg_svr
.br
.B startreg
.SH DESCRIPTION
The registration server
must be running on the machine hosting the SMS database for the 
.I userreg
program to function.  Rather than invoke
.B reg_svr
directly, it is started by
.B startreg,
which starts the daemon running in the proper working directory and
captures logging messages.
.PP
Logging is done to standard output.
If critical errors are detected, they are logged to
.B /u1/sms/critical.log
and in a zephyrgram to class
.B SMS
instance
.B REG_SVR
in addition to standard output.
Also, a journal file is kept in
.B /u1/sms/journal.reg
logging every successful change of the database in a format that can
be replayed by
.I smstest(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,
Kerberos principal "register.sms" must have permission to create new
Kerberos 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,
and will capture lines the server writes to standard output and log them
in
.B /u1/sms/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
.br
/u1/sms/critical.log
.br
/u1/sms/journal.reg
.br
.br
/tmp/tkt_ureg \- temporary Kerberos ticket storage.
.br
/etc/srvtab \- The dcm must be able to get Kerberos tickets for "register.sms".
.SH AUTHORS
Jay Berkenbilt, Bill Sommerfeld
.SH "SEE ALSO"
userreg(1), The Project Athena Technical Plan section on SMS.
Commit	Line	Data
5834a392	1	.TH REG_SVR 8 "30 Nov 1988" "Project Athena"
	2	\" RCSID: $Header$
	3	.SH NAME
35bacfb8	4	reg_svr, startreg \- SMS account registration server
5834a392	5	.SH SYNOPSIS
	6	.B reg_svr
	7	.br
	8	.B startreg
	9	.SH DESCRIPTION
	10	The registration server
	11	must be running on the machine hosting the SMS database for the
	12	.I userreg
	13	program to function. Rather than invoke
	14	.B reg_svr
	15	directly, it is started by
	16	.B startreg,
	17	which starts the daemon running in the proper working directory and
	18	captures logging messages.
	19	.PP
	20	Logging is done to standard output.
	21	If critical errors are detected, they are logged to
	22	.B /u1/sms/critical.log
	23	and in a zephyrgram to class
	24	.B SMS
	25	instance
	26	.B REG_SVR
	27	in addition to standard output.
	28	Also, a journal file is kept in
	29	.B /u1/sms/journal.reg
	30	logging every successful change of the database in a format that can
	31	be replayed by
	32	.I smstest(8).
	33	For the server to be able to function properly, if must be run as root
	34	and root must have access to the tables through RTI Ingres. Also,
	35	Kerberos principal "register.sms" must have permission to create new
	36	Kerberos principals and set their passwords.
	37	.PP
	38	.B startreg
	39	sets its working directory to the root, disconnects from the terminal
	40	and puts itself in the background. It then starts
	41	.B /u1/sms/bin/reg_svr,
	42	and will capture lines the server writes to standard output and log them
	43	in
	44	.B /u1/sms/reg_svr.log
	45	along with a timestamp.
	46	.B startreg
	47	will also log the exit status of the
	48	.B reg_svr
	49	if it is non-zero.
	50	.SH FILES
	51	/u1/sms/reg_svr.log
	52	.br
	53	/u1/sms/critical.log
	54	.br
	55	/u1/sms/journal.reg
	56	.br
	57	.br
	58	/tmp/tkt_ureg \- temporary Kerberos ticket storage.
	59	.br
	60	/etc/srvtab \- The dcm must be able to get Kerberos tickets for "register.sms".
8eeef30a	61	.SH AUTHORS
8eeef30a	62	Jay Berkenbilt, Bill Sommerfeld
5834a392	63	.SH "SEE ALSO"
35bacfb8	64	userreg(1), The Project Athena Technical Plan section on SMS.