Commit aa3792bd authored by Leigh B. Stoller's avatar Leigh B. Stoller

Kill obsolete man pages.

parent 471e3f81
# $Id: Makefile,v 1.1 2000-10-02 21:25:36 kwright Exp $
all: mkacct rmacct
clean:
rm -f *.8 *.gz
mkacct:
rm -f mkacct.8 mkacct.8.gz
groff -t -man -Tascii mkacct.man > mkacct.8
/usr/bin/gzip -c mkacct.8 > mkacct.8.gz
rmacct:
rm -f rmacct.8 rmacct.8.gz
groff -t -man -Tascii rmacct.man > rmacct.8
/usr/bin/gzip -c rmacct.8 > rmacct.8.gz
install:
mv mkacct.8.gz /usr/local/man/man8
mv rmacct.8.gz /usr/local/man/man8
.TH MKACCT 8
.SH NAME
mkacct \- Make accounts for the experiment identified by a user-supplied
experiment ID.
.SH SYNOPSIS
.B mkacct
.RI experiment-id
.SH DESCRIPTION
.de SP
.if t .sp 0.4
.if n .sp
..
.B mkacct
creates accounts on machines reserved for the given
.RI experiment-id .
You must be root
to run
.B mkacct.
The appropriate machines are found by querying the testbed
database for all
machines reserved for
.RI experiment-id .
An account will be made only if the machine is reachable and only for the
currently booted OS. Only FreeBSD and Linux are supported OSes.
User directories
are created in /users/<user> and users are given a tcsh login shell.
All other account attributes (login name, password, fullname/comments, group
ID, user ID) are derived from
testbed database records.
The user and group databases are not rebuilt from scratch. The
new users/groups
are effectively appended to existing account databases.
.B mkacct
will report descriptive errors
and exit on the following conditions: if the
.RI experiment-id
is not found in the testbed database, if the user is not root,
if there is no group in the database for the experiment, if a
reserved machine is not reachable, or if the operating system for
a certain machine cannot be determined.
.B mkacct
uses the standard locking mechanisms for password database modification
and, in that respect, is mt-safe. However, the testbed database has no
coarse-grained locking
mechanism, however, so undefined behavior could result if other users
are modifying the testbed database while
.B mkacct
is running.
.SH FILES
.TP 25n
$CVSROOT/testbed/doc/man/mkacct.man
.SH "SEE ALSO"
.BR rmacct (8).
.SH NOTES
This command is specific to the Utah Testbed environment.
To avoid running as root, a login on plastic must be created with root access
to the testbed machines and access to the testbed database.
.SH BUGS
Not mt-safe (see above). Must run as root. Due to complexities that we
chose not to sort out at this time, no local disk space is allocated. It is up to the
user to allocate and, if necessary, filesave local disk space.
Exiting isn't
the most robust error-handling for unreachable machines or machines with
unknown OSes: skipping the problem machine and continuing would be better.
.SH AUTHOR
L. Kristin Wright (kwright@cs.utah.edu)
.TH RMACCT 8
.SH NAME
rmacct \- Remove accounts for the experiment identified by a user-supplied
experiment ID.
.SH SYNOPSIS
.B rmacct
.RB [ \-nt ]
.RI experiment-id
.SH DESCRIPTION
.de SP
.if t .sp 0.4
.if n .sp
..
.B rmacct
removes accounts on machines reserved for the members of the given
.RI experiment-id .
You must be root
to run
.B rmacct.
The appropriate machines are found by querying the testbed
database for all
machines reserved for
.RI experiment-id .
Accounts will be deleted only if the machine is reachable and only for the
currently booted OS. Only FreeBSD and Linux are supported OSes. Unless
otherwise specified, the
user directory /users/<login name> is tarred and deleted. The
tarball is placed in plastic:/tmp/<login name>.tar.
.B rmacct
will report descriptive errors
and exit on the following conditions: if the
.RI experiment-id
is not found in the testbed database, if the user is not root,
if a reserved machine is not reachable, or if the operating system for
a certain machine cannot be determined.
.B rmacct
uses the standard locking mechanisms for password database modification
and, in that respect, is mt-safe. However, the testbed database has no
coarse-grained locking
mechanism, however, so undefined behavior could result if other users
are modifying the testbed database while
.B mkacct
is running.
.SH OPTIONS
.TP
.B \-nt
Do NOT create the tarfile in plastic:/tmp ("No Tar").
.SH FILES
.TP 25n
$CVSROOT/testbed/doc/man/rmacct.man
.SH "SEE ALSO"
.BR mkacct (8).
.SH NOTES
This command is specific to the Utah Testbed environment.
.SH BUGS
Not mt-safe (see above). Must run as root. Due to complexities that we
could not sort out, there is no convention for local disk space
allocated. It is up to the user to save local disk space. Exiting isn't
the most robust error-handling for unreachable machines or machines with
unknown OSes: skipping the problem machine and continuing would be better.
.SH AUTHOR
L. Kristin Wright (kwright@cs.utah.edu)
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment