[moira.git] / man / moirad.8

.TH SMSD 8 "30 Nov 1988" "Project Athena"
\" RCSID: $Header$
.SH NAME
smsd, startsms \- SMS query daemon
.SH SYNOPSIS
.B smsd
.br
.B startsms
.SH DESCRIPTION
The SMS server
must be running on the machine hosting the SMS database for any of the
SMS clients to function.  Rather than invoke
.B smsd
directly, it is started by
.B startsms,
which starts the daemon running in the proper working directory and
captures logging messages.
.PP
Logging is done to standard output.
How much gets logged by
.B smsd
is controlled by the variable
.I log_flags
which is compiled into the file
.I sms_srvdata.c.
If critical errors are detected, they are logged to
.B /u1/sms/critical.log
and in a zephyrgram to class
.B SMS
instance
.B SMS
in addition to standard output.
Also, a journal file is kept in
.B /u1/sms/journal
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.
.PP
.B startsms
sets its working directory to the root, disconnects from the terminal
and puts itself in the background.  It then starts
.B /u1/sms/bin/smsd,
and will capture lines the server writes to standard output and log them
in
.B /u1/sms/sms.log
along with a timestamp.
.B startsms
will also log the exit status of the
.B smsd
if it is non-zero.
.SH FILES
/u1/sms/sms.log
.br
/u1/sms/critical.log
.br
/u1/sms/journal
.br
/etc/srvtab \- The dcm must be able to get Kerberos tickets for "sms.sms".
.SH "SEE ALSO"
The Project Athena Technical Plan section on SMS.
Commit	Line	Data
5834a392	1	.TH SMSD 8 "30 Nov 1988" "Project Athena"
	2	\" RCSID: $Header$
	3	.SH NAME
2ba19438	4	smsd, startsms \- SMS query daemon
5834a392	5	.SH SYNOPSIS
	6	.B smsd
	7	.br
	8	.B startsms
	9	.SH DESCRIPTION
	10	The SMS server
	11	must be running on the machine hosting the SMS database for any of the
	12	SMS clients to function. Rather than invoke
	13	.B smsd
	14	directly, it is started by
	15	.B startsms,
	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	How much gets logged by
	21	.B smsd
	22	is controlled by the variable
	23	.I log_flags
	24	which is compiled into the file
	25	.I sms_srvdata.c.
	26	If critical errors are detected, they are logged to
	27	.B /u1/sms/critical.log
	28	and in a zephyrgram to class
	29	.B SMS
	30	instance
	31	.B SMS
	32	in addition to standard output.
	33	Also, a journal file is kept in
	34	.B /u1/sms/journal
	35	logging every successful change of the database in a format that can
	36	be replayed by
	37	.I smstest(8).
	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.
	40	.PP
	41	.B startsms
	42	sets its working directory to the root, disconnects from the terminal
	43	and puts itself in the background. It then starts
	44	.B /u1/sms/bin/smsd,
	45	and will capture lines the server writes to standard output and log them
	46	in
	47	.B /u1/sms/sms.log
	48	along with a timestamp.
	49	.B startsms
	50	will also log the exit status of the
	51	.B smsd
	52	if it is non-zero.
	53	.SH FILES
	54	/u1/sms/sms.log
	55	.br
	56	/u1/sms/critical.log
	57	.br
	58	/u1/sms/journal
	59	.br
5834a392	60	/etc/srvtab \- The dcm must be able to get Kerberos tickets for "sms.sms".
	61	.SH "SEE ALSO"
	62	The Project Athena Technical Plan section on SMS.