diff options
Diffstat (limited to 'static/v10/man8')
119 files changed, 11832 insertions, 0 deletions
diff --git a/static/v10/man8/11.8 b/static/v10/man8/11.8 new file mode 100644 index 00000000..ed079810 --- /dev/null +++ b/static/v10/man8/11.8 @@ -0,0 +1,12 @@ +.TH 11 8 +.CT 1 prog_c +.SH NAME +11as, 11cc, 11ld, 11nm, 11ranlib, 11reloc, 11size, 11strip \- pdp11 support +.SH DESCRIPTION +These programs do cross-compiling and related support +functions for the DEC PDP-11 family of computers. +Their descriptions correspond closely with those of +similarly named programs in Section 1 of this manual. +.SH FILES +.F 11a.out +output file diff --git a/static/v10/man8/20boot.8 b/static/v10/man8/20boot.8 new file mode 100644 index 00000000..893cb167 --- /dev/null +++ b/static/v10/man8/20boot.8 @@ -0,0 +1,31 @@ +.pa 1 +.he '20BOOT (VIII)'1/25/73'20BOOT (VIII)' +.ti 0 +NAME 20boot -- install new 11/20 system +.sp +.ti 0 +SYNOPSIS 20boot______ [ x_ ] +.sp +.ti 0 +DESCRIPTION This +shell command file copies the current version +of the 11/20 program used to run the VT01 display +onto the /dev/vt0 file. + +If no argument is given, the 11/20 program should be executing +but idle; the 11/20 program is sent preceded by a +"reboot" command. +If an argument is given, the 11/20 should +have been restarted at its ROM location +777300. +.sp +.ti 0 +FILES /dev/vt0; +.br +/sys/mdec/20.o (11/20 program) +.sp +.ti 0 +SEE ALSO vt0 (IV) +.sp +.ti 0 +DIAGNOSTICS -- diff --git a/static/v10/man8/Makefile b/static/v10/man8/Makefile new file mode 100644 index 00000000..a2af6bc6 --- /dev/null +++ b/static/v10/man8/Makefile @@ -0,0 +1,3 @@ +MAN = $(wildcard *.8) + +include ../../mandoc.mk diff --git a/static/v10/man8/ac.8 b/static/v10/man8/ac.8 new file mode 100644 index 00000000..1048aa19 --- /dev/null +++ b/static/v10/man8/ac.8 @@ -0,0 +1,56 @@ +.TH AC 8 +.CT 1 sa_nonmortals +.SH NAME +ac \- login accounting +.SH SYNOPSIS +.B /etc/ac +[ +.I option ... +] +[ +.I person ... +] +.SH DESCRIPTION +.I Ac +prints the total connect time +recorded in the accounting file, +.FR /usr/adm/wtmp . +If +.I persons +are named, only those login names are considered. +The options are +.TP +.BI -w " file" +Use +.I file +instead of +.FR /usr/adm/wtmp ; +.L - +means the standard input. +.TP +.B -p +Print total connect time for each +user. +.TP +.B -d +Print totals for each day. +.PP +The accounting file +.F /usr/adm/wtmp +is maintained by +.I init +and +.IR login (8), +provided it exists. +To start accounting, create it with length 0. +When accounting is turned on, the file grows without limit. +It is prudent periodically +to process the data and truncate the file. +.SH FILES +.F /usr/adm/wtmp +.SH "SEE ALSO" +.IR init (8), +.IR sa (8), +.IR login (8), +.IR utmp (5), +.IR who (1) diff --git a/static/v10/man8/acct.8 b/static/v10/man8/acct.8 new file mode 100644 index 00000000..fe5bebbc --- /dev/null +++ b/static/v10/man8/acct.8 @@ -0,0 +1,37 @@ +.pa 1 +.he 'ACCT (VIII)'1/20/73'ACCT (VIII)' +.ti 0 +NAME acct -- login accounting +.sp +.ti 0 +SYNOPSIS acct____ [ -w__ wtmp ] [ -p__ ] [ -d__ ] people +.sp +.ti 0 +DESCRIPTION acct____ +produces a printout giving +connect time +for each user who has logged in +during the life of the current wtmp____ file. +A total is also produced. +-w__ is used to specify an alternate wtmp file. +-p__ prints individual totals; without this option, +only totals are printed. +-d__ causes a printout for each midnight to midnight +period. +The people______ argument will limit the +printout to only the specified login names. +If no wtmp file is given, +/usr/adm/wtmp_____________ +is used. +.sp +.ti 0 +FILES /usr/adm/wtmp +.sp +.ti 0 +SEE ALSO init(VII), login(I), wtmp(V). +.sp +.ti 0 +DIAGNOSTICS "Cannot open 'wtmp'" if argument is unreadable. +.sp +.ti 0 +BUGS -- diff --git a/static/v10/man8/adduser.8 b/static/v10/man8/adduser.8 new file mode 100644 index 00000000..c22c10b1 --- /dev/null +++ b/static/v10/man8/adduser.8 @@ -0,0 +1,87 @@ +.TH ADDUSER 8 +.UC 4 +.SH NAME +adduser \- procedure for adding new users +.SH DESCRIPTION +A new user must choose a login name, which must not already appear in +.I /etc/passwd. +An account can be added by editing a line into the passwd file; this must +be done with the password file locked e.g. by using +.IR vipw (8). +.PP +A new user is given a group and user id. +User id's should be distinct across a system, since they +are used to control access to files. +Typically, users working on +similar projects will be put in the same group. Thus at UCB we have +groups for system staff, faculty, graduate students, and a few special +groups for large projects. System staff is group \*(lq10\*(rq for historical +reasons, and the super-user is in this group. +.PP +A skeletal account for a new user \*(lqernie\*(rq would look like: +.IP +ernie::235:20:& Kovacs,508E,7925,6428202:/mnt/grad/ernie:/bin/csh +.PP +The first field is the login name \*(lqernie\*(rq. The next field is the +encrypted password which is not given and must be initialized using +.IR passwd (1). +The next two fields are the user and group id's. +Traditionally, users in group 20 are graduate students and have account +names with numbers in the 200's. +The next field gives information about ernie's real name, office and office +phone and home phone. +This information is used by the +.IR finger (1) +program. +From this information we can tell that ernie's real name is +\*(lqErnie Kovacs\*(rq (the & here serves to repeat \*(lqernie\*(rq +with appropriate capitalization), that his office is 508 Evans Hall, +his extension is x2-7925, and this his home phone number is 642-8202. +You can modify the +.IR finger (1) +program if necessary to allow different information to be encoded in +this field. The UCB version of finger knows several things particular +to Berkeley \- that phone extensions start \*(lq2\-\*(rq, that offices ending +in \*(lqE\*(rq are in Evans Hall and that offices ending in \*(lqC\*(rq are +in Cory Hall. +.PP +The final two fields give a login directory and a login shell name. +Traditionally, user files live on a file system which has the machines +single letter +.IR net (1) +address as the first of two characters. Thus on the Berkeley CS Department +VAX, whose Berknet address is ``csvax'' abbreviated ``v'' the user file +systems are mounted on ``/va'', ``/vb'', etc. +On each such filesystem there are subdirectories there for each group +of users, i.e.: \*(lq/va/staff\*(rq and \*(lq/vb/prof\*(rq. +This is not strictly necessary but keeps the number of files in the +top level directories reasonably small. +.PP +The login shell will default to \*(lq/bin/sh\*(rq if none is given. +Most users at Berkeley choose \*(lq/bin/csh\*(rq so this is usually +specified here. +.PP +It is useful to give new users some help in getting started, supplying +them with a few skeletal files such as +.I \&.profile +if they use \*(lq/bin/sh\*(rq, or +.I \&.cshrc +and +.I \&.login +if they use \*(lq/bin/csh\*(rq. +The directory +\*(lq/usr/skel\*(rq contains skeletal definitions of such files. +New users should be given copies of these files which, for instance, +arrange to use +.IR tset (1) +automatically at each login. +.SH FILES +.ta 2i +/etc/passwd password file +.br +/usr/skel skeletal login directory +.SH SEE ALSO +passwd(1), finger(1), chsh(1), chfn(1), passwd(5), vipw(8) +.SH BUGS +User information should be stored in its own data base separate from +the password file. diff --git a/static/v10/man8/analyze.8 b/static/v10/man8/analyze.8 new file mode 100644 index 00000000..72c8769c --- /dev/null +++ b/static/v10/man8/analyze.8 @@ -0,0 +1,117 @@ +.lg 0 +.TH ANALYZE 8 +.UC 4 +.SH NAME +analyze \- Virtual UNIX postmortem crash analyzer +.SH SYNOPSIS +.B /etc/analyze +[ +.B \-s +swapfile +] [ +.B \-f +] [ +.B \-m +] [ +.B \-d +] [ +.B \-D +] [ +.B \-v +] +corefile +[ system ] +.SH DESCRIPTION +.I Analyze +is the post-mortem analyzer for the state of the paging system. +In order to use +.I analyze +you must arrange to get a image of the memory (and possibly the +paging area) of the system after it crashes (see +.IR crash (8)). +.PP +The +.I analyze +program reads the relevant system data structures from the core +image file and indexing information from +.B /vmunix +(or the specified file). +to determine the state of the paging subsystem at the point of crash. +It looks at each process in the system, and the resources each is +using in an attempt to determine inconsistencies in the paging system +state. Normally, the output consists of a sequence of lines showing +each active process, its state (whether swapped in or not), its +.I p0br, +and the number and location of its page table pages. +Any pages which are locked while raw i/o is in progress, or which +are locked because they are +.I intransit +are also printed. (Intransit text pages often diagnose as duplicated; +you will have to weed these out by hand.) +.PP +The program checks that any pages in core which are marked as not +modified are, in fact, identical to the swap space copies. +It also checks for non-overlap of the swap space, and that the core +map entries correspond to the page tables. +The state of the free list is also checked. +.PP +Options to +.I analyze: +.TP +.B \-D +causes the diskmap for each process to be printed. +.TP +.B \-d +causes the (sorted) paging area usage to be printed. +.TP +.B \-f +which causes the free list to be dumped. +.TP +.B \-m +causes the entire coremap state to be dumped. +.TP +.B \-v +(long unused) which causes a hugely verbose output format to be used. +.PP +In general, the output from this program can be confused by processes +which were forking, swapping, or exiting or +happened to be in unusual states when the +crash occurred. You should examine the flags fields of relevant processes +in the output of a +.IR pstat (8) +to weed out such processes. +.PP +It is possible to look at the core dump with +.I adb +if you do +.IP +adb /vmunix /vmcore +.br +.lg 0 +/m 80000000 #ffffffff +.LP +which fixes the map of +.I vmcore +so that symbols in data space will work. +Note that the debugger is looking at the physical memory at the point +of crash; you will have to determine which pages of physical memory +virtual pages are in if you wish to look at them. +If +.I analyze +says that a processes page tables are in page 218 (hex of course), then +you can look at them by looking at address 0x80043000 in the dump, i.e. +\*(lq80043000,80/X\*(rq will print the page of page tables. +.SH FILES +/vmunix default system namelist +.SH SEE ALSO +ps(1), crash(8), pstat(8) +.SH AUTHORS +Ozalp Babaoglu and William Joy +.SH DIAGNOSTICS +Various diagnostics about overlaps in swap mappings, missing swap mappings, +page table entries inconsistent with the core map, incore pages which +are marked clean but differ from disk-image copies, pages which are +locked or intransit, and inconsistencies in the free list. +.PP +It would be nice if this program analyzed the system in general, rather +than just the paging system in particular. diff --git a/static/v10/man8/apx.8 b/static/v10/man8/apx.8 new file mode 100644 index 00000000..3d2cd296 --- /dev/null +++ b/static/v10/man8/apx.8 @@ -0,0 +1,33 @@ +.TH APX 8 +.CT 1 sa_nonmortals secur +.SH NAME +apx \- mark an open stream device trusted +.SH SYNOPSIS +.B /etc/apx +[ +.I arg +] +.SH DESCRIPTION +By default, a freshly opened stream device has the +.B APX +bit cleared: it will reject all pex requests. +If invoked without an argument, +.I apx +will set the APX bit on its standard input +(by calling the +.B FIOAPX +control). +If invoked without an argument the +.B APX +bit is cleared. +.I Apx +needs licence +.B T_EXTERN +to run. +It is usually automatically invoked at login time, +provided that the source identifier of the standard input +of the login session is worthy. +.SH FILES +.F /etc/privs +.SH SEE ALSO +.IR pex (4) diff --git a/static/v10/man8/arcv.8 b/static/v10/man8/arcv.8 new file mode 100644 index 00000000..a55ac199 --- /dev/null +++ b/static/v10/man8/arcv.8 @@ -0,0 +1,23 @@ +.TH ARCV 8 +.UC 4 +.SH NAME +arcv \- convert archives to new format +.SH SYNOPSIS +.B /etc/arcv +file ... +.SH DESCRIPTION +.I Arcv +converts archive files +(see +.IR ar (1), +.IR ar (5)) +from 32v and Third Berkeley editions to a new portable format. +The conversion is done in place, and the command +refuses to alter a file not in old archive format. +.PP +Old archives are marked with a magic number of 0177545 at the start; +new archives have a first line ``!<arch>''. +.SH FILES +/tmp/v*, temporary copy +.SH SEE ALSO +ar(1), ar(5) diff --git a/static/v10/man8/arff.8 b/static/v10/man8/arff.8 new file mode 100644 index 00000000..4f082533 --- /dev/null +++ b/static/v10/man8/arff.8 @@ -0,0 +1,64 @@ +.TH ARFF 8 +.CT 1 sa_nonmortals +.SH NAME +arff \- read RT11 files +.SH SYNOPSIS +.B arff +[ +.I key +] +[ +.I name ... +] +.SH DESCRIPTION +.I Arff +reads and writes files +on an RT11 volume, +such as the VAX-11/780 console floppy or +11/750 console tape. +Its actions are controlled by the +.I key +argument, in the manner of +.IR ar (1). +Other arguments +are the names of files +to be read or written. +.PP +The RT11 filesystem restricts names to the character set +.BR a - z0 - 9.\| , +and there are no subdirectories. +Filename arguments are trimmed to the last pathname element +and mapped to lower case. +.PP +The key must contain one of the letters +.LR rxdt , +which mean the same as in +.I ar. +Unlike +.I ar, +however, +.I arff +may reorder files to fit without moving existing files. +.PP +Other key letters are +.TP +v +Verbose. +.TP +.B f +The next argument is the name of the archive instead +of the default +.FR /dev/floppy . +.TP +.B m +Omit the DEC-standard sector interleaving algorithm; +needed when the file isn't a floppy; +e.g. the 11/750 console cassette. +.SH FILES +.F /dev/floppy +.SH BUGS +Floppy errors are handled ungracefully. +.br +The program is too floppy-dependent. +Mapping belongs in the device driver, +or at least shouldn't be the default. diff --git a/static/v10/man8/asd.8 b/static/v10/man8/asd.8 new file mode 100644 index 00000000..1bf1ff51 --- /dev/null +++ b/static/v10/man8/asd.8 @@ -0,0 +1,174 @@ +.TH ASD 8 +.CT 1 sa_auto +.SH NAME +asd \- automatic software distribution +.SH SYNOPSIS +.B /usr/lib/asd/cdaemon +.br +.B /usr/lib/asd/dkinstall +.br +.B /usr/lib/asd/mkspool +.br +.B /usr/lib/asd/rmlocks +.br +.B /usr/lib/asd/udaemon +.SH DESCRIPTION +These programs constitute the innards of the +automatic software distribution system +invoked by +.IR ship (8). +.PP +.I Mkspool +creates an +.SM ASD +spool directory for its invoker (if necessary), +puts a file named +.F dummy +in the directory to prevent +.I cdaemon +from deleting it, +and prints the directory's name. +.PP +.I Udaemon +examines its invoker's +.SM ASD +spool directory in lexical order +for things to do. +To forestall multiple daemons, it first makes an empty file named +.BI L. pid +in the spool directory +and tries to link to it a file +.FR lock . +If the link fails, +.BI L. pid +is removed and +.I udaemon +exits. +.PP +Shipping instructions +appear in pairs of files with +.B .s +and +.B .d +suffixes. +.I Udaemon +examines each status +.RB ( .s ) +file for destination names and +places a network call +to send the corresponding data +.RB ( .d ) +file to +.I dkinstall +at each destination. +.I Dkinstall +verifies the data +and gives it to +.IR inspkg , +see +.IR mkpkg (8). +.PP +A status file contains +zero or more entries, +each of which has one or more lines. +The first line of an entry is a +network address, +with default network +.B dk +and default service +.BR asd , +possibly followed by a blank and a failure report. +An entry with destination +.L # +is a comment and is ignored. +Lines after the first begin with +a tab, +and contain output generated by the entry. +If an entry has output, +it is considered complete +and will be processed no further. +.PP +.I Udaemon +scans each status file once, +and attempts to send the corresponding data file to the destination +for each incomplete entry. +If the attempt fails, +a failure report is appended to the entry, +and it remains incomplete. +If the attempt succeeds, +or the failure is severe, +an error message +or output from +.I dkinstall +is appended to the entry, +which makes the entry complete. +If an entry is completed successfully +but there are no output lines, +the entry is deleted. +.PP +Each instance of +.I udaemon +remembers which network addresses failed with non-severe errors; +entries with the same address in later status files +are given failure status `deferred for sequence.' +.PP +If at least one additional entry was completed, +.I udaemon +sends the new status file to the owner by +.IR mail (1) +after the whole file has been scanned. +If no incomplete entries remain, +both status and data files are removed. +.PP +.I Cdaemon +examines every subdirectory of +.FR /usr/spool/asd , +deletes empty directories and, impersonating the owner, +invokes +.I udaemon +for nonempty directories. +.I Cdaemon +should be run regularly by +.IR cron (8) +with super-user permissions. +.PP +.IR Rmlocks +removes all lock files in +subdirectories of +.FR /usr/spool/asd . +It should be called from +.IR rc (8). +.PP +Entries in an +.SM ASD +spool directory may be made without regard to locks +provided that everything is done in the right +sequence: +(1) call +.IR mkspool ; +(2) create the data file; +(3) create the status file under a temporary name; +(4) rename the status file to end with +.BR .s ; +(5) remove the +.F dummy +file, if present; and +(6) call +.IR udaemon . +.PP +Because +.I mail +will not send an empty file, +a status file must have a comment entry if +acknowledgment is desired after a +successful +.I udaemon +run. +.SH FILES +.BI /usr/spool/asd/ "userid " +user's +.SM ASD +spool directory +.SH SEE ALSO +.IR mkpkg (8), +.IR ship (8) diff --git a/static/v10/man8/atalla.8 b/static/v10/man8/atalla.8 new file mode 100644 index 00000000..3e73746e --- /dev/null +++ b/static/v10/man8/atalla.8 @@ -0,0 +1,62 @@ +.TH ATALLA 8 +.SH NAME +atalla \- initializing a challenge box +.SH DESCRIPTION +It is easiest to initialize an Atalla +(a.k.a. SNK) box at the same time you use the +.B -c +option of +.IR pwx , +before you hand it to the user, not in the user's presence. +To initialize the box: +freak it out by giving five consecutive wrong PIN entries, for example by +pushing the sequence +.B ON +.B 0 +.B ENTER +five times. +The box's display should now read +.BR "ES0 ----" , +you push +.B 1 +.BR ENTER . +The display now reads +.BR "ES1 ----" , +you now enter eight bytes of secret key, which you may ask +.I pwx +to invent, and which the user will not know. +Each byte is represented by three octal digits, in the range +.B 000 +through +.BR 277 , +so it takes 24 key strokes to enter the secret key. +Now push +.BR ENTER , +and a check sum of form +.B "C xxxxxxxx" +is displayed. +Push +.B ENTER +again +and another check sum is displayed, +this time of form +.BR "F xxxxxxxx" . +Push +.B ENTER +yet again +and +the display reads +.BR "EP1 ----" . +At this point the box may be handed to the user. +The user enters a personal password (his ``PIN'') +of 4 through 8 digits' length, +followed by +.BR ENTER , +and again, as a check. +Thereafter the user must +type his personal password whenever he uses the box. +Instruct the user not to divulge his personal password, and +promise the user you will not divulge +his secret key. +.SH SEE ALSO +.IR passwd (1) diff --git a/static/v10/man8/authmgr.8 b/static/v10/man8/authmgr.8 new file mode 100644 index 00000000..a20c22e2 --- /dev/null +++ b/static/v10/man8/authmgr.8 @@ -0,0 +1,204 @@ +.TH AUTHMGR 8 +.CT 1 sa_auto secur +.SH NAME +authmgr \- authenticate users and make secure calls +.SH SYNOPSIS +.B authmgr +.BI [ "options ..." ] +.SH DESCRIPTION +.I Authmgr +receives authentication requests from the network via +.IR svcmgr (8), +authenticates the requesting user, and redials their +call using one of the network interfaces, such as +.IR dkmgr (8). +The actual method used to authenticate the user depends +on the command line arguments and the environment at the +time +.I authmgr +is executed. +.PP +One mode is used when a user connects directly to the authentication +service. +In this mode, the user is asked to enter a login name (unless +there is a login name present in the CSOURCE environment variable). +The user is then challenged to encode some character string with +their challenge box (or possibly just enter their password), and +enter this as a response. +If the response is correct (i.e. the user had the correct encryption +key or password), the user is asked to enter the name of a new +destination, and the call is redialed to this new destination. +.PP +The other mode is used when a call to a service using the V9 authentication +protocol is rerouted through the authentication server (this is currently +only possible if the call was placed over the datakit, through a trunk). +In this case, the authentication server uses an extension of the "OK"/"NO" +protocol used by +.IR con (1). +Here, +.I authmgr +responds to a connection with a string ``CH''. +The calling program should prompt the user for a login name, and +send that login back, followed by a newline. +.I Authmgr +responds with a challenge string, up to 60 characters long, followed +by a newline (the challenge will be printable ASCII). +The calling process must encode this string (unless it is blank; then +it should obtain the user's password), and send this response back, also +terminated by a newline. +If the response is correct, the "OK"/"NO" protocol continues as +normal (that is, the call is automatically redialed by the server +without further intervention); otherwise, the "CH" challenge is +repeated. +.PP +The options are +.TP +.B -n +Do not prompt the user for a new destination, even if we don't have +one already. +This option is useful for authenticating an entire host (or a +powerful terminal) as one user. +The call will automatically be redialed in a special way. +.TP +.BI -f file +Use +.I file +as the configuration file rather than the default. +.PP +When a call is redialed, the security ID of the new call is that +of the authentication server itself, rather than the original security ID. +.PP +Much of the operation of the server is keyed off its configuration +file. Each line in the file contains an initial keyword, followed +by a number of arguments (there are no continuation lines), a line +starting with a ``#'' is a comment. The various keywords are: +.TP +.BI admin " address ..." +This defines the names of the administrators of the authentication server. +The addresses (up to 10 may be specified) are the electronic mail +addresses of the administrators. These names will received mail +if the server detects a possibly security violation. +.TP +.BI failures " number" +This sets the maximum number of failures to allow an individual +instantiation of +.I authmgr +before the connection is closed and the administrators are notified. +The default is 3. +.TP +.BI disallow " login" +Defines a login name that may not authenticate itself, even if it +exists in the keys file. +Any number of +.B disallow +lines may appear in the configuration file. +.TP +.BI usepasswd " regexp" +Tells +.I authmgr +that despite what the key file says, if the source of this call +matches +.IR regexp , +the user should be requested to enter their password from the +/etc/passwd file, rather than doing some kind of key encryption. +This is useful when +.I authmgr +is being used for authentication inside a trusted network, and +using encryption boxes would be too cumbersome. +.TP +.BI setuser " regexp user" +Map all calls from machines matching +.IR regexp +to +.IR user . +If the +.I user +field is empty, prompt for the login name. This can be useful +for calls coming from untrusted machines. +.TP +.BI setsvc " regexp service" +If a call comes from a machine matching +.IR regexp , +set the default service of the redialed call to +.IR service . +.TP +.BI setlog " regexp file" +Log calls from machines matching +.I regexp +in +.IR file . +.TP +.BI secmapid " regexp securityid" +If the security ID of the incoming call matches +.I regexp +(in the format of +.IR regexp (3)) +the outgoing security ID will be +.IR securityid . +There must be at least one +.B secmapid +lines in the configuration file, that of the default (``.*'') +outgoing security ID. +Because of the way the security ID mappings are stored, any +mappings that contain wildcards should appear after those without; +the mappings are tried against an incoming security ID in top-down +order (this implies that the default mapping should appear last). +.PP +The keys are stored in a key file. +Each line in the key file is of the form +.RS +.sp +login:keytype:key encoding: +.sp +.RE +Login is a usual login name. +Keytype is the type of the key (more than one encryption box type +are supported by +.IR authmgr ). +The key encoding is the key for this user; this encoding differs +depending on the keytype. +Currently, two key types recognized. +One is +.BR atalla , +for the Atalla Confidante style key (the key encoding for this +type is 8 groups of octal numbers between 0 and 0377, specifying the DES +key kept in this box, for example ``010 342 176 214 212 101 414 527''). +The other is +.BR passwd , +which means the key encoding is a standard password file 13 character +password entry (if the key encoding is blank, +.I authmgr +look in the password file for the password). +Because these keys are stored +in the clear, this file should be well protected, and probably +should be encrypted. +.PP +Currently, the authentication server may be connected to at the +service point ``security'' on the security host. +If you use the service ``gsecurity'', you get the no-redial +option of the server. +.SH FILES +.nf +.F /usr/net/authmgr.conf +.F /usr/net/authmgr.keys +.F /etc/passwd +.fi +.SH "SEE ALSO" +.IR con (1), +.IR regexp (3), +.IR svcmgr (8), +.IR dkmgr (8) +.SH BUGS +There is currently no support for encrypting the keys file. +.br +The only current use for this is over the datakit, and the +regular expressions in the secmapid line are not of the same +format as would be expected for wildcard datakit names. +.br +Users will still have to enter a login and password if the +service they redial doesn't believe +.IR authmgr . +.br +The +.I secmapid +parameter is currently ignored. diff --git a/static/v10/man8/backup.8 b/static/v10/man8/backup.8 new file mode 100644 index 00000000..793f463e --- /dev/null +++ b/static/v10/man8/backup.8 @@ -0,0 +1,90 @@ +.TH BACKUP 8 +.CT 1 sa_nonmortals +.SH NAME +backup \- backup client administration +.SH SYNOPSIS +.B /usr/lib/backup/sel +.PP +.B /usr/lib/backup/fcheck +.I maxsize +.I maxdays +.I files ... +.PP +.B /usr/lib/backup/act +[ +.I stat +] +.SH DESCRIPTION +These programs select and back up files +to the incremental file backup system, +.IR backup (1). +.PP +.I Sel +prints on the standard output +a list of filenames that might need to be backed up. +The initial version +picks out files that have been changed in the past few days, +skipping huge files +and eliding boring names like +.BR core . +.I Sel +is a shell script; +the local administrator is expected to customize it. +.PP +.I Fcheck +is a fast, +specialized file scanning program, +used by +.IR sel . +It examines each of the +.IR files , +descending into directories, +and prints the name of each file +that has been changed in the last +.I maxdays +days and is smaller than +.I maxsize +kilobytes. +Symbolic links are followed when presented as arguments, +examined but not followed otherwise. +.PP +.I Act +reads a list of filenames from the standard input. +It searches the backup database +.IR backup (5) +for the current version of each file, +and backs up files that aren't registered. +.PP +By default, +.I act +sends errors by +.IR mail (1) +to user +.BR backup . +If the +.I stat +argument is non-empty, +errors and additional comforting chatter +are printed on the standard output instead. +.PP +One way to request automatic backups is to run +.IP +.L +/usr/lib/backup/sel | /usr/lib/backup/act +.LP +regularly from +.IR cron (8). +Particular files may be backed up by hand at any time +by running +.I act +with a list of filenames. +There are no special permissions involved; +any user may run +.IR act . +.SH SEE ALSO +.IR backup (1), +.IR backup (5) +.br +A. Hume, `The File Motel: An Owner's Manual', +this manual, +Volume 2 diff --git a/static/v10/man8/blmount.8 b/static/v10/man8/blmount.8 new file mode 100644 index 00000000..de9f167e --- /dev/null +++ b/static/v10/man8/blmount.8 @@ -0,0 +1,23 @@ +.TH BLMOUNT 8 +.CT 1 sa_nonmortals +.SH NAME +blmount \- mark directories blind +.SH SYNOPSIS +.B /etc/blmount +[ +.B -u +] +.I directory +.SH DESCRIPTION +.I Blmount +without options +mounts the named directory on itself as a blind file system +.IR bl (4) . +With option +.BR -u , +the treatment is reversed. +The +.I directory +must be on a traditional (disk) file system. +.SH SEE ALSO +.IR bl (4) diff --git a/static/v10/man8/bproc.8 b/static/v10/man8/bproc.8 new file mode 100644 index 00000000..fd4f5a77 --- /dev/null +++ b/static/v10/man8/bproc.8 @@ -0,0 +1,235 @@ +.pa 1 +.he 'BOOT PROCEDURES (VIII)'2/6/73'BOOT PROCEDURES (VIII)' +.ti 0 +NAME bos, maki, vcboot, msys, et__ al__. +.sp +.ti 0 +DESCRIPTION +.br +.in 8 +On +the RF disk, the highest 16K words are +reserved for stand-alone programs. +These 16K words are allocated as follows: +.sp +bos (1K) +.br +Warm UNIX (7K) +.br +Cold UNIX (8K) +.sp +The program bos___ (Bootstrap Operating System) +examines the console switches and executes +one of several internal programs depending on the setting. +The following settings are currently recognized: +.sp +.in +8 +.ti -8 +??? Will read Warm UNIX from +the RF into core location 0 and transfer to 600. +.sp +.ti -8 +1 Will read Cold UNIX from the +RF into core location 0 and transfer to 600. +.sp +.ti -8 +10 Will dump all of memory +from core location 0 onto DECtape drive 7 +and then halt. +.sp +.ti -8 +20 Will read 256 words from RK0 into +core 0 and transfer to zero. +This is the procedure to boot +DOS from an RK. +.sp +.ti -8 +40 This is the same as 10 above, but +instead of halting, UNIX warm is loaded. +.sp +.ti -8 +0 Will load a standard UNIX binary paper tape +into core location 0 and transfer to 0. +.sp +.ti -8 +77500 Will load the standard DEC absolute and binary +loaders and transfer to 77500. +.sp +.in 8 +All manual methods of booting the system involve +manipulation of the console switches. +In order for this to be possible, +the panel must be unlocked +and the machine must be halted. +Also, remember that at the time UNIX comes up, +the console switches must contain 773030 +for a single-user system; anything else gives +a multi-user system. + +There are four temperatures of boots. +They are: + +.in +4 +Hot boot: restart the system without refreshing +its code, that is simply by transferring to +its start. +The only use for this procedure is if the +system has been patched and one doesn't wish +to redo the patches. +The procedure is: + + 600 in switches + Load address + (773030 in switches for single-user system) + start + +Warm boot: refresh system code from the RF disk, but +the "panic" routine must be in core. +Best for general use if it works, since +outstanding I/O +is cleaned up. +Procedure: + + 602 in switches + load address + (773030 in switches for single-user system) + start (flushes any I/O, then executes bos___) + +Cool boot: RF disk is OK, but nothing in core. +Procedure: + + UTIL DECtape on drive 0 + 773030 in switches + load address + (602 in switches for multi-user system) + start + type "boot" on console tty to load bos___ + +Cold boot: nothing in core, nothing on RF. +Best to have an expert around for this +one. +Procedure: + + INIT DECtape on drive 0 + 773030 in switches + load address + 1 in switches + start + (machine halts. last chance to preserve RF!) + 773030 in switches + continue + (reads in basic files) + +UNIX is then up, but for various reasons, one should +do a warm boot (single user) right away. +At this point also, one might +consider whether the INIT tape UNIX is the +latest version. +If there is reason for doubt, +mount the /sys disk pack, change to directory +/sys/sys, do "msys u unix", and reboot. +Then get the /bin-/etc-/lib tape which contains +the rest of of the RF disk, +and do an "mt x". +Conceivably, "create errors" due to lack of some +directories will occur; make the directories, +then try again. +Set the date correctly; the system starts off +at time 0. + +At this point UNIX is in full operation and +can be rebooted for +a multi-user system. +.sp +.in 8 +Here is what happens during a cold boot: +the INIT tape contains a program called +.ul +vcboot. +The ROM program reads vcboot +from the tape into +core location 0 and transfers to it. +vcboot then reads 16K words from +the DECtape (blocks 1-32) +and copies the data to the highest 16K words of +the RF. +Thus this initializes the read-only part of the RF. +vcboot then reads in bos___ and executes it. +bos___ reads in Cold UNIX and executes that. +Cold UNIX halts for a last chance before +it completely initializes the RF file system. +When continue is pressed, +Cold UNIX initializes the RF. +It then reads the DECtape for initialization files +starting from block 33. +Normal operation then commences +with the execution of "/etc/init". +.sp +The INIT tape is made by the program maki____ +running under UNIX. +maki____ writes vcboot______ on block 0 of +.ul +/dev/tap7. +It then copies the RF 16K words (using +.ul +/dev/rf0) +onto blocks 1 thru 32. +It has internally a list of files to +be copied from block 33 on. +This list follows: +.sp +.nf +.in +8 +/etc/init +/bin/chmod +/bin/date +/bin/login +/bin/ls +/bin/mkdir +/etc/mount +/bin/sh +/bin/tap +/bin/mt +.in -8 +.fi +.sp +Thus this is the set of programs available after a cold boot. +init____ and sh__ are mandatory. +For multi-user UNIX, +getty_____ and login_____ are also necessary. +mkdir_____ is necessary due to a bug in tap___. +mt__, tap___ and mount_____ are useful to +bring in new files. +As soon as possible, date____ should be done. +That leaves ls__ and chmod_____ as frosting. +.sp +The last link in this incestuous +daisy chain is the program msys____. +.sp + msys____ char file +.sp +will copy the file file____ onto the +RF read only slot specified by the character char____. +Char is taken from the following set: +.sp + b_ bos + u_ Warm UNIX + 1_ Cold UNIX +.sp +.in 16 +.ti 0 +FILES /dev/rf0, +/dev/tap? +.sp +.ti 0 +SEE ALSO init(VII), +tap(I), +sh(I), +mkdir(I) +.sp +.ti 0 +DIAGNOSTICS -- +.sp +.ti 0 +BUGS This +section is very configuration dependent. diff --git a/static/v10/man8/check.8 b/static/v10/man8/check.8 new file mode 100644 index 00000000..9f6e030b --- /dev/null +++ b/static/v10/man8/check.8 @@ -0,0 +1,50 @@ +.pa 1 +.he 'CHECK (VIII)'1/20/73'CHECK (VIII)' +.ti 0 +NAME check -- file system consistency check +.sp +.ti 0 +SYNOPSIS check_____ [ filesystem [ blockno918 ... ] ] +.sp +.ti 0 +DESCRIPTION check_____ +will examine a file system, +build a bit map of used blocks, +and compare this bit map against +the bit map maintained on the file system. +If the file system is not specified, +a check of all +of the normally mounted file systems +is performed. +Output includes the number of files on the file system, +the number of these that are 'large', the number +of indirect blocks, +the number +of used blocks, and the number of free blocks. +.sp +check_____ works by examining the i-nodes +on the file system and is entirely +independent of its directory hierarchy. +The file system may be, +but need not be, mounted. + +.ti 0 +FILES /dev/rf?, +/dev/rk?, +/dev/rp? +.sp +.ti 0 +SEE ALSO find(I), ds(I) +.sp +.ti 0 +DIAGNOSTICS Diagnostics are produced for +blocks missing, duplicated, and bad block addresses. +Diagnostics are also produced for block numbers passed as parameters. +In each case, the block number, i-number, and +block class (i_ = inode, x_ indirect, f_ free) is printed. +.sp +.ti 0 +BUGS The +checking process is two pass in nature. +If checking is done on an active file system, +extraneous diagnostics may occur. diff --git a/static/v10/man8/chk.8 b/static/v10/man8/chk.8 new file mode 100644 index 00000000..54114b62 --- /dev/null +++ b/static/v10/man8/chk.8 @@ -0,0 +1,21 @@ +.pa 1 +.he 'CHK (VIII)'1/20/73'CHK (VIII)' +.ti 0 +NAME chk -- check + dcheck +.sp +.ti 0 +SYNOPSIS chk +.sp +.ti 0 +DESCRIPTION This +command file does a check_____ and a dcheck______ of all of the normally mounted +file systems. +.sp +.ti 0 +FILES /dev/[fkp]* +.sp +.ti 0 +SEE ALSO check (VIII), dcheck (VIII) +.sp +.ti 0 +DIAGNOSTICS see "SEE ALSO" diff --git a/static/v10/man8/chown.8 b/static/v10/man8/chown.8 new file mode 100644 index 00000000..ba114a64 --- /dev/null +++ b/static/v10/man8/chown.8 @@ -0,0 +1,47 @@ +.TH CHOWN 8 +.CT 1 sa_nonmortals secur +.SH NAME +chown \- change owner or group +.SH SYNOPSIS +.B /etc/chown +.IB owner , group +.I file ... +.SH DESCRIPTION +.I Chown +changes the owner of the +.I files +to +.I owner +and the groupid to +.IR group . +Either +.I owner +or +.I group +may be omitted +to leave the owner or groupid unchanged. +.PP +.I Owner +may be either a decimal userid or +a login name found in +.FR /etc/passwd . +.I Group +may be either a decimal groupid or +a group name found in +.FR /etc/group . +.PP +The owner of a file +may change its group +to that of the current process. +Other changes are restricted to the super-user. +.SH FILES +.F /etc/passwd +.br +.F /etc/group +.SH "SEE ALSO" +.I chown +in +.IR chmod (2), +.IR passwd (5), +.IR chmod (1), +.IR chdate (1) diff --git a/static/v10/man8/chuck.8 b/static/v10/man8/chuck.8 new file mode 100644 index 00000000..087b6d50 --- /dev/null +++ b/static/v10/man8/chuck.8 @@ -0,0 +1,116 @@ +.TH CHUCK 8 +.CT 1 sa_nonmortals +.SH NAME +chuck \- a file system checking program +.SH SYNOPSIS +.B /etc/chuck +[ +.I option ... +] +.I device +.PP +.B /etc/chuck +.B -M +.I blocks +.I device +.PP +.B /etc/upchuck +[ +.B -w +] [ +.B -p +.I program +] +.SH DESCRIPTION +.PP +.I Chuck +checks and optionally repairs the file system on the named +.I device. +It is normally invoked by +.I upchuck +by +.IR rc (8) +during reboots. +The +.B -w +flag to +.I upchuck +is passed on to +.I program. +If +.I program +is not present, the default is +.FR /etc/chuck . +(Try, as super-user, +.B "/etc/upchuck -p /bin/echo +to see the normal arguments to +.IR chuck .) +If +.I upchuck +can read the raw version of +.I device, +it will, except for the root file system. +.PP +The options are +.TP +.B -w +Try to do standard repairs. +.TP +.BI -b " blocksize +Specify file system block size; default is 4096. +.TP +.B -i +Interactive. +Ask approval for each change. +.TP +.BI -I " inode ... +.br +.ns +.TP +.BI -B " block ... +Report on inodes or blocks specified by number. +.TP +.B -v +Verbose. +Give more commentary. +.PP +.I Chuck +can also make a new file system: +.B "chuck -M" +.I size device +makes a bitmapped file system (only) +of +.I size +4096-byte blocks +on +.IR device . +It asks approval before writing. +.SH FILES +.F /etc/fstab +.SH "SEE ALSO" +.IR fstab (5), +.IR filsys (5), +.IR fsck (8), +.IR reboot (8) +.SH BUGS +.I Chuck +does not replace real expertise. +It will not automatically repair a file system with duplicate blocks. +In complicated situations it may have to be run +several times to get complete consistency. +.br +It will not recover from I/O errors in reading the inodes, +and does not yet extend +.F lost+found +when necessary. +.br +It uses memory freely (about 12 bytes per file system block +and 84 bytes per inode). +.br +.I Chuck +is still experimental, +and acts the part. +Error messages are usually inscrutable. +.br +It believes even preposterous super-blocks and +consequently can get core images. diff --git a/static/v10/man8/cl.8 b/static/v10/man8/cl.8 new file mode 100644 index 00000000..75a0de9e --- /dev/null +++ b/static/v10/man8/cl.8 @@ -0,0 +1,100 @@ +.TH CL 8 +.CT 1 sa_nonmortals +.SH NAME +cl, integrity \- file system label check +.SH SYNOPSIS +.B /etc/cl +[ +.IR specfile " | " dir +] ... +.PP +.B /etc/integrity +[ +.I rootdir +] +.SH DESCRIPTION +.I Cl +examines file trees for correctness of labels. +Each +.I specfile +argument names a file containing a description +of the labels expected in a given subtree of a file system. +Each line of a +.I specfile +has the form +.IP +.L +filename uid,gid mode capabilities licenses label +.LP +User and group ids are specified in the style of +.IR chown (8). +The mode is specified in the style of +.IR chmod (2); +only the 07777 bits are significant. +Capabilities and licenses are in the style of +.IR atopriv ; +see +.IR labtoa (3). +The label is in the style of +.IR atolab, +without capabilities or licenses. +.PP +The first valid line names the root of the tree in question. +Subsequent lines name particular files in the tree. +A report is made for each `suspicious' file and for each +particular file which does +not match its description in +.IR specfile . +.LP +A suspicious file is a file that is not named in the +.I specfile +for which one of the following holds: +.IP +The label has flag +.B L_UNDEF +or +.BR L_YES . +.br +The file is a special file the label flag is +.BR L_NO . +.br +The file is not a special file the label flag is not +.BR L_NO . +.br +The lattice value of the label is not dominated by the +label in the first line of +.IR specfile . +.br +The capability or license is not dominated by the corresponding +value in the first line of +.IR specfile . +.LP +Each named directory argument +.I dir +is treated as if there were a +.I specfile +argument +consisting of just a single line +.IP +.EX +\fIdir\fP bin,bin 666 ----- ----- 0000... +.EE +.I Integrity +surveys the directory tree dependent from +.I rootdir, +or +.L / +if no +.I rootdir +is given. +It reports non-bottom labels, which are possible signs +of loss of integrity \- modification without privilege. +The search cuts off at directories with non-bottom labels. +.SH "SEE ALSO" +.IR getflab (2), +.IR ftw (3), +.IR lcheck (8) +.SH BUGS +Extraneous diagnostics +may be produced if this command is applied to +active file systems. diff --git a/static/v10/man8/clri.8 b/static/v10/man8/clri.8 new file mode 100644 index 00000000..68ec27af --- /dev/null +++ b/static/v10/man8/clri.8 @@ -0,0 +1,41 @@ +.pa 1 +.he 'CLRI (VIII)'1/20/73'CLRI (VIII)' +.ti 0 +NAME clri -- clear i-node +.sp +.ti 0 +SYNOPSIS clri i-number [ file system ] +.sp +.ti 0 +DESCRIPTION clri____ +writes zeros on the 32 bytes occupied by the i-node +numbered +.ul +i-number. +If the +.ul +file system +argument is given, the i-node resides on +the given device, otherwise on a +default file system. +The file system argument +must be a special file +name referring to a device +containing a file system. + +After clri____, any blocks +in the affected file +will show up as "missing" in a check_____ of +the file system. + +Read and write permission is required on the specified +file system device. +The i-node becomes allocatable. + +The primary purpose of this routine +is to remove a file which +for some reason appears in no +directory. +.sp +.ti 0 +DIAGNOSTICS "error" diff --git a/static/v10/man8/config.8 b/static/v10/man8/config.8 new file mode 100644 index 00000000..dc215527 --- /dev/null +++ b/static/v10/man8/config.8 @@ -0,0 +1,48 @@ +.TH CONFIG 8 +.SH NAME +config \- configure a Unix kernel +.SH SYNOPSIS +.B /etc/config +[ machine ] +.SH DESCRIPTION +.I Config +generates files used to build a Unix kernel +for the named +.IR machine . +The working directory should be +.I /usr/sys/conf +or +.IR /usr/sys/ machine; +if the latter, +.I machine +may be omitted from the command. +.PP +A machine description is expected in +.RI machine /conf ; +a makefile, +a number of header files, +and some C and assembler programs +are generated from the description. +.PP +The usual way to configure a new system is: +.nf +mkdir /usr/sys/newmach +cd /usr/sys/newmach +(create conf) +/etc/config +make +.fi +.SH FILES +\&../conf/makefile makefile template +.br +\&../conf/files list of kernel source files +.br +files more sources specific to this machine +.br +\&../conf/devices list of device handlers +.br +devices more devices specific to this machine +.br +conf machine description +.SH SEE ALSO +config(5) diff --git a/static/v10/man8/cpp.8 b/static/v10/man8/cpp.8 new file mode 100644 index 00000000..fa52b773 --- /dev/null +++ b/static/v10/man8/cpp.8 @@ -0,0 +1,114 @@ +.TH CPP 8 +.CT 1 prog_c +.SH NAME +cpp \- C language preprocessor +.SH SYNOPSIS +.B /lib/cpp +[ +.I option ... +] +[ +.I ifile +[ +.I ofile +] +] +.SH DESCRIPTION +.I Cpp\^ +interprets preprocessor directives +and does macro substitution +for +.IR cc (1) +and other compilers. +The input +.I ifile +and output +.I ofile +default to standard input and standard output respectively. +.PP +The options are: +.TP +.B -P +Do not place line number markings in output. +.TP +.B -C +Do not remove comments. +.TP +.BI -U name\^ +.PD 0 +.TP +.BI -D name\^ +.TP +.BI -D name=def\^ +.TP +.BI -I dir\^ +Same as in +.IR cc (1). +.B -U +overrides +.BR -D . +.PD +.TP +.B -H +Report all included files on standard error file,. +.TP +.B -M +Attach modification date to file names in line number +directives thus: +.IB file @ modtime, +where modtime is the integer number of seconds since the epoch. +.TP +.B -T +Truncate preprocessor symbols to eight characters. +.TP +.BI -Y dir +Use +.I dir +instead of +.F /usr/include +as the last resort in searching for include files. +.PP +The output file contains processed text sprinkled +with lines that show the original input line numbering: +.IP +.B # +.I linenumber +.L +"\fIifile\fP" +.PP +The input language is as described in the reference, +with a few additions: +.PP +The +.B # +.I linenumber +marks placed in the output are accepted as an alternative +to the official +.B #line +directive. +.PP +These symbols are predefined in various implementations: +.IP +.EX +ibm gcos os tss unix +interdata pdp11 u370 u3b u3b5 vax +RES RT +lint +.EE +.PP +Preprocessor formal parameters are recognized within +quoted strings in the replacement text. +.PP +When comments are removed they are replaced by null strings; +this unofficial feature makes it possible to construct +identifiers by concatenation. +.SH FILES +.TF /usr/include +.TP +.F /usr/include +standard directory for include files +.SH SEE ALSO +B. W. Kernighan and D. M. Ritchie, +.I The C Programming Language, +Prentice-Hall, +1988 diff --git a/static/v10/man8/crash.8 b/static/v10/man8/crash.8 new file mode 100644 index 00000000..e38a694c --- /dev/null +++ b/static/v10/man8/crash.8 @@ -0,0 +1,268 @@ +.TH CRASH 8 VAX-11 +.UC 4 +.SH NAME +crash \- what happens when the system crashes +.SH DESCRIPTION +This section explains what happens when the system crashes and how +you can get a crash dump for analysis of non-transient problems. +.PP +When the system crashes voluntarily it prints a message of the form +.IP +panic: why i gave up the ghost +.LP +on the console, and then invokes an automatic reboot procedure as +described in +.IR reboot (8). +If the auto-reboot switch is off on the console, then the processor +will simply halt at this point. +Otherwise the registers and the top few locations of the stack will +be printed on the console, and then the system will check the disks +and (unless some unexpected inconsistency is encountered), resume +multi-user operations. +.PP +The system has a large number of internal consistency checks; if one +of these fails, then it will panic with a very short message indicating +which one failed. In the absence of a dump, little can be done about +one of these. If the problem recurs, you should arrange to get a dump +for further analysis by running with auto-reboot disabled during normal +working hours and then following the procedure described below. +.PP +The most common cause of system failures is hardware failure, which +can reflect itself in different ways. Here are the messages which +you are likely to encounter, with some hints as to causes. +Left unstated in all cases is the possibility that hardware or software +error produced the message in some unexpected way. +.TP +IO err in push +.ns +.TP +hard IO err in swap +The system encountered an error trying to write to the paging device +or an error in reading critical information from a disk drive. +You should fix your disk if it is broken or unreliable. +.TP +Timeout table overflow +.ns +.TP +ran out of bdp's +.ns +.TP +ran out of uba map +These really shouldn't be panics, but until we fix up the data structures +involved, running out of entries causes a crash. If the timeout table +overflows, you should make it bigger. If you run out of bdp's or uba map +you probably have a buggy device driver in your system, allocating and +not releasing UNIBUS resources. +.TP +KSP not valid +.ns +.TP +SBI fault +.ns +.TP +Machine check +.ns +.TP +CHM? in kernel +These indicate either a serious bug in the system or, more often, +a glitch or failing hardware. For the machine check, the top part of +the resulting stack frame gives more information. You can refer to a +VAX 11/780 System Maintenance Guide for information on machine checks. +If machine checks or SBI faults recur, check out the hardware or call +field service. If the other faults recur, there is likely a bug somewhere +in the system, although these can be caused by a flakey processor. +Run processor microdiagnostics. +.TP +trap type %d, code=%d +A unexpected trap has occurred within the system; the trap types are: +.RS +.TP 10 +0 +reserved addressing mode +.br +.ns +.TP 10 +1 +privileged instruction +.br +.ns +.TP 10 +2 +BPT +.br +.ns +.TP 10 +3 +XFC +.br +.ns +.TP 10 +4 +reserved operand +.br +.ns +.TP 10 +5 +CHMK (system call) +.br +.ns +.TP 10 +6 +arithmetic trap +.br +.ns +.TP 10 +7 +reschedule trap (software level 3) +.br +.ns +.TP 10 +8 +segmentation fault +.br +.ns +.TP 10 +9 +protection fault +.br +.ns +.TP 10 +10 +trace pending (TP bit) +.RE +.IP +The favorite trap type in system crashes is trap type 9, indicating +a wild reference. The code is the referenced address. If you look +down the stack, just after the trap type and the code are the pc and +the ps of the processor when it trapped, showing you where in the +system the problem occurred. These problems tend to be easy to track +down if they are kernel bugs since the processor stops cold, but random +flakiness seems to cause this sometimes, e.g. we have trapped with +code 80000800 three times in six months as an instruction fetch went across +this page boundary in the kernel but have been unable to find any reason +for this to have happened. +.TP +init died +The system initialization process has exited. This is bad news, as no new +users will then be able to log in. Rebooting is the only fix, so the +system just does it right away. +.PP +That completes the list of panic types you are likely to see. +Now for the crash dump procedure: +.PP +At the moment a dump can be taken only on magnetic tape. +Before you do anything, be sure that a clean tape is mounted with a ring-in +on the tape drive if you plan to make a dump. +.PP +Write the date and time on the console log. +Use the console commands to examine the registers, program status long word, +and the top several locations on the stack. +A suggested command sequence, which is executed by the \*(lq@DUMP\*(rq +console command script, is: +.DS +.nf + E PSL<return> + E R0/NE:F<return> + E SP<return> + E/V @ /NE:40<return> +.fi +.DE +If hardware problems dictate a special set of commands be executed when +the system crashes, a sequence of commands can be saved using the console +command \*(lqLINK\*(rq to be reexecuted with \*(lqPERFORM\*(rq (which can be +abbreviated \*(lqP\*(rq). +If a dump is to be taken on magnetic tape (this is a good idea +in most any case where the cause of the crash is not immediately obvious) +then the following commands will (should) be executed: +.DS +.nf + D PSL 0<return> + D PC 80000200<return> + C<return> +.fi +.DE +These commands are actually part of the standard \*(lq@DUMP\*(rq script. +This should write a copy of all of memory +on the tape, followed by two EOF marks. +Caution: +Any error is taken to mean the end of memory has been reached. +This means that you must be sure the ring is in, +the tape is ready, and the tape is clean and new. +.PP +If there are not 40(hex) locations active on the kernel stack when the +procedure is begun, then the console may begin to print error diagnostics. +You can stop this by hitting \*(lq^C\*(rq (control-C), and then give the +last three commands above. +.PP +If the dump fails, you can try again, +but some of the registers will be lost. +See below for what to do with the tape. +.PP +To restart after a crash, follow the directions in +.IR reboot (8); +if the virtual memory subsystem is suspected as the cause of the crash, +then a version of the system other than \*(lqvmunix\*(rq should be booted +which will leave the paging areas temporarily intact +for use by the post-mortem analysis program +.I analyze. +After checking your root file system consistency with +.IR fsck (8), +you can read the core dump tape into the file /vmcore with +.IP +dd if=/dev/rmt0 of=/vmcore bs=20b +.LP +It does not work to use just +.IR cp (1), +as the tape is blocked. +With the system still in single-user mode, run the analysis program +.I analyze, +e.g.: +.IP +analyze \-s /dev/drum /vmcore /vmunix +.LP +and save the output. +Then boot up +\*(lqvmunix\*(rq +and let it do the automatic reboot, i.e. to boot multi-user from +an RM03/RM05/RP06 on the MASSBUS +.IP +>>> BOOT RPM +.PP +After rebooting, to analyze a dump you should execute +.I "ps \-alxk" +to print the process table at the time of the crash. +Use +.IR adb (1) +to examine +.IR /vmcore . +The location +.I dumpstack\-80000000 +is the bottom of a stack onto which were pushed the stack pointer +.BR sp , +.B PCBB +(containing the physical address of a +.IR u_area ), +.BR MAPEN , +.BR IPL , +and registers +.BR r13 \- r0 +(in that order). +.BR r13 (fp) +is the system frame pointer and the stack is used in standard +.B calls +format. Use +.IR adb (1) +to get a reverse calling order. +In most cases this procedure will give +an idea of what is wrong. +A more complete discussion +of system debugging is impossible here. +See, however, +.IR analyze (8) +for some more hints. +.SH "SEE ALSO" +analyze(8), reboot(8) +.br +.I "VAX 11/780 System Maintenance Guide" +for more information about machine checks. +.SH BUGS diff --git a/static/v10/man8/cron.8 b/static/v10/man8/cron.8 new file mode 100644 index 00000000..3a58416f --- /dev/null +++ b/static/v10/man8/cron.8 @@ -0,0 +1,86 @@ +.TH CRON 8 +.CT 1 sa_auto +.SH NAME +cron \- clock daemon +.SH SYNOPSIS +.B /etc/cron +.SH DESCRIPTION +.I Cron +executes commands at specified dates and times +according to the instructions in the file +.FR /etc/crontab . +It should be run once from +.IR rc (8). +.PP +.I Crontab +entries are lines of seven fields separated by blanks or tabs: +.IP +.I +login minute hour day month weekday command +.PP +.I Login +is the login name under +whose userid and groupid +the command should be executed. +The next five fields are integer patterns for +.PD0 +.RS +.TP \w'day\ of\ month\ \ 'u +minute +0-59 +.TP +hour +0-23 +.TP +day of month +1-31 +.TP +month of year +1-12 +.TP +day of week +0-6; 0=Sunday +.PD +.RE +.PP +Each pattern may +contain a number in the range above; +two numbers separated by +a hyphen +meaning an inclusive range; +a list of numbers separated by +commas meaning any of the numbers; +or an asterisk meaning all legal values. +.PP +The last field is a string +to be executed by the shell, +after replacing +.L % +with newline. +.PP +It is wise to spread the times of activities to avoid +bogging the system down at favorite hours. +.PP +.I Cron +examines +.I crontab +every minute. +.SH EXAMPLES +.EX +daemon 17 3 * * * /usr/bin/calendar - # reminders at 0317 +adm 15 4 1,15 * * ac -p | mail adm # bimonthly accounts +root 0 12 22-28 11 4 /etc/wall Time for Thanksgiving dinner +.EE +.SH FILES +.F /etc/crontab +.SH SEE ALSO +.IR at (1) +.SH BUGS +The behavior of +.L % +in +.I crontab +entries is nonstandard. +Strings following +.L % +should be delivered to the command as standard input. diff --git a/static/v10/man8/dcheck.8 b/static/v10/man8/dcheck.8 new file mode 100644 index 00000000..9f9d8eec --- /dev/null +++ b/static/v10/man8/dcheck.8 @@ -0,0 +1,44 @@ +.pa 1 +.he 'DCHECK (VIII)'1/20/73'DCHECK (VIII)' +.ti 0 +NAME dcheck -- directory consistency check +.sp +.ti 0 +SYNOPSIS dcheck______ [ -l__ ] [ device ] +.sp +.ti 0 +DESCRIPTION dcheck______ +builds an image of the directory hierarchy +of the specified device +by reading all its directories (using physical I/O +guided by the i-nodes on the device). +A list entry is made for +each file encountered. +A second pass reads the i-nodes and for +each file compares the number of links +specified in its i-node +with the number of entries actually seen. +All discrepancies are noted. +.sp +If no device is specified, +a default device is assumed. +.sp +The argument -l__ causes a complete +listing of the file names on the device +in i-node order. +.sp +.ti 0 +FILES /dev/rk? +.sp +.ti 0 +SEE ALSO check(VIII) +.sp +.ti 0 +DIAGNOSTICS inconsistent i-numbers, +unnamed files, +unreachable files, +loops in directory "hierarchy". +.sp +.ti 0 +BUGS Unreachable files and loops are +discovered only under the "-l" option. diff --git a/static/v10/man8/delivermail.8 b/static/v10/man8/delivermail.8 new file mode 100644 index 00000000..5c1070b4 --- /dev/null +++ b/static/v10/man8/delivermail.8 @@ -0,0 +1,248 @@ +.TH DELIVERMAIL 8 +.UC 4 +.SH NAME +delivermail \- deliver mail to arbitrary people +.SH SYNOPSIS +.B /etc/delivermail +[ +.BR \- [ fr ] +.I address +] [ +.B \-a +] [ +.BI \-e x +] [ +.B \-n +] [ +.B \-m +] [ +.B \-s +] [ +.B \-i +] [ +.B \-h +.I N +] address ... +.SH DESCRIPTION +.I Delivermail +delivers a letter to one or more people, +routing the letter over whatever networks +are necessary. +.I Delivermail +will do inter-net forwarding as necessary +to deliver the mail to the correct place. +.PP +.I Delivermail +is not intended as a user interface routine; +it is expected that other programs will provide user-friendly +front ends, +and +.I delivermail +will be used only to deliver pre-formatted messages. +.PP +.I Delivermail +reads its standard input +up to a control-D +or a line with a single dot +and sends a copy of the letter found there +to all of the addresses listed. +If the +.B \-i +flag is given, +single dots are ignored. +It determines the network to use +based on the syntax of the addresses. +Addresses containing the character `@' +or the word \*(lqat\*(rq +are sent to the +.SM ARPANET; +addresses containing `!' +are sent to the +.SM UUCP +net, +and addresses containing `:' or `.' +are sent to the Berkeley network. +Other addresses are assumed to be local. +.PP +Local addresses are looked up in a file +constructed by +.IR newaliases (1) +from the data file +.I /usr/lib/aliases +and aliased appropriately. +Aliasing can be prevented by preceding the address +with a backslash or using the +.B \-n +flag. +Normally the sender is not included in any alias +expansions, e.g., +if `john' sends to `group', +and `group' includes `john' in the expansion, +then the letter will not be delivered to `john'. +The +.B \-m +flag disables this suppression. +.PP +.I Delivermail +computes the person sending the mail +by looking at your login name. +The \*(lqfrom\*(rq person +can be explicitly specified by using the +.B \-f +flag; +or, if the +.B \-a +flag is given, +delivermail looks in the body of the message +for a \*(lqFrom:\*(rq or \*(lqSender:\*(rq +field in +.SM ARPANET +format. +The +.B \-f +and +.B \-a +flags can be used +only by the special users +.I root +and +.I network, +or if the person you are trying to become +is the same as the person you are. +The +.B \-r +flag is entirely equivalent to the +.B \-f +flag; it is provided for ease of interface only. +.PP +The +.BI \-e x +flag controls the disposition of error output, +as follows: +.TP 3n +.B e +Print errors on the standard output, +and echo a copy of the message when done. +It is assumed that a network server will +return the message back to the user. +.TP +.B m +Mail errors back to the user. +.TP +.B p +Print errors on the standard output. +.TP +.B q +Throw errors away; +only exit status is returned. +.TP +.B w +Write errors back to the user's terminal, +but only if the user is still logged in +and write permission is enabled; +otherwise errors are mailed back. +.LP +If the error is not mailed back, +and if the mail originated on the machine where the error occurred, +the letter is appended to the file +.I dead.letter +in the sender's home directory. +.PP +If the first character of the user name +is a vertical bar, +the rest of the user name is used as the name of a program +to pipe the mail to. +It may be necessary to quote the name of the user +to keep +.I delivermail +from suppressing the blanks from between arguments. +.PP +The message is normally edited to eliminate \*(lqFrom\*(rq +lines that might confuse other mailers. +In particular, +\*(lqFrom\*(rq lines in the header are deleted, +and \*(lqFrom\*(rq lines in the body are prepended by `>'. +The +.B \-s +flag saves \*(lqFrom\*(rq lines in the header. +.PP +The +.B \-h +flag gives a \*(lqhop-count\*(rq, i.e., +a measure of how many times this message +has been processed by +.I delivermail +(presumably on different machines). +Each time +.I delivermail +processes a message, +it increases the hop-count by one; +if it exceeds 30 +.I delivermail +assumes that an alias loop has occurred +and it aborts the message. +The hop-count defaults to zero. +.PP +.I Delivermail +returns an exit status +describing what it did. +The codes are defined in <sysexits.h> +.ta 3n +\w'EX_UNAVAILABLE'u+3n +.de XX +.ti \n(.iu +.. +.in +\w'EX_UNAVAILABLE'u+6n +.XX + EX_OK Successful completion on all addresses. +.XX + EX_NOUSER User name not recognized. +.XX + EX_UNAVAILABLE Catchall meaning necessary resources +were not available. +.XX + EX_SYNTAX Syntax error in address. +.XX + EX_SOFTWARE Internal software error, +including bad arguments. +.XX + EX_OSERR Temporary operating system error, +such as \*(lqcannot fork\*(rq. +.XX + EX_NOHOST Host name not recognized. +.SH FILES +.if t .ta 2i +.if n .ta 3i +/usr/lib/aliases raw data for alias names +.br +/usr/lib/aliases.dir data base of alias names +.br +/usr/lib/aliases.pag +.br +/bin/mail to deliver uucp mail +.br +/usr/net/bin/v6mail to deliver local mail +.br +/usr/net/bin/sendmail to deliver Berknet mail +.br +/usr/lib/mailers/arpa to deliver ARPANET mail +.br +/tmp/mail* temp file +.br +/tmp/xscript* saved transcript +.SH SEE\ ALSO +biff(1), binmail(1), mail(1), newaliases(1), aliases(5) +.SH BUGS +.I Delivermail +sends one copy of the letter +to each user; +it should send one copy +of the letter to each host +and distribute to multiple users there +whenever possible. +.PP +.I Delivermail +assumes the addresses can be represented as one word. +This is incorrect according to the +.SM ARPANET +mail protocol RFC 733 (NIC 41952), +but is consistent with the real world. diff --git a/static/v10/man8/df.8 b/static/v10/man8/df.8 new file mode 100644 index 00000000..49713d39 --- /dev/null +++ b/static/v10/man8/df.8 @@ -0,0 +1,21 @@ +.th DF VIII 1/20/73 +.sh NAME +df \*- disk free +.sh SYNOPSIS +.bd df +[ filesystem ] +.sh DESCRIPTION +.it Df +prints out the number of free blocks +available on a file system. +If the file system is unspecified, +the free space on all of +the normally mounted file systems +is printed. +.sh FILES +/dev/rf?, +/dev/rk?, +/dev/rp? +.sh "SEE ALSO" +check(VIII) +.sh BUGS diff --git a/static/v10/man8/dist.8 b/static/v10/man8/dist.8 new file mode 100644 index 00000000..37f65622 --- /dev/null +++ b/static/v10/man8/dist.8 @@ -0,0 +1,146 @@ +.TH DIST 8 +.ds ld /usr/lib/dist +.SH NAME +connect, dispatch \(mi generic network client and server +.PP +query, receive, notify \(mi network clients +.PP +answer, transmit, notified \(mi network servers +.SH SYNOPSIS +.B \*(ld/connect +.I remote-system remote-cmd io local-cmd local-args +.PP +.B \*(ld/query +.PP +.B \*(ld/receive +.I package-id +.PP +.B \*(ld/notify +.I package-id +.PP +.B \*(ld/dispatch +.I remote-system remote-user +.PP +.B \*(ld/answer +.I remote-system remote-user +.PP +.B \*(ld/transmit +.I remote-system remote-user +.PP +.B \*(ld/notified +.I remote-system remote-user +.SH DESCRIPTION +These programs act behind the scenes on behalf of +.IR dist (1). +.I Connect +and +.I dispatch +deal with all the details of establishing and authenticating connections +on the network. The remaining programs are independent of the underlying +network. +.PP +.I Connect +encapsulates all the details of making a call on the underlying network. +Its arguments are mostly self explanatory. +.I Remote-cmd +must be one of +.BR answer ", " transmit ", or " notified "." +If +.I io +is +.BR i , +the standard input of the local command is connected +to the standard output of the remote command. If +.B i +is not specified, the local command inherits its local +standard input, and the remote command has its standard +output directed to a log file. +Similarly, +.B o +means the standard output of the local command is connected +to the standard input of the remote command. If +.B o +is not specified, the local command inherits its local +standard output, and the remote command has its standard +input attached to +.BR /dev/null . +Legal possibilities are +.BR i , +.BR o , +and +.BR io. +.PP +.I Dispatch +is intended to be called by a generic network daemon +such as +.IR svcmgr (8). +It talks to +.I connect +and takes care of establishing the appropriate standard input and +output before calling +.IR answer , +.IR transmit , +or +.IR notified . +.I Dispatch +expects arguments giving the remote system, remote user, and remote +address, and passes these to whatever program it calls. +.PP +.I Query +is a simple program called by +.I connect +with its standard input attached to the remote +.IR answer . +.I Query +displays a formatted version of the queue list from the remote machine. +(It may even turn out to be the same as +.BR /bin/cat .) +.PP +.I Receive +is a more complicated program that is called by +.I connect +with both its input and output attached to the remote +.IR transmit . +.I Receive +performs actual software installation and sends a transcript of any +errors back to the remote system. +.PP +.I Notify +is a simple program called by +.I connect +with its standard output attached to the remote +.IR notified . +.I Notify +sends an announcement of the availability of some specific package. +.PP +All of the servers read a configuration file, +.BR \*(ld/conf , +to determine how to handle installation on behalf +of a given remote system and user. The file consists of lines +containing patterns and actions. Empty lines or lines beginning +with a '\c +.BR "#" "'" +are ignored. The first three fields (separated by white space) +of each line are regular +expressions to be matched the remote system name, remote user name, +and file name respectively. The first line in which all three match +will be chosen. +The remainder of the line contains +the associated actions. +Each action is an alphanumeric name, optionally followed immediately +by a parenthesized argument. +.PP +Someday the actions will be enumerated here, but I don't know what +they are yet. +.SH EXAMPLES +A simple configuration file: +.EX +.ta \w'00000000'u +\w'00000000'u +\w'00000000'u +\w'00000000'u +\w'00000000'u +\w'00000000'u +# system user pathname action +# we are willing to distribute stuff to coma and pyxis. +(coma|pyxis) .* .* accept(yes) +\&.* .* .* accept(no) +.EE +.SH "SEE ALSO" +.IR dist (1), +.IR dist (5) diff --git a/static/v10/man8/dkmgr.8 b/static/v10/man8/dkmgr.8 new file mode 100644 index 00000000..168f6640 --- /dev/null +++ b/static/v10/man8/dkmgr.8 @@ -0,0 +1,165 @@ +.TH DKMGR 8 +.CT 1 sa_auto +.SH NAME +dkhup, dkmgr, dkzap \- manage Datakit interface +.SH SYNOPSIS +.B /usr/ipc/mgrs/dkhup +[ +.B -N +.I prefix +] +.br +.B /usr/ipc/mgrs/dkmgr +[ +.B -N +.I prefix +] [ +.B -m +.I outname +] [ +.B -n +.I service +] +.br +.B /usr/ipc/mgrs/dkzap +[ +.B -N +.I prefix +] +.SH DESCRIPTION +.I Dkhup +starts the common signaling channel protocol +for a Datakit interface. +Initially it sends several reset messages, +and tells the controller +to hang up all outstanding calls; +thereafter it simply keeps the signaling protocol running. +.PP +.I Dkmgr +receives and places Datakit calls. +Outbound calls may be placed by calling +.I ipcopen +.RI ( ipc (3)) +with the +.I outname +specified by option +.BR -m ; +the default is +.BR dk . +.I Dkmgr +announces itself to the Datakit network +with the +.I service +name specified by option +.BR -n ; +the default is taken from +.FR /etc/whoami . +Inbound calls to +.I service +are connected to the local +.L login +service; +inbound calls to +Datakit address +.IB service . serv +are handed to local service +.IR serv . +.PP +.I Dkhup +and +.I dkmgr +are normally run once from +.IR rc (8). +Both programs must be running +to make the network available. +.PP +.I Dkzap +arranges for a KMC11-assisted Datakit interface +to be reset, reloaded, and restarted. +This should be done only if things are badly broken, +as it hangs up all existing calls through that interface. +.PP +Datakit devices are expected to have names of the form +.BI /dev/dk/dk nn +with +.I nn +a two-digit channel number. +If there are more than 100 channels, +the first digit overflows to lower-case letters: +channel 100 is +.LR a0 . +The common signaling control channel +is named +.BR /dev/dk/dkctl . +All three programs accept an option +.B -N +.I prefix +to change the naming convention; +for example, +.B -N /dev/kb/kb +means that the files have names like +.B /dev/kb/kb32 +and +.BR /dev/kb/kbctl . +.PP +Support also exists for a less general naming convention: +there may be two sets of files, +named +.BI /dev/dk/dk0 nn +and +.BI /dev/dk/dk2 nn\c +, +with control channels +.B /dev/dk/dkctl0 +and +.BR /dev/dk/dkctl2 . +.I Dkhup +and +.I dkzap +take the extra argument +.B 0 +or +.B 2 +to point at one or the other of the control names. +A separate copy of +.I dkhup +is needed for each name. +.I Dkmgr +takes an option +.B -u +.IR c , +where +.I c +is +.B 0 +or +.B 2 +to use one set of files, +or +.B b +to use both simultaneously; +in the latter case, +.I service +is announced to both networks. +This scheme is obsolete and overdue for replacement; +the missing piece is something to pick an interface for outcalls. +.PP +.I Dkmgr +records its activity in file +.I service +in directory +.BR /usr/ipc/log , +default +.BR /usr/ipc/log/dk . +.SH FILES +.F /dev/dk +.SH "SEE ALSO" +.IR con (1), +.IR kmc (8), +.IR svcmgr (8), +.IR ipc (3) +.SH BUGS +.I Dkhup +should be folded into +.IR dkmgr ; +it is separate for historic reasons. diff --git a/static/v10/man8/dli.8 b/static/v10/man8/dli.8 new file mode 100644 index 00000000..b63e9af0 --- /dev/null +++ b/static/v10/man8/dli.8 @@ -0,0 +1,27 @@ +.pa 1 +.he 'DLI (VIII)'3/15/72'DLI (VIII)' +.ti 0 +NAME dli -- load DEC binary paper tapes +.sp +.ti 0 +SYNOPSIS dli output [input] +.sp +.ti 0 +DESCRIPTION dli___ +will load a DEC binary paper tape +into the output file. +The binary format paper tape +is read from the input file +(/dev/ppt is default.) +.sp +.ti 0 +FILES /dev/ppt +.sp +.ti 0 +SEE ALSO -- +.sp +.ti 0 +DIAGNOSTICS "checksum" +.sp +.ti 0 +BUGS -- diff --git a/static/v10/man8/dmesg.8 b/static/v10/man8/dmesg.8 new file mode 100644 index 00000000..162b84fd --- /dev/null +++ b/static/v10/man8/dmesg.8 @@ -0,0 +1,64 @@ +.TH DMESG 8 +.CT 1 sa_nonmortals +.SH NAME +dmesg \- system diagnostic messages +.SH SYNOPSIS +.B /etc/dmesg +[ +.B - +] +[ +.B -i +] +[ +.I core namelist +] +.SH DESCRIPTION +.I Dmesg +looks in a system buffer +for recent console messages from the operating system +and reproduces them on the standard output. +Under option +.LR - , +.I dmesg +produces only those messages printed by the system +since the last time +.L dmesg\ - +was run. +It is normally run periodically by +.IR cron (8) +to produce the error log +.FR /usr/adm/messages . +.PP +Option +.B -i +prints messages produced since the last +.L dmesg\ - +without changing any records. +.PP +If +.I core +and +.I namelist +are specified, +they are used in place of +.F /dev/kmem +and +.FR /unix . +.SH FILES +.TF /usr/adm/messages +.TP +.F /usr/adm/messages +error log +.br +.TP +.F /usr/adm/msgbuf +record of option +.L - +.SH BUGS +Since the system error message buffer is small, +not all error messages +are guaranteed to be logged. +.br +Error messages generated immediately before a system crash +may not be logged. diff --git a/static/v10/man8/downgrade.8 b/static/v10/man8/downgrade.8 new file mode 100644 index 00000000..9ab11d51 --- /dev/null +++ b/static/v10/man8/downgrade.8 @@ -0,0 +1,37 @@ +.TH DOWNGRADE 8 +.CT 8 sa_nonmortals +.SH NAME +downgrade \- downgrade a file +.SH SYNOPSIS +.B /etc/downgrade +.I label +.I file ... +.SH DESCRIPTION +.I Downgrade +clears from the label of each +.I file +all bits that correspond to one bits in +.I label. +Capabilities or licenses specified in +.I label +are ignored. +The +.I files +must be readable and must be specified by full path name. +.LP +.I Downgrade +requires +.B T_EXTERN +privilege, which may be granted to authorized users by +.IR priv (8). +.SH EXAMPLES +.L +priv downgrade 0110 /usr/myproject/*.c +.SH FILES +.F /dev/log +.SH "SEE ALSO" +.IR getlab (2), +.IR setlab (1) +.SH BUGS +Downgrading is not an atomic operation. If a file is +relinked underfoot misleading logging records may result. diff --git a/static/v10/man8/dump.8 b/static/v10/man8/dump.8 new file mode 100644 index 00000000..51a70ec8 --- /dev/null +++ b/static/v10/man8/dump.8 @@ -0,0 +1,94 @@ +.th DUMP VIII 11/24/73 +.sh NAME +dump \*- incremental file system dump +.sh SYNOPSIS +.bd dump +[ key [ arguments ] filesystem ] +.sh DESCRIPTION +.it Dump +will make an incremental file system dump +on magtape +of all files changed after a certain date. +The argument +.it key, +specifies the date and other options about the dump. +.it Key +consists of characters from +the set +.bd iu0hds. +.s3 +.lp +5 3 +\fBi\fR the +dump date is taken from the file +.bd /etc/ddate. +.s3 +.lp +5 3 +\fBu\fR the date just prior to this dump +is written on +.bd /etc/ddate +upon successful completion of this dump. +.s3 +.lp +5 3 +\fB0\fR the dump date is taken as the epoch +(beginning of time). +Thus this option causes an entire file system dump to be taken. +.s3 +.lp +5 3 +\fBh\fR the dump date is some number of hours before the current date. +The number of hours is taken from the next argument in +.it arguments. +.s3 +.lp +5 3 +\fBd\fR the dump date is some number of days before the current date. +The number of days is taken from the next argument in +.it arguments. +.s3 +.lp +5 3 +\fBs\fR the size of the dump tape is specified in feet. +The number of feet is taken from the next argument in +.it arguments. +It is assumed that there are 9 standard UNIX records per foot. +When the specified size is reached, +the dump will wait for reels to be changed. +The default size is 1700 feet. +.s3 +.i0 +If no arguments are given, +the +.it key +is assumed to be +.bd i +and the file system is +assumed to be +.bd /dev/rp1. +.s3 +Full dumps +should be taken on quiet file systems as follows: +.s3 + dump 0u /dev/rp1 +.br + check -l /dev/rp1 +.s3 +The +.it check +will come in handy in case it is necessary +to resore indiviidual files from this dump. +Incremental dumps should then be taken +when desired by: +.s3 + dump +.s3 +When the incremental dumps get cumbersome, +a new complete dump should be taken. +In this way, +a restore requires +loading of the complete dump tape and only the latest incremental tape. +.sh FILES +/dev/mt0 magtape +.br +/dev/rp1 default file system +.br +/etc/ddate +.sh "SEE ALSO" +restor, check(VIII), dump(V) +.sh BUGS diff --git a/static/v10/man8/dumpdir.8 b/static/v10/man8/dumpdir.8 new file mode 100644 index 00000000..005bd8ef --- /dev/null +++ b/static/v10/man8/dumpdir.8 @@ -0,0 +1,38 @@ +.TH DUMPDIR 8 +.UC 4 +.SH NAME +dumpdir \- print the names of files on a dump tape +.SH SYNOPSIS +.B /etc/dumpdir +[ +.B f +filename ] +.SH DESCRIPTION +.I Dumpdir +is used to read magtapes dumped with the +.I dump +command and list the names and inode numbers +of all the files and directories on the tape. +.PP +The +.B f +option causes +.I filename +as the name of the tape instead +of the default. +.SH FILES +default tape unit varies with installation +.br +rst* +.SH "SEE ALSO" +dump(1), restor(1) +.SH DIAGNOSTICS +If the dump extends over more than one tape, +it may ask you to change tapes. +Reply with a new-line when the next tape has been mounted. +.SH BUGS +There is redundant information on the tape +that could be used in case of tape reading problems. +Unfortunately, +.I dumpdir +doesn't use it. diff --git a/static/v10/man8/expire.8 b/static/v10/man8/expire.8 new file mode 100644 index 00000000..3c5a2672 --- /dev/null +++ b/static/v10/man8/expire.8 @@ -0,0 +1,67 @@ +.TH EXPIRE 8 +.SH NAME +expire \- remove outdated news articles +.SH SYNOPSIS +.BR /usr/lib/news/expire " [ " \-n +.IR newsgroups " ] [ " +.BR \-i " ] [ " \-I " ] [ " \-v " [ " +.IR level " ] ] [ " +.BI \-e days + ] + [ +.B \-a + ] +.SH DESCRIPTION +.PP +.I Expire +is normally started up by +.IR cron (8) +every night to remove all expired news. +If no newsgroups are specified, the default is to expire +.BR all . +.PP +Articles whose specified expiration date has already passed +are considered expirable. +The +.B \-a +option causes expire to archive articles in /usr/spool/oldnews. +Otherwise, the articles are unlinked. +.PP +The +.B \-v +option causes expire to be more verbose. +It can be given a verbosity level (default 1) as in +.B \-v3 +for even more output. +This is useful if articles aren't being expired and you want to know why. +.PP +The +.B \-e +flag gives the number of days to use for a default expiration date. +If not given, an installation dependent default (often 2 weeks) is used. +.PP +The +.B \-i +and +.B \-I +flags +tell +.B expire +to ignore any expiration date explicitly given on articles. +This can be used when disk space is really tight. +The +.B \-I +flag will always ignore expiration dates, +while the +.B \-i +flag will only ignore the date if ignoring it would expire the article sooner. +.I WARNING: +If you have articles archived by giving them expiration dates far into the +future, these options might remove these files anyway. +.SH "SEE ALSO" +checknews(1), +inews(1), +readnews(1), +recnews(8), +sendnews(8), +uurec(8) diff --git a/static/v10/man8/fsck.8 b/static/v10/man8/fsck.8 new file mode 100644 index 00000000..2f6841c5 --- /dev/null +++ b/static/v10/man8/fsck.8 @@ -0,0 +1,248 @@ +.TH FSCK 8 +.CT 1 sa_nonmortals +.SH NAME +fsck \- file system consistency check and interactive repair +.SH SYNOPSIS +.B /etc/fsck +.B -p +[ +.I special ... +] +.br +.B /etc/fsck +[ +.B -y +] +[ +.B -n +] +[ +.BI -s X +] +[ +.BI -S X +] +[ +.B -t +.I filename +] [ +.I special ... +] +.SH DESCRIPTION +.I Fsck +inspects the disk filesystems +in the named +.I special +files +and repairs inconsistencies. +If no files are named, +every file system listed in +.IR fstab (5) +with type 0 +and a nonzero pass number +is checked. +.PP +Under option +.BR -p , +.I fsck +runs without intervention, +repairing minor inconsistencies +and aborting on major ones. +This form is usually called from +.IR rc (8). +If no special files are named, +file systems in +.I fstab +are checked in parallel passes: +all file systems with pass number 1 +are checked simultaneously, +then all file systems with pass number 2, +and so on until +.I fstab +is exhausted. +.PP +Here are the minor ailments +repaired automatically +under +.BR -p : +.RS +unreferenced inodes; +.br +wrong link counts in inodes; +.br +missing blocks in the free list; +.br +blocks in the free list also in files; and +.br +counts wrong in the super-block. +.RE +.PP +Other inconsistencies +cause +.I fsck +to abandon the inconsistent file system, +and exit with a nonzero status +when the current pass finishes. +.PP +Without the +.B -p +option, +.I fsck +inspects one file system at a time, +interactively. +Each inconsistency causes +.I fsck +to print a message +and ask permission to fix the problem. +The operator may require arcane knowledge +to guide +.I fsck +safely through repair of a badly damaged file system. +.PP +Here are the remaining options. +They are allowed only if +.B -p +is absent. +.TP +.B -y +Assume a yes response to all questions. +This should be used with great caution. +.TP +.B -n +Assume a no response to all questions; +do not open the file system for writing. +This option is assumed if the file system cannot be opened for writing. +.TP +.BI -s X +Ignore the actual free list and (unconditionally) reconstruct a new +one by rewriting the super-block of the file system. +The file system should be unmounted while this is done; if this +is not possible, care should be taken that the system is quiescent +and that it is rebooted immediately afterwards. +This precaution is necessary so that the old, bad, in-core copy +of the superblock will not continue to be used, or written on the file system. +If the file system has a bitmap free list (see +.IR filsys (5)), +the free list is always reconstructed unless the +.B -n +option is enabled. +.IP +Parameter +.I X +allows free-list parameters to be specified: +.BI -s blocks-per-cylinder : blocks-to-skip\c +\&. +If +.I X +is not given, +the values used when the file system was created +are used; see +.IR mkfs (8). +If these values were not specified, +.I X +is assumed to be +.BR 400:9 . +.TP +.BI -S X +Conditionally reconstruct the free list. +This option +is like +.BI -s X +except that the free list is rebuilt only +if no discrepancies were found. +.B -S +implies +.BR -n . +.TP +.B -t +If +.I fsck +cannot obtain enough memory to keep its tables, +it uses a scratch file. +If the +.B -t +option is +specified, the file named in the next argument +is used as the scratch file, if needed. +Without +.BR -t , +.I fsck +will prompt the operator for the name of the +scratch file. +The file chosen should not be on the +file system being checked. +If it did not already exist, +it is removed when +.I fsck +completes. +.PD +.br +.ne 6 +.PP +Inconsistencies checked are: +.IP +.nf +Blocks claimed more than once. +Blocks designated outside the file system. +Incorrect link counts. +Directory size not 16-byte aligned. +Bad inode format. +Blocks not accounted for anywhere. +Directory entry pointing to unallocated inode. +Inode number out of range. +More than 65536 inodes. +More blocks for inodes than there are in the file system. +Bad free block list format. +Total free block and/or free inode count incorrect. +.fi +.PP +Orphaned files and directories (allocated but unreferenced) are +reconnected by +placing them in the directory +.F lost+found +in the root of the file system being checked. +The name assigned is the inode number, +prefixed by +.LR # . +.PP +Checking the raw device is almost always faster, +but +.I fsck +distinguishes bitmapped from non-bitmapped file systems +by examining the minor device number, +so the block device is safer. +.SH FILES +.F /etc/fstab +.SH "SEE ALSO" +.IR fstab (5), +.IR filsys (5), +.IR mkfs (8), +.IR reboot (8) +.br +T. J. Kowalski, +`Fsck\(emthe +.SM UNIX +File System Check Program', +this manual, Volume 2 +.SH BUGS +Inode numbers for +.B . +and +.B .. +in each directory should be checked for validity. +.PP +Some systems save core images after a crash +in the swap area; +on such machines, +checking many large file systems in parallel +may cause swapping, overwriting the crash dump. +It is best just to write crash dumps in a a safer place. +If disk space for dumps and swapping is scarce, +avoid checking more than three 120-megabyte file systems +in parallel on a machine with four megabytes of physical memory. +.PP +Examining the minor device number is a botch; +there should be an explicit flag somewhere. +.PP +.I Fsck +does not have supernatural powers. diff --git a/static/v10/man8/fstat.8 b/static/v10/man8/fstat.8 new file mode 100644 index 00000000..7abf677b --- /dev/null +++ b/static/v10/man8/fstat.8 @@ -0,0 +1,49 @@ +.TH FSTAT 1 +.SH NAME +fstat \- file status +.SH SYNOPSIS +.B /etc/fstat +[ +.B \-u +user ] [ +.B \-p +pid ] [ +.B \-f +filename ] +.SH DESCRIPTION +.I Fstat +identifies open files. +A file is considered open if a process has it open, +if it is the working directory for a process, +or if it is an active pure text file. +Under default options, +.I fstat +reports on all open files. +.PP +Options: +.TP 6 +.B \-u +Report all files open by a specified user. +.TP 6 +.B \-p +Report all files open by a specified process id. +.TP 6 +.B \-f +Restrict reports to the specified file. +If the file is a character special file, +.I fstat +additionally reports on any open files on that device, +treating it as a mounted file system. +.dt +.SH "SEE ALSO" +ps(1), pstat(8) +.SH DIAGNOSTICS +Yet to be determined. +.SH BUGS +.I Fstat +tries to be clever if you elide the +.B \-u , +.B \-f , +or +.B \-p +flags for the argument. Like any expert system, it is sometimes wrong. diff --git a/static/v10/man8/gacct.8 b/static/v10/man8/gacct.8 new file mode 100644 index 00000000..bc72d1a3 --- /dev/null +++ b/static/v10/man8/gacct.8 @@ -0,0 +1,22 @@ +.pa 1 +.he 'GACCT (VIII)'4/27/73'GACCT (VIII)' +.ti 0 +NAME gacct -- command accounting statistics +.sp +.ti 0 +SYNOPSIS gacct [ -arnl ] [ files ] +.sp +.ti 0 +DESCRIPTION X +.sp +.ti 0 +FILES /usr/adm/tacct +.sp +.ti 0 +SEE ALSO sh(i) +.sp +.ti 0 +DIAGNOSTICS -- +.sp +.ti 0 +BUGS -- diff --git a/static/v10/man8/gettable.8 b/static/v10/man8/gettable.8 new file mode 100644 index 00000000..32ed9d57 --- /dev/null +++ b/static/v10/man8/gettable.8 @@ -0,0 +1,65 @@ +.\" Copyright (c) 1983 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms are permitted +.\" provided that the above copyright notice and this paragraph are +.\" duplicated in all such forms and that any documentation, +.\" advertising materials, and other materials related to such +.\" distribution and use acknowledge that the software was developed +.\" by the University of California, Berkeley. The name of the +.\" University may not be used to endorse or promote products derived +.\" from this software without specific prior written permission. +.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED +.\" WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. +.\" +.\" @(#)gettable.8 6.3 (Berkeley) 9/20/88 +.\" +.TH GETTABLE 8 "September 20, 1988" +.UC 5 +.SH NAME +gettable \- get NIC format host tables from a host +.SH SYNOPSIS +.B /etc/gettable +[ +.B \-v +] +.I host +[ outfile ] +.SH DESCRIPTION +.I Gettable +is a simple program used to obtain the NIC standard +host tables from a ``nicname'' server. The indicated +.I host +is queried for the tables. The tables, if retrieved, +are placed in the file +.I outfile +or by default, +.IR hosts.txt . +.PP +The +.B \-v +option will get just the version number instead of the complete host table +and put the output in the file +.I outfile +or by default, +.IR hosts.ver . +.PP +.I Gettable +operates by opening a TCP connection to the port indicated +in the service specification for ``nicname''. A request +is then made for ``ALL'' names and the resultant information +is placed in the output file. +.PP +.I Gettable +is best used in conjunction with the +.IR htable (8) +program which converts the NIC standard file format to +that used by the network library lookup routines. +.SH "SEE ALSO" +intro(3), htable(8), named(8) +.SH BUGS +If the name-domain system provided network name mapping well as host +name mapping, +.I gettable +would no longer be needed. diff --git a/static/v10/man8/getty.8 b/static/v10/man8/getty.8 new file mode 100644 index 00000000..41c7cf37 --- /dev/null +++ b/static/v10/man8/getty.8 @@ -0,0 +1,88 @@ +.TH GETTY 8 +.CT 1 sa_auto secur +.SH NAME +getty \- set terminal mode +.SH SYNOPSIS +.B /etc/getty +[ +.I char +] +.SH DESCRIPTION +.I Getty +is invoked by +.IR init (8) +after a terminal is opened. +While reading the user's name +.I getty +attempts to adapt the system to the speed and type of terminal +being used. +.PP +.I Init +calls +.I getty +with an argument specified by the +.IR ttys (5) +entry for the terminal line. +The argument +.I char +determines the line speed +and other characteristics; +see below. +.I Getty +then types a banner identifying the system (from +.FR /etc/whoami ) +and the +.L login: +message. +The user's name is then read, a character at a time. +If a null character is received, it is assumed to be the result +of the user pushing the `break' (`interrupt') key. +The speed is then +changed to another baud rate and +.L login: +is typed again. +Successive breaks cycle through a set of speeds. +.PP +The user's name is terminated by a newline or +carriage return. +The latter results in the system being set to +treat carriage returns appropriately (see +.IR ioctl (2)). +.PP +Finally, +.IR login (8) +is called with the user's name as argument. +.PP +Here are the possible values for +.IR char . +If more than one speed is given, +the first speed is used initially; +others are selected by successive depressions of the +BREAK key. +Other things, +like delays and tab expansion, +are set in various ways as well. +.PP +.de fq +\f5\\$1 \fR\\$2 \\$3 \\$4 \\$5 \\$6 +.. +.nf +char speed +.fq 0 300-1200-150-110 +.fq 2 9600 +.fq 3 1200-300 +.fq 4 300 +.fq 5 300-1200 +.fq 6 2400 +.fq 7 4800 +.fq 8 9600-1200-300 +.fq 9 300-9600-1200 +.fq a 2400-1200 +.fq b 1200-2400 +.fq j exta (usually 19200) +.fi +.SH "SEE ALSO" +.IR init (8), +.IR login (8), +.IR ioctl (2), +.IR ttys (5) diff --git a/static/v10/man8/halt.8 b/static/v10/man8/halt.8 new file mode 100644 index 00000000..cd4de601 --- /dev/null +++ b/static/v10/man8/halt.8 @@ -0,0 +1,21 @@ +.TH HALT 8 +.UC 4 +.SH NAME +halt \- halt the processor +.SH SYNOPSIS +.B /etc/halt +[ +.B \-n +] +.SH DESCRIPTION +.I Halt +writes out sandbagged information to the disks and then halts +the processor. The machine does not reboot, even if the auto-reboot +switch is set on the console. +.PP +The +.B \-n +option prevent the sync before the reboot. +.SH SEE ALSO +reboot(8) +.SH BUGS diff --git a/static/v10/man8/htable.8 b/static/v10/man8/htable.8 new file mode 100644 index 00000000..f98c9b05 --- /dev/null +++ b/static/v10/man8/htable.8 @@ -0,0 +1,116 @@ +.\" Copyright (c) 1983 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms are permitted +.\" provided that the above copyright notice and this paragraph are +.\" duplicated in all such forms and that any documentation, +.\" advertising materials, and other materials related to such +.\" distribution and use acknowledge that the software was developed +.\" by the University of California, Berkeley. The name of the +.\" University may not be used to endorse or promote products derived +.\" from this software without specific prior written permission. +.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED +.\" WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. +.\" +.\" @(#)htable.8 6.4 (Berkeley) 9/20/88 +.\" +.TH HTABLE 8 "September 20, 1988" +.UC 5 +.SH NAME +htable \- convert NIC standard format host tables +.SH SYNOPSIS +.B /etc/htable +[ +.B \-c +.I connected-nets +] [ +.B \-l +.I local-nets +] +.I file +.SH DESCRIPTION +.I Htable +is used to convert host files in the format specified +in Internet RFC 810 to the format used by the network +library routines. Three files are created as a result +of running +.IR htable : +.IR hosts , +.IR networks , +and +.IR gateways . +The +.I hosts +file may be used by the +.IR gethostbyname (3N) +routines in mapping host names to addresses +if the nameserver, +.IR named (8), +is not used. +The +.I networks +file is used by the +.IR getnetent (3N) +routines in mapping network names to numbers. +The +.I gateways +file may be used by the routing daemon +in identifying ``passive'' Internet gateways; +see +.IR routed (8C) +for an explanation. +.PP +If any of the files +.IR localhosts , +.IR localnetworks , +or +.I localgateways +are present in the current directory, +the file's contents is prepended to the +output file. +Of these, only the gateways file is interpreted. +This allows sites to maintain local aliases and +entries which are not normally present in the +master database. +Only one gateway to each network will be placed in the gateways file; +a gateway listed in the localgateways file will override any in the +input file. +.PP +If the gateways file is to be used, +a list of networks to which the host is directly connected +is specified with the +.B \-c +flag. +The networks, separated by commas, +may be given by name or in Internet-standard dot notation, +e.g. +.B \-c +arpanet,128.32,local-ether-net. +.I Htable +only includes gateways +which are directly connected to one of the networks specified, +or which can be reached from another gateway on a connected net. +.PP +If the +.B \-l +option is given with a list of networks (in the same format as for +.BR \-c ), +these networks will be treated as ``local,'' +and information about hosts on local networks is +taken only from the localhosts file. +Entries for local hosts from the main database will be omitted. +This allows the localhosts file to completely override +any entries in the input file. +.PP +.I Htable +is best used in conjunction with the +.IR gettable (8) +program which retrieves the NIC database from a host. +.SH "SEE ALSO" +netintro(4), gettable(8), named(8) +.SH BUGS +If the name-domain system provided network name mapping well as host +name mapping, +.I htable +would no longer be needed. diff --git a/static/v10/man8/icheck.8 b/static/v10/man8/icheck.8 new file mode 100644 index 00000000..b4ae5804 --- /dev/null +++ b/static/v10/man8/icheck.8 @@ -0,0 +1,182 @@ +.TH ICHECK 8 +.CT 1 sa_nonmortals +.SH NAME +icheck, dcheck, ncheck \- file system consistency check +.SH SYNOPSIS +.B /etc/icheck +[ +option ... ] +.I filesystem ... +.PP +.B /etc/dcheck +[ +option ... ] +.I filesystem ... +.PP +.B /etc/ncheck +[ +option ... ] +.I filesystem ... +.SH DESCRIPTION +These programs perform +consistency checks on file systems. +For normal file system maintenance, see +.IR fsck (8). +Common options are +.TP +.B -B +The file system is bitmapped. +If +.I filesystem +is a special file, this option is set automatically from +the minor device number. +.TP +.BI -i " number ... +Report only on specified inode +.I numbers +.RI ( dcheck +and +.I ncheck +only). +.PP +.I Icheck +examines each +.I filesystem, +builds a list of used blocks, +and compares this list against +the free list maintained on the file system. +The normal output of +.I icheck +includes a report of +.IP "" +The total number of files and the numbers of +regular, directory, block special and character special files. +.IP "" +The total number of blocks in use and the numbers of +single-, double-, and triple-indirect blocks and directory blocks. +.IP "" +The number of free blocks. +.IP "" +The number of blocks missing; +.I i.e.\& +not in any file +nor in the free list. +.PP +Other +.I icheck +options are +.TP +.B -s +Ignore the free list and reconstruct a new one +by rewriting the super-block of the file system. +The file system should be dismounted while this is done; +if this is not possible (for example if +the root file system has to be salvaged) +care should be taken that the system is quiescent. +The words in the super-block +which indicate the size of the free list and of the +i-list are believed. +If the super-block has been curdled +these words will have to be patched. +The normal output reports are suppressed. +.TP +.BI -b " number ... +Report each appearance of the selected block +.I numbers +in a file or on the free list. +.TP +.B -d +Report each duplicate block. +.TP +.B -m +Report each missing block. +.TP +.B -e +Print at most one diagnostic per file; +useful for badly curdled file systems. +.PP +.I Dcheck +reads the directories in each +.I filesystem +and compares +the link count in each inode with the number of directory +entries by which it is referenced. +.PP +.I Ncheck +generates a list of pathname vs i-number for each named +.I filesystem. +Other +.I ncheck +options are +.TP +.B -a +Report +.L . +and +.LR .. , +which are normally ignored. +.TP +.B -s +Report only special files, and files with +set-userid or set-groupid mode; +helpful in finding security breaches. +.SH "SEE ALSO" +.IR filsys (5), +.IR chuck (8), +.IR fsck (8), +.IR clri (8) +.SH DIAGNOSTICS +For duplicate blocks +and bad blocks (which lie outside the file system) +.I icheck +announces the difficulty, the i-number, and the kind of block involved. +If a read error is encountered, +the block number of the bad block is printed and +.I icheck +considers it to contain 0. +`Bad freeblock' means that +a block number outside the available space was encountered in the free list. +`Dups in free' +means that +blocks were found in the free list which +duplicate blocks either in some file or in the +earlier part of the free list. +.PP +When a file turns up for which the link-count and the number +of directory entries disagree, +.I dcheck +reports the relevant facts. +Allocated files which have 0 link-count and no entries are also +listed. +The only dangerous situation +occurs when there are more entries than links; +if entries are removed, +so the link-count drops to 0, +the remaining entries point to thin air. +They should be removed. +When there are more links than entries, or there is +an allocated file with neither links nor entries, +some disk space may be lost but the situation will not degenerate. +.PP +When the filesystem structure is improper, +.I ncheck +prints +.L ?? +to denote the `parent' of +a parentless file. +A pathname beginning with +.L ... +denotes a loop. +.SH BUGS +Extraneous diagnostics +may be produced if these commands are applied to +active file systems. +.br +They believe even preposterous super-blocks and +consequently can get core images. +.br +.I Ncheck's +report is in no useful +order, and probably should be sorted. +.I Ncheck +fails to report the root inode. diff --git a/static/v10/man8/inews.8 b/static/v10/man8/inews.8 new file mode 100644 index 00000000..561d345f --- /dev/null +++ b/static/v10/man8/inews.8 @@ -0,0 +1,93 @@ +.TH INEWS 8 +.SH NAME +inews \- submit news articles +.SH SYNOPSIS +.B inews +[ +.B \-h +] +.B \-t +title [ +.B \-n +newsgroup ... ] [ +.B \-e +expiration ] +.PP +.B inews \-p +[ file ] +.PP +.B inews \-C +newsgroup +.SH DESCRIPTION +.I Inews +submits netnews articles. +It is not intended for people; see +.IR postnews (1) +for routine use. +The first form is for submitting articles; +the second for receiving articles from other machines; +the third for creating newsgroups. +.PP +In the first form, the article is read from the standard input. +A +.I title +must be specified, one or more +.I newsgroups +(default `general') +may be specified, and a nonstandard +.I expiration +date may be specified. +Option +.B \-f +substitutes another sender's name instead of the user. +Option +.B \-h +specifies that headers are present at the beginning of the +article and should be included with the article +header instead of as text. +.PP +The sender's full name is taken from the environment variable NAME, +or from the system index (often +.IR passwd (5)). +The environment variable ORGANIZATION overrides the system default. +.PP +In the second form +.I inews +reads the article from the named +.I file. +.PP +The third form is for creating new newsgroups. +This may +be limited to specific users such as the super-user or news administrator. +.SH FILES +.PD 0 +.TP \w'/usr/spool/news/newsgroup/article_no 'u +/usr/spool/news/.sys.nnn +temporary articles +.TP +.RI /usr/spool/news/ newsgroup / article_no +articles +.TP +/usr/spool/oldnews/ +expired articles +.TP +/usr/lib/news/active +known newsgroups and highest article number in each +.TP +/usr/lib/news/seq +sequence number of last article +.TP +/usr/lib/news/history +list of all articles ever seen +.TP +/usr/lib/news/sys +system subscription list +.PD +.SH "SEE ALSO" +news(5), +newsrc(5), +postnews(1), +readnews(1), +recnews(8), +sendnews(8) +uurec(8) diff --git a/static/v10/man8/init.8 b/static/v10/man8/init.8 new file mode 100644 index 00000000..72def2a8 --- /dev/null +++ b/static/v10/man8/init.8 @@ -0,0 +1,147 @@ +.TH INIT 8 +.CT 1 sa_auto secur +.SH NAME +init \- process control initialization +.SH SYNOPSIS +.B /etc/init +.SH DESCRIPTION +.I Init +is invoked by the kernel as the last step in the boot procedure. +It is always process 1. +.PP +When started normally, +.I init +calls +.IR rc (8). +The security label is set at bottom. +If this succeeds, +.I init +begins multi-user operation. +If +.I rc +fails, +.I init +commences single user operation by executing +a superuser shell, +.IR nosh (8), +with bottom security label, top ceiling, and all privileges. +.PP +When started by a cold boot from the console, +.I init +starts single user operation immediately. +When the single user shell terminates, +.I init +runs +.IR rc +without the parameter, +and begins multi-user operation. +.PP +In multi-user operation, +.IR init 's +role is to create a process for each +directly connected terminal port on which a user may log in. +To begin such operations, it reads the +.IR ttys (5) +file and forks to create a process +for each terminal specified in the file. +Each of these processes opens the appropriate terminal +for reading and writing +on file descriptors 0, 1, 2, and 3 (the standard input and +output, the diagnostic output and +.FR /dev/tty ). +The security label of each port is set to that of file +.FR /etc/floor . +Opening the terminal will usually involve a delay, +since the +.I open +is not completed until someone +dials and carrier is established on the channel. +Then +.IR getty (8) +is called with argument as specified by the second character of +the +.I ttys +file line. +.I Getty +reads the user's name and invokes +.IR login (8) +to log in the user and execute the shell. +.PP +Ultimately the shell will terminate +because of an end-of-file or as a result of hanging up. +The main path of +.IR init , +which has been waiting +for such an event, +wakes up and removes the appropriate entry from the +file +.IR utmp (5), +which records current users, and +makes an entry in +.IR wtmp , +which maintains a history +of logins and logouts. +Then the appropriate terminal is reopened and +.I getty +is +invoked again. +.PP +.I Init +catches signal +.B SIGHUP +and interprets it to mean that +the +.I ttys +file +should be read again. +The shell process on each line that has become inactive +according to +.I ttys +is terminated; +a new process is created for each line added; +lines unchanged in the file are undisturbed. +Thus it is possible to drop or add terminal lines without +rebooting the system by changing the +.I ttys +file and sending a +.I hangup +signal to the +.I init +process: use +.LR "kill -1 1" . +.PP +.I Init +will terminate multi-user operations, +kill all outstanding processes, +and resume single-user mode +if sent signal +.BR SIGTERM : +use +.LR "kill 1" . +.I Init +will wait at most 30 seconds for outstanding processes to die, +to avoid waiting forever. +.PP +If, at bootstrap time, the +.I init +program cannot be executed, +the system will loop in user mode at a low address. +.SH FILES +.nf +.F /dev/console +.F /dev/tty +.F /etc/utmp +.F /usr/adm/wtmp +.F /etc/ttys +.F /etc/rc.nosh +.fi +.SH "SEE ALSO" +.IR login (8), +.IR kill (1), +.IR sh (1), +.IR ttys (5), +.IR getty (8), +.IR rc (8), +.IR reboot (8) +.SH BUGS +The single-user shell has all privileges. diff --git a/static/v10/man8/ino.8 b/static/v10/man8/ino.8 new file mode 100644 index 00000000..be9c35c4 --- /dev/null +++ b/static/v10/man8/ino.8 @@ -0,0 +1,10 @@ +.th INO VIII 11/1/73 +.sh NAME +ino \*- get the i-number of a file +.sh SYNOPSIS +.bd ino +file ... +.sh DESCRIPTION +The i-number of each file argument is printed. +An i-number of zero is printed if a bad argument is given. +.sh BUGS diff --git a/static/v10/man8/ins.8 b/static/v10/man8/ins.8 new file mode 100644 index 00000000..f4efaa4e --- /dev/null +++ b/static/v10/man8/ins.8 @@ -0,0 +1,103 @@ +.TH INS 8 +.SH NAME +ins \- install software +.SH USAGE +.B ins +[ +.I option ... +] +[ +[ +.I source +] +.I target +] +.SH DESCRIPTION +.I Ins +queues a request to `install' the named +.I target +file \- in the simplest case, by copying from +.I source +to +.BR target " \- +and then attempts to execute all pending requests +for the target, +until thwarted by lack of privilege. +By default, each target has a separate queue, but if several files are +to be updated together their requests can +also be placed in another separate queue. +If modification requests for a given target file appear in several +different queues, those requests will be executed in correct time +order. +A request will be served only when it is at the front of all the queues +it is in. +.PP +If no target is named, +.I ins +attempts to serve all pending requests. +The options are +.TP +.B -x +Verify consistency of currently queued-up requests +with historical record in +.F /usr/spool/ins/log. +.TP +.B -v +Print a verbose commentary +(by copying logging data to standard output). +.TP +.B -n +Print, but do not execute, the modification requests. +.TP +.BI -j " jobnumber" "... +Delete a queued-up request. +Possible values for +.I jobnumber +are revealed by using the +.B -n +flag, where they are listed in the style +.BI /usr/spool/ins/job jobnumber. +.TP +.BI -q " queuename +Put the request in special named queue, in addition to the +queue for +.I target. +.TP +.B -r +Remove target. +.TP +.BI -o " owner +Set uid of target. +.TP +.BI -g " group +Set gid of target. +.TP +.BI -m " mode +Set file mode of target, as in +.IR chmod (1). +.TP +.BI -l " label +Set file label of target, as in +.IR setlab (1). +.TP +.BI -p " cap lic +Set file privileges, as in +.IR setpriv (8). +.PP +.I Ins +records +.IR xs (8)-style +checksums of both modified software and of its own queues, +keeps a verbose log file, etc, etc. +.SH FILES +.F /usr/spool/ins/log +.br +.F /usr/spool/ins/lock +.br +.F /usr/spool/ins/pending +.br +.F /usr/spool/ins/job* +.br +.F /usr/spool/ins/dat* +.SH BUGS +Not written yet. diff --git a/static/v10/man8/install.8 b/static/v10/man8/install.8 new file mode 100644 index 00000000..966aeffa --- /dev/null +++ b/static/v10/man8/install.8 @@ -0,0 +1,34 @@ +.TH INSTALL 8 bowell +.SH NAME +install \- place files in their proper homes +.SH SYNOPSIS +.B /etc/install +[ +.B \-c +] [ \-s ] +file dest +.SH DESCRIPTION +.I Install +moves or copies the +.I file +to +.I dest. +If +.I dest +is a directory, the file is installed in the directory. +Its main use is in makefiles subsidiary to the primary source directory /src. +.PP +Option +.B \-c +causes the file to be copied, otherwise it is moved. +Option +.B \-s +invokes +.IR strip (1) +on the file first. +.PP +If possible, the group and owner of +.I dest +are changed to `bin'. +.SH BUGS +Only one option can appear. diff --git a/static/v10/man8/ipconfig.8 b/static/v10/man8/ipconfig.8 new file mode 100644 index 00000000..6fcc66c7 --- /dev/null +++ b/static/v10/man8/ipconfig.8 @@ -0,0 +1,125 @@ +.TH IPCONFIG 8 +.CT 1 sa_auto +.SH NAME +ipconfig, dkipconfig, udpconfig \- set up DARPA Internet protocols +.SH SYNOPSIS +.B /usr/ipc/mgrs/ipconfig +[ +.B -m +.I mask +] [ +.B -df +] +.I "ip-device localhost network" +.BI [ arp-device ] +.B & +.br +.B /usr/ipc/mgrs/dkipconfig +.I "gatemachine localhost remotehost" +.B & +.br +.B /usr/ipc/mgrs/udpconfig +.I udp-device +.B & +.SH DESCRIPTION +.I Ipconfig +activates the DARPA Internet protocol on a communications device, +with Internet address +.I localhost +for the host +and network address +.I network +for the device. +.PP +If +.I arp-device +is specified, +the ARP address resolution protocol +is started on that device. +Option +.B -d +causes +.I ipconfig +to print ARP requests on the standard output +as they are received. +.PP +Option +.B -m +declares a subnet mask +for the network reached through +.IR ip-device . +.I Mask +may be a four-piece IP address like +.L 255.255.255.0 +or a 32-bit hexadecimal number like +.LR ffffff00 . +.PP +Option +.B -f +is a special workaround for networks with obsolete hosts. +It causes +.I ipconfig +to answer illegal ARP requests for the subnet's broadcast address +with an illegal Ethernet address, +to prevent broadcast storms. +.PP +.I Dkipconfig +places a network call to +.I gatemachine +and activates the IP protocol on the connection, +so that the remote machine becomes a gateway for the caller's IP traffic. +.I Localhost +becomes the calling machine's Internet address +through this IP interface; +.I remotehost +is the Internet address +to which local IP packets should be sent +to reach the gateway. +.PP +.I Ipconfig +and +.I dkipconfig +record unusual events and errors in +log files +.F /usr/ipc/log/ipconfig +and +.FR /usr/ipc/log/dkipconfig . +.PP +.I Udpconfig +activates the UDP datagram protocol +on the named +.IR udp-device , +usually +.FR /dev/ipudp . +Only one +.I udpconfig +is needed for the entire collection of IP networks. +.PP +These programs are usually run once from +.IR rc (8). +.SH EXAMPLES +The following calls start IP +on system +.B fs +on the first Interlan Ethernet controller, +with ARP active; +arrange for machine +.B nj/astro/research +to pass IP packets to +.BR fs ; +and activate +UDP. +.EX +/usr/ipc/mgrs/ipconfig /dev/il00 fs mh-astro-net /dev/il01 & +/usr/ipc/mgrs/dkipconfig nj/astro/research fs-dk research-dk127 & +/usr/ipc/mgrs/udpconfig /dev/ipudp & +.EE +.SH FILES +.F /usr/ipc/log/ipconfig +.br +.F /usr/ipc/log/dkipconfig +.SH "SEE ALSO" +.IR con (1), +.IR qns (7), +.IR route (8), +.IR tcpmgr (8) diff --git a/static/v10/man8/istat.8 b/static/v10/man8/istat.8 new file mode 100644 index 00000000..d44f3133 --- /dev/null +++ b/static/v10/man8/istat.8 @@ -0,0 +1,35 @@ +.pa 1 +.he 'ISTAT (VIII)'1/20/73'ISTAT (VIII)' +.ti 0 +NAME istat -- get inode status +.sp +.ti 0 +SYNOPSIS istat_____ [ filesystem ] inumber\d1\u ... +.sp +.ti 0 +DESCRIPTION istat_____ +gives information about one or more i-nodes +on the given file system or on /dev/rk0 if no file system +is given. +.sp +The information is in exactly the same form +as that for stat(I), +except that mode letter "a" is +used to indicate that the i-node is allocated, +"u" that it is unallocated. +.sp +.ti 0 +FILES /etc/uids, +/dev/rk0 +.sp +.ti 0 +SEE ALSO stat(I), ls(I) (-l option) +.sp +.ti 0 +DIAGNOSTICS -- +.sp +.ti 0 +BUGS istat_____ +ignores any read error +and pretends to give status even if the file system +is not physically present. diff --git a/static/v10/man8/kill.8 b/static/v10/man8/kill.8 new file mode 100644 index 00000000..0c6db3ff --- /dev/null +++ b/static/v10/man8/kill.8 @@ -0,0 +1,36 @@ +.pa 1 +.he 'KILL (VIII)'1/20/73'KILL (VIII)' +.ti 0 +NAME kill -- terminate process with extreme prejudice +.sp +.ti 0 +SYNOPSIS /usr/adm/kill_____________ processnumber +.sp +.ti 0 +DESCRIPTION After ps__ +(q.v.) has given you the unique ID of a process, you can terminate +it by this command. +A core image is produced in the process's working directory. + +Only the super-user can exercise this privilege. +.sp +.ti 0 +FILES -- +.sp +.ti 0 +SEE ALSO ps (VIII) +.sp +.ti 0 +DIAGNOSTICS yes +.sp +.ti 0 +BUGS If the process +has executed sys nice (II) +and there is another process which has not, but +which loops, +the first process cannot be done in properly, +since it has to be swapped in so as cooperate +in its own murder. + +It would also be nice if ordinary people could +kill their own processes. diff --git a/static/v10/man8/kmc.8 b/static/v10/man8/kmc.8 new file mode 100644 index 00000000..a2e40dc2 --- /dev/null +++ b/static/v10/man8/kmc.8 @@ -0,0 +1,107 @@ +.TH KMC 8 +.CT 1 sa_nonmortals +.SH NAME +kmc, kdiload, kmcdump \- control KMC11 input/output processors +.SH SYNOPSIS +.B /etc/kdiload +[ +.I dev +[ +.I file +] ] +.PP +.B /etc/kmcdump +[ +.I dev +] +.SH DESCRIPTION +These commands control the KMC11-B +microprocessors +used for Datakit protocol processing. +.PP +.I Kdiload +resets KMC device +.IR dev , +copies the microcode in +.IR file +into the KMC's memory, +and starts the KMC. +.I Dev +may be a pathname +or a single character key +identifying the KMC; +the default is +.LR 2 . +.I File +defaults to that specified in +.F /etc/kmctab +if a single character key is used, +.F /etc/dkk.dubhi +otherwise. +.PP +.I Kmcdump +stops the KMC +and copies its state into files +in the working directory. +.I Dev +may be a single character key +or a pathname; +the default is +.LR 2 . +The KMC's memory is copied to the file +.BI core. k . nnn\c +, +where +.I k +is the keyletter +and +.I nnn +is some number; +the state of the KMC's registers and some trace information from Unix +is written to +.BI regs. k . nnn\c +\&. +.PP +These commands search the file +.F /etc/kmctab +for KMC devices and microcode files. +The file contains lines of +three blank-separated fields: +.PP +.RS +single character identifying this KMC +.br +full pathname of the KMC device file +.br +full pathname of the microcode to be used in this KMC +.RE +.PP +The KMC with key +.I K +uses Datakit special files with names like +.BI /dev/dk/dk K 03\c +\&. +If there is only one KMC for Datakit, +its key is +.LR 2 . +If the only KMC is the only Datakit interface in a machine, +its key is +.LR 2 , +and its special files look like +.BR /dev/dk/dk03 . +.SH FILES +.F /etc/kmctab +.br +.F /bin/kasb +.SH SEE ALSO +.IR dkmgr (8) +.SH BUGS +For the moment, +the only permissible keys are +.L 0 +and +.LR 2 . +The KMC and Datakit filename conventions +are arcane, +and based on obsolete notions; +they should be replaced. diff --git a/static/v10/man8/ldpcs.8 b/static/v10/man8/ldpcs.8 new file mode 100644 index 00000000..31db6da2 --- /dev/null +++ b/static/v10/man8/ldpcs.8 @@ -0,0 +1,58 @@ +.TH LDPCS 8 VAX-11/750 +.CT 1 sa_auto +.SH NAME +ldpcs \- load comet microcode +.SH SYNOPSIS +.B /etc/ldpcs +[ +.B -f +] +[ +.B -v +] +.I pcsfile +.SH DESCRIPTION +.I Ldpcs +loads microcode +from +.I pcsfile +into the VAX-11/750 patchable control store. +Normally, +the hardware ID register is checked +to see that the system is an 11/750 +and that its base microcode revision level +is appropriately high; +the +.B -f +option +removes the checks. +The +.B -v +option causes the microcode version number +to be printed after loading. +.PP +.I Ldpcs +is usually called from +.IR rc (8) +to load the most recent +.SM DEC +microcode patches from +.FR /etc/pcs750.bin . +.PP +The patch file consists of +1024 bytes of patch bits, +followed by 10240 bytes of actual patches. +Each patch bit represents a 20-bit microcode word; +the patches themselves are 20-bit words +packed together. +The format is the same as that distributed by DEC. +.SH FILES +.F /dev/mem +.br +.F /dev/mtpr +.SH BUGS +Calling +.I ldpcs +is a good idea, +but it is not mandatory; +the system will run without the patches. diff --git a/static/v10/man8/login.8 b/static/v10/man8/login.8 new file mode 100644 index 00000000..50336078 --- /dev/null +++ b/static/v10/man8/login.8 @@ -0,0 +1,138 @@ +.TH LOGIN 8 +.CT 1 sa_auto +.SH NAME +login \- sign on +.SH SYNOPSIS +.B /etc/login +.I name +.br +.B /etc/login +.B -f +.I name +[ +.I cmd +] +.br +.B /etc/login +.B -p +.I passwd-line +[ +.I cmd +] +.SH DESCRIPTION +.I Login +is executed by +.IR getty (8). +See the Introduction to this volume for how to dial up initially. +.PP +.I Login +asks for a password if appropriate. +Echoing is turned off during the typing of the password. +The +.B -f +option forces login of the named user, without a password. +.B -p +is similar to +.BR -f , +but an entire line of password file information +is supplied. +.PP +.I Login +initializes the userid, the groupid, and the working directory +according to specifications found in the password file; +see +.IR passwd (5). +It also initializes environment variables +.SM PATH +and +.SM HOME . +Finally it executes a command interpreter (usually +.IR sh (1)). +Argument 0 of the command interpreter is its name with +a dash +.RL ( - ) +prepended. +If +a +.I cmd +argument was present, +two additional arguments +.B -c +.I cmd +are passed, +and environment variable +.SM REXEC +is set to +.LR 1 . +.PP +Upon a successful login, +accounting files are updated and, +if no options are present, +the message of the day is printed +and the user is informed of the +existence of mail. +.PP +Successful logins are recorded in +.F /etc/utmp +and +.FR /usr/adm/wtmp . +If +.I cmd +was present, +.L * +is appended to the login name in +.IR wtmp , +and +no record is made in +.IR utmp . +.PP +Only the super-user may execute +.IR login . +.SH FILES +.TF /usr/spool/mail/* +.TP +.F /etc/utmp +accounting +.TP +.F /usr/adm/wtmp +accounting +.TP +.F /usr/spool/mail/* +mail +.TP +.F /etc/motd +message-of-the-day +.TP +.F /etc/passwd +password file +.TP +.F /etc/group +groups file +.SH "SEE ALSO" +.IR newgrp (1), +.IR passwd (1), +.IR environ (5), +.IR passwd (5), +.IR getty (8), +.IR init (8), +.IR su (8), +.IR svcmgr (8). +.SH DIAGNOSTICS +`Login incorrect': +the name or the password is bad. +.br +`No Shell' or `no directory': the initial shell or +home directory specified in the password file does not exist. +.br +`Cannot open password file': things are badly curdled. +.SH BUGS +Information passed to options +.B -p +and +.B -f +is not checked. +Only trusted programs should run +.IR login . +Only trusted programs may usefully do so anyway; +.I login +has no privileges. diff --git a/static/v10/man8/makekey.8 b/static/v10/man8/makekey.8 new file mode 100644 index 00000000..193201bf --- /dev/null +++ b/static/v10/man8/makekey.8 @@ -0,0 +1,53 @@ +.TH MAKEKEY 8 +.CT 1 sa_nonmortals +.SH NAME +makekey \- generate encryption key +.SH SYNOPSIS +.B /usr/lib/makekey +.SH DESCRIPTION +.I Makekey +improves the usefulness of encryption schemes depending on a key by +increasing the amount of time required to search the key space. +It +reads 10 bytes from its standard input, and writes 13 bytes on its +standard output. +The output depends on the input in a way intended to +be difficult to compute (i.e. to require a substantial fraction of a +second). +.PP +The first eight input bytes +(the +.IR "input key" ) +can be arbitrary +.SM ASCII +characters. +The last +two (the +.IR salt ) +are best chosen from the set of digits, upper- and lower-case +letters, +.L . +and +.LR / . +The salt characters are repeated as the first two characters of the output. +The remaining 11 output characters are chosen from the same set as the salt +and constitute the +.I "output key." +.PP +The salt is used to select one of 4096 cryptographic +machines all based on the National Bureau of Standards +.SM DES +algorithm, but modified in 4096 different ways. +Using the input key as key, +a constant string is fed into the machine and recirculated +a number of times. +The 64 bits that come out are distributed into the +66 useful key bits in the result. +.PP +.I Makekey +is intended for programs, such as +.IR crypt (1), +that perform encryption. +Usually its input and output will be pipes. +.SH SEE ALSO +.IR crypt (1) diff --git a/static/v10/man8/mkfs.8 b/static/v10/man8/mkfs.8 new file mode 100644 index 00000000..595723ba --- /dev/null +++ b/static/v10/man8/mkfs.8 @@ -0,0 +1,138 @@ +.th MKFS VIII 11/1/73 +.sh NAME +mkfs \*- construct a file system +.sh SYNOPSIS +.bd /etc/mkfs +special +proto +.sh DESCRIPTION +.it Mkfs +constructs a file system +by writing on the special file +.it special +according to the directions +found in +the prototype file +.it proto. +The prototype file +contains tokens separated by spaces or +new lines. +The first token is the name of a file +to be copied onto block zero as +the bootstrap program +(see boot procedures(VIII)). +The second token is a number specifying the +size of the created file system. +Typically it will be the number of blocks on the device, +perhaps diminished +by space for swapping. +The next token is the i-list size in blocks +(remember there are 16 i-nodes per block). +The next set of tokens comprise the specification +for the root file. +File specifications consist of tokens +giving the mode, +the user-id, +the group id, +and the initial contents of the file. +The syntax of the contents field +depends on the mode. +.s3 +The mode token for a file is a 6 character string. +The first character +specifies the type of the file. +(The characters +.bd \*-bcd +specify regular, block special, +character special and directory files +respectively.) +The second character of the type +is either +.bd u +or +.bd \*- +to specify set-user-id mode or not. +The third is +.bd g +or +.bd \*- +for the set-group-id mode. +The rest of the mode +is a three digit octal number giving the +owner, group, and foreigner read, write, execute +permissions (see +.it chmod +(I)). +.s3 +Two decimal number +tokens come after the mode; they specify the +user and group ID's of the owner of the file. +.s3 +If the file is a regular file, +the next token is a pathname +whence the contents and size are copied. +.s3 +If the file is a block or character special file, +two decimal number tokens +follow which give the major and minor device numbers. +.s3 +If the file is a directory, +.it mkfs +makes the entries \fB.\fR and \fB..\fR +and then +reads a list of names and +(recursively) +file specifications for the entries +in the directory. +The scan is terminated with the +token \fB$\fR. +.s3 +If the prototype file cannot be opened and +its name consists of a string of digits, +.it mkfs +builds a file system with a single +empty directory on it. +The size of the file system is the value +of +.it proto +interpreted as a decimal number. +The i-list size is the file system size +divided by 50. +(This corresponds to an average size of +three blocks per file.) +The boot program is left uninitialized. +.s3 +A sample prototype specification follows: +.s3 +.nf +.in +5 +/usr/mdec/uboot +4872 55 +d\*-\*-777 3 1 +usr d\*-\*-777 3 1 + sh \*-\*-\*-755 3 1 /bin/sh + ken d\*-\*-755 6 1 + $ + b0 b\*-\*-644 3 1 0 0 + c0 c\*-\*-644 3 1 0 0 + $ +$ +.in -5 +.fi +.sh "SEE ALSO" +file system(V), +directory(V), +boot procedures(VIII) +.sh DIAGNOSTICS +There are various diagnostics for +syntax errors, +inconsistent values, +and sizes too small. +.sh BUGS +It is not possible to initialize a file larger than +64K bytes. +.br +The size of the file system is restricted to +64K blocks. +.br +There should be some way to specify links. diff --git a/static/v10/man8/mknod.8 b/static/v10/man8/mknod.8 new file mode 100644 index 00000000..ea3a5137 --- /dev/null +++ b/static/v10/man8/mknod.8 @@ -0,0 +1,79 @@ +.th MKNOD VIII 10/31/73 +.sh NAME +mknod \*- build special file +.sh SYNOPSIS +.bd /etc/mknod +name +[ +.bd c +] [ +.bd b +] +major +minor +.sh DESCRIPTION +.it Mknod +makes a directory entry and corresponding i-node +for a special file. +The first argument is the +.it name +of the entry. +The second is +.bd b +if the special file is block-type (disks, tape) or +.bd c +if it is character-type (other devices). +The last two arguments are +numbers specifying the +.it major +device type +and the +.it minor +device (e.g. unit, drive, or line number). +.s3 +The assignment of major device numbers is specific to each system. +For reference, here are the numbers for the MH 2C-644 machine. +Do not believe them too much. +.s3 +Block devices: +.lp +8 4 +0 RF fixed-head disk +.lp +8 4 +1 RK moving-head disk +.lp +8 4 +2 TC DECtape +.lp +8 4 +3 TM magtape +.lp +8 4 +4 RP moving-head disk +.lp +8 4 +5 Vermont Research moving-head disk +.i0 +.s3 +Character devices: +.lp +8 4 +0 KL on-line console +.lp +8 4 +1 DC communications lines +.lp +8 4 +2 PC paper tape +.lp +8 4 +3 DP synchronous interface +.lp +8 4 +4 DN ACU interface +.lp +8 4 +5 core memory +.lp +8 4 +6 VT scope (via 11/20) +.lp +8 4 +7 DA voice response unit +.lp +8 4 +8 CT phototypesetter +.lp +8 4 +9 VS voice synthesizer +.lp +8 4 +10 TIU Spider interface +.i0 +.sh "SEE ALSO" +mknod (II) +.sh BUGS diff --git a/static/v10/man8/mkpkg.8 b/static/v10/man8/mkpkg.8 new file mode 100644 index 00000000..50032998 --- /dev/null +++ b/static/v10/man8/mkpkg.8 @@ -0,0 +1,179 @@ +.TH MKPKG 8 +.CT 1 comm_mach +.SH NAME +mkpkg, inspkg, seal, unseal \- package files for automatic software distribution +.SH SYNOPSIS +.B mkpkg +[ +.I option ... +] +.I file ... +.PP +.B inspkg +[ +.I option ... +] +[ +.I file ... +] +.PP +.B seal +[ +.I option +] +[ +.I file ... +] +.PP +.B unseal +[ +.I option +] +[ +.I file ... +] +.SH DESCRIPTION +These programs are used by +.IR ship (8) +to keep files identical across machines. +.PP +.I Mkpkg +packages +.I files +and writes the result on the standard output. +.I Inspkg +installs the named packages +or the standard input. +.PP +Non-existent files given to +.I mkpkg +are deleted upon installation. +Directories are copied with all their contents. +Hard links are reproduced. +Symbolic links and special files +are reproduced with the same inode contents. +File modification and access times and owner and group names +are reproduced as far as possible. +Old versions of files are removed before installation: +.I inspkg +needs write permission in containing directories. +.PP +Options for both +.I mkpkg +and +.IR inspkg : +.nr xx \w'\f5-K \f2keyfile ' +.TP \n(xxu +.B -v +Place running commentary on the standard error file. +.br +.ns +.TP +.BI -D path1 = path2 +Pretend that any pathname beginning with +.I path1 +really begins with +.IR path2 . +Relative pathnames are extended to full pathnames before comparison. +.PP +Options for +.IR mkpkg ; +only one may occur: +.TP \n(xxu +.BI -x command +Include in the package instructions to execute the shell +.I command +after all files have been installed. +.I Command +is unaffected by option +.BR -D . +.br +.ns +.TP +.BI -X file +Include in the package instructions to +run the shell script +.I file +after all files have been installed. +The file name is subject to option +.BR -D . +.PP +Options for +.IR inspkg : +.TP \n(xxu +.B -n +Skip the actual installation, but verify +the input packages and produce a backup if requested. +.br +.ns +.TP +.B +-b +Write on the standard output a backup package +that contains whatever was destroyed. +.PP +A package is an +.IR ar (1) +archive containing an extra +.SM ASCII +file named +.FR Instructions . +.PP +.I Seal +concatenates the named +.I files +or the standard input +onto the standard output in +an error-detecting form suitable for shipment by +.IR mail (1). +.I Unseal +reverses the process, concatenating copies of all the +original inputs onto the standard output. +When +.IR asd (8) +uses +.IR uucp (1), +it sends sealed packages. +.PP +A sealed file is printable, has +fewer than 128 characters per line, and has no lines +consisting of a single period. +The first line is +.L !<seal> +and the last one begins with +.LR !end . +Other lines, such as mail headers, can be added to +either end of a sealed file +without hindering +.IR unseal . +.PP +Options for +.I seal +and +.IR unseal : +.TP \n(xxu +.B -k +A key will be demanded to encrypt the +checksum calculation. +.br +.ns +.TP +.BI -K " keyfile" +Same, but taking the first line of +.I keyfile +as the key. +.SH SEE ALSO +.IR ar (1), +.IR cpio (1), +.IR tar (1), +.IR bundle (1), +.IR ship (8), +.IR ar (5), +.IR asd (8) +.SH BUGS +The pipeline +.L mkpkg ... | inspkg +fails if input and output files overlap. +.br +.I Inspkg +fills any holes in files. diff --git a/static/v10/man8/mount.8 b/static/v10/man8/mount.8 new file mode 100644 index 00000000..1dfa16a2 --- /dev/null +++ b/static/v10/man8/mount.8 @@ -0,0 +1,153 @@ +.TH MOUNT 8 +.CT 1 sa_nonmortals +.SH NAME +mount, umount \- mount and dismount file system +.SH SYNOPSIS +.B /etc/mount +[ options ] +[ +.I special name +[ +.I fstype +[ +.I flags +] ] ] +.PP +.B /etc/mount +.B -a +.PP +.B /etc/mount +[ +.I special name +[ +.B -r +] +] +.PP +.B /etc/umount +.I name +.PP +.B /etc/umount +.B -a +.SH DESCRIPTION +.I Mount +announces to the system that a removable file system +of type +.I fstype +is present on the file +.I special. +The file +.I name +must exist already; it +must be a directory (unless the root of the +mounted file system is not a directory). +It becomes the name of the newly mounted root. +See +.IR fmount (2) +for a list of file system types +and appropriate flags. +If +.I fstype +or +.I flags +is omitted, +zero is assumed; +file system type 0 +is an ordinary disk file system. +.PP +The options are +.TP +.B -a +Mount all the files designated in +.FR /etc/fstab ; +see +.IR fstab (5). +No other arguments are legal with +.BR -a . +.TP +.B -r +Read only; shorthand for +.I fstype +0 +and +.I flag +1. +A deprecated usage allows +.B -r +to follow +.I name. +.TP +.BI -l " label +The +.I label, +given in the form of +.I atolab +(see +.IR labtoa (3)), +becomes the file system ceiling described in +.IR fmount (2). +.PP +.I Umount +announces to the system that the file system mounted on file +.I name +is to be removed. +.PP +If the +.B -a +option is present for +.I mount +.RI ( umount ), +an attempt is made to mount (remove) each file system named in +.FR /etc/fstab +(\c +.FR /etc/mtab ). +.PP +These commands +maintain a table of mounted devices in +.FR /etc/mtab . +If invoked without an argument, +.I mount +prints the table. +.PP +Physically write-protected and magnetic tape file +systems must be mounted read-only +or errors will occur when access times are updated, +whether or not any explicit write is attempted. +.SH EXAMPLES +.TP +.B "/etc/mount /dev/ra02 /usr" +Mount the file system on disk +.L /dev/ra02 +on directory +.LR /usr . +.TP +.B "/etc/mount /dev/null /proc 2" +Mount the process file system. +.TP +.B " /etc/mount -l 'nu u ffff...' /dev/ra02 /usr +File capabilities on +.IR exec (2) +are limited to +.BR T_NOCHK +and +.BR T_UAREA , +with self-licensing only for +.BR T_UAREA ; +all lattice labels are accessible (ceiling is lattice top). +.SH FILES +.TF /etc/fstab +.TP +.F /etc/mtab +mount table +.TP +.F /etc/fstab +file system table +.SH "SEE ALSO" +.IR fmount (2), +.IR fstab (5), +.IR netfs (8) +.SH BUGS +Mounting file systems full of garbage will crash the system. +.br +Mounting a root directory on a non-directory +makes some apparently good pathnames invalid. diff --git a/static/v10/man8/netfs.8 b/static/v10/man8/netfs.8 new file mode 100644 index 00000000..d4b97656 --- /dev/null +++ b/static/v10/man8/netfs.8 @@ -0,0 +1,315 @@ +.TH NETFS 8 +.CT 1 sa_nonmortals +.SH NAME +netfs \- network file system +.SH SYNOPSIS +.nf +.B /usr/netb/setup.go +.fi +.SH DESCRIPTION +The network file system is conventionally a set of directories +contained in +.FR /n , +and a set of files and programs in +.FR /usr/netb . +Connections in the network file system are asymmetric: +files on a `server' system are made accessible on a `client' system, +usually in directory +.BI /n/ server-name. +.SS Client +The client runs +.FR /usr/netb/setup +to maintain connections; +it is started by invoking +.F /usr/netb/setup.go +from +.IR rc (8). +.I Setup +uses +.F /usr/netb/friends +to control the connections to servers. +Each line in +.I friends +contains six fields: +.RS +network address +.br +network call argument +.br +mount point +.br +protocol id +.br +unique identifier +.br +debugging flag +.br +network calling username +.RE +.PP +The network address and argument give the location of the server. +They are interpreted differently according to the protocol id, +which should be one of +.TP +.B d +Call the server on the named network address, +with default network +.L dk +and default service name +.LR fsb . +The network call argument is ignored. +The server machine should respond by calling +.IR zarf , +described below; +see +.IR svcmgr (8). +.TP +.B t +Call the named network address, +with default network +.LR tcp , +and invoke the program named in the +network call argument +using the protocol of +.IR rsh ; +.IR con (1). +.PP +.I Setup +calls +.IR setlogname +(see +.IR getuid (2)) +to make the network call appear to have been placed +by the calling username. +The username may be omitted; +.LR daemon +is the default. +.PP +The mount point is the directory +on which the remote file system is to appear. +The unique identifier is a integer in the range 0-255; +it is used internally to distinguish connections, +and must be unique among all active remote file systems +(including those not maintained by +.IR setup , +e.g. +.IR faced (9.5)). +The debugging flag is usually 0; +nonzero numbers +increase the chatter in various logfiles. +.PP +.I Setup +reads the +.I friends +file when it starts, +and checks for changes once a minute. +Each remote file system is probed once a minute; +if there is no response to several consecutive probes, +the connection is torn down and restarted. +Failed connections are retried every minute. +.SS Server +The server program is +.FR /usr/netb/zarf . +A separate +.I zarf +process exists for each client. +.PP +When a connection is started, +the client sends the server a list of valid user and group names +and the corresponding numerical IDs +on the client system. +The userid and groupid of user and group names that exist +on both machines are mapped so that +client and server see IDs +under the same names. +Unmapped IDs on the server appear as \-1 on the client. +Client processes with unmapped IDs are denied access. +.PP +.I Zarf +is subject to access control on the server. +It will have access only to files that its own userid +and groupid admit. +Unless run as super-user, it will create files with its own, +not mapped, userid. +.PP +.I Zarf +reads configuration information +from +.F /usr/netb/except.local +and +.FR /usr/netb/except . +The +files are read only once, +when +.I zarf +starts, +.B except.local +first. +Usually +.B except +is the same on all machines in some administrative cluster, +.B except.local +contains things specific to a particular server system. +.PP +The files contain sections +beginning with the line +.B client +.I origin. +.I Origin +is the name of the calling client, +as provided by the network; +.L * +matches any client. +The first matching section is used. +.PP +Within each section, +lines have of one of the following forms. +Lines beginning with +.L # +are ignored. +.TP +.BI "uid " cname = sname +Regardless of the contents of password files, +map client user name +.I cname +to server user name +.IR sname . +If +.I cname +is not announced as valid by the client, +the line is ignored. +If +.I sname +is not a valid name on the server, +any previous mapping for +.I cname +is discarded. +.TP +.BI "gid " cname = sname +Map client group name +.I cname +to server group name +.IR sname , +as above. +.TP +.BI "param otherok=" val +If +.I val +is +.LR 1 , +client processes with unmapped userids +are granted world access +to existing files on the server. +Unmapped userids +may never create files +(who would own them?). +If +.I val +is anything else, +no access is permitted +to +unmapped client userids. +.TP +.BI "param root=" pathname +Use +.I pathname +rather than +.B / +as the root of the filename hierarchy +made visible on the client. +.SH EXAMPLES +A +.I friends +file +for a connection to +.B alice +over Datakit, +.B shamash +over TCP/IP, +and +.B bebop +over TCP/IP +without administrative help: +.RS +.EX +.ta \w'tcp!shamash!400 'u +\w'/usr/pjw/netb/zarf 'u +\w'/n/alice 'u +.3i +.3i +.3i +alice - /n/alice d 0 0 +tcp!shamash!400 - /n/sun d 1 0 +bebop /usr/pjw/netb/zarf /n/bebop t 2 0 pjw +.EE +.RE +.PP +Some +.I except +file rules: +.RS +.EX +client dk!nj/astro/research +param otherok=1 +client * +uid root= +gid mail=other +param otherok=0 +param root=/usr/spool +.EE +.RE +.PP +If the +.I research +machine calls as a client, +the whole file system tree is visible, +all userids including the super-user +are permitted normal access, +and user names unknown to the server +are permitted world access. +If any other machine calls, +only the contents of +.B /usr/spool +are visible, +.I root +and unknown users +are explicitly denied access, +and +processes in group +.I mail +on the client +are treated as if in group +.I other +on the server. +.SH FILES +.PD 0 +.TF /usr/netb/except.local +.TP +.F /n/* +.TP +.F /usr/netb/friends +client connection info +.TP +.F /usr/netb/except.local +.TP +.F /usr/netb/except +.TP +.F /usr/netb/setupl +log file for +.I setup +.TP +.F /usr/netb/zarf.log +log file for zarf +server control info +.SH SEE ALSO +S. A. Rago, `A Look at the Version 9 Network File System', +this manual, Volume\ 2 +.SH BUGS +The scheme works only in a modest-sized, friendly community, as it +requires a process per client, trust of clients' security, and common +login names. +.br +File modification times are adjusted for clock-time differences +between machines. +Thus, when viewed across the network, +identical files installed on different machines by +.IR asd (8) +may appear to have different modification times, and +symbol tables of random libraries +.RI ( ar (1)) +may appear to be out of date. diff --git a/static/v10/man8/netstat.8 b/static/v10/man8/netstat.8 new file mode 100644 index 00000000..2cc7257f --- /dev/null +++ b/static/v10/man8/netstat.8 @@ -0,0 +1,100 @@ +.TH NETSTAT 8 +.CT 1 sa_nonmortals +.SH NAME +netstat, dkstat \- show network status for internet and datakit networks +.SH SYNOPSIS +.B netstat +[ +.B \-acCirRst +] +[ +.I system +] +[ +.I core +] +.PP +.B dkstat +[ +.I interval +[ +.I count +] +] +.SH DESCRIPTION +.I Netstat +displays internet +(TCP/IP and UDP/IP) +traffic and configuration +data. +Without options, +it lists all TCP and UDP connection assignments. +A single option +changes the listing: +.TP +.B -a +known mappings between internet names and +Ethernet addresses. +.TP +.B -c +all TCP and UDP connection assignments +(the default). +.TP +.B -C +detailed state of active TCP connections. +.TP +.B -i +active IP interfaces. +.TP +.B -n +display numeric internet addresses rather than host and +network names. +.TP +.B -s +protocol statistics. +.TP +.B -r +routing tables. +.TP +.B -R +routing tables, +including deleted entries +(for debugging). +.TP +.BI -t buf +running trace of +packets passing through +.IR buf : +.L il +for the Interlan Ethernet controller, +.L qe +for the DEQNA, +.L tcp +(the default) +for all packets passing through TCP. +.PP +The arguments +.I system +and +.I core +are substitutes for the defaults +.F /unix +and +.FR /dev/kmem . +.PP +.I Dkstat +reports the number of bytes received and sent over +the Datakit network, together with error reports if any occurred. +The first report is cumulative since a reboot. +Further reports may be requested every +.I interval +seconds; these reports are incremental. +.PP +The optional +.I count +argument restricts the number of reports. +.SH DIAGNOSTICS +.BR "nlist /unix failed" : +.I netstat +could not find pertinent system information, +perhaps because this system isn't set up for TCP/IP. diff --git a/static/v10/man8/nosh.8 b/static/v10/man8/nosh.8 new file mode 100644 index 00000000..7447f767 --- /dev/null +++ b/static/v10/man8/nosh.8 @@ -0,0 +1,138 @@ +.TH NOSH 8 +.CT 1 shell proc_man dirs files +.SH NAME +nosh \- `no-surprise' shell, a sub-standard command interpreter +.SH SYNOPSIS +.B /etc/nosh +[ +.I file +] +.PP +.B priv nosh -gunxlp +.I file +.SH DESCRIPTION +.I Nosh +executes commands read from its standard input +or from the named +.IR file . +It has few of the advanced features of +.IR sh (1), +making it more trustable for use in +security administration tasks. +In the second usage, +.I nosh +is endowed with one or more of the licenses +.BR gunxlp ; +see +.IR labtoa (3). +.SS Commands +A +command is either +.I simple +or +.I builtin. +Each command consists of +a sequence of +.I words +separated by white space, +terminated by a new-line character or end of input. +Backslash quoting and sharp commenting are honored. +The first word specifies the name of the command to +be executed. +If the command name matches one of the builtins +listed below it is executed in the shell process. +If the command name matches no +builtin command, it is taken to be the +pathname of an executable file; the name must begin with +.L / +or +.LR . . +A new process is created and an attempt is made to +execute the file via +.IR exec (2) +with an empty environment. +.SS Input-Output Redirection +The standard input is inherited by simple commands. +Simple +.B > +output redirection to named files as in +.IR sh (1) +works only for simple commands, and only for file +descriptors 1 (default) and 2. +.SS Builtin Commands +.PP +.PD 0 +.TP +.BI cd " dir +Change the current directory to +.I dir. +.TP +.BI exit " status +Exit with given status, 0 by default. +.TP +.B set +e +.TP +.B set -e +Turn an ignore-error switch on +.RB ( +e , +default) or off +.RB ( -e ). +.I Nosh +normally ignores nonzero exit status from an executed +command, but exits with that status if +.B -e +is set. +.TP +.B set +x +.TP +.B set -x +Refrain from echoing +.RB ( +x , +default) or echo +.RB ( -x ) +each command as it is executed. +.TP +.BI lmask " licenses command \fR[\fP arg \fR... ]\fP +Run a simple command, allowing licenses +indicated by a nonempty string from the set +.BR gunxlp- +to be inherited from +.I nosh. +Normally no licenses are inherited. +.SS Missing features +Features of +.IR sh (1) +that +.IR nosh +lacks include: +background commands, pipelines, compound commands, most builtins, +multicharacter quotation, +command substitution, parameter substitution, variables, environments, +file name generation, redirection of input, signal traps, +search paths, mail notification, +.BR .profile , +user specification of prompts. +.SH DIAGNOSTICS +.I Nosh +prints nonzero exit or termination status +of executed commands as octal numbers labeled +.L e= +and +.LR t= ; +see +.IR wait (2). +If invoked with a +.I file +argument, it exits unconditionally for nonzero termination +status or syntax error, and conditionally (under control of +.LR set ) +for nonzero exit status. +.PP +.I Nosh +exits immediately if +invoked with more than one argument, +if invoked with an argument with a relative path name, +if invoked by a relative path name, or if invoked +with interrupt or quit signals ignored. +.SH SEE ALSO +.IR sh (1) diff --git a/static/v10/man8/ns.8 b/static/v10/man8/ns.8 new file mode 100644 index 00000000..620e80e3 --- /dev/null +++ b/static/v10/man8/ns.8 @@ -0,0 +1,153 @@ +.TH NS 8 +.CT 1 sa_auto +.SH NAME +ns \- name server database +.SH SYNOPSIS +.B /usr/ipc/mgrs/ns +[ +.B -m +.I server +] [ +.B -d +] +.SH DESCRIPTION +.I Ns +maintains a database +of naming information, +accessed by +.IR qns (7) +and other programs. +It should be run once from +.IR rc (8). +.PP +The database is accessed +through local service +.BR ns , +or service +.I server +if option +.B -m +was specified. +.PP +The file +.F /usr/ipc/lib/ns.db +contains instructions for building the database. +These instructions are lines +of one of the following forms: +.TP \w'#include\0file\0\0\0\0'u \" wrong fonts; near enough? +.BI #uusys " file" +Read the named +.I uucp +.B Systems +.IR file . +For entries using caller +.LR ACU , +add a database entry containing +.RS +.IP +.I system\0 +.IB telephone-number ,tel\0 +.B uucp,svc +.PP +For entries using caller +.LR DK +or +.LR DKH , +add an entry containing +.IP +.I system\0 +.IB datakit-address ,dk\0 +.B uucp,svc +.PP +For any other entry, +add +.IP +.I system\0 +.B uucp,svc +.RE +.TP +.BI #inhost " file" +For each line in the named +4BSD-style internet hosts +.IR file , +add a database entry of the form +.RS +.IP +.IB ip-address ,in\0 +.I hostname\0 +.IB host-domain-name ,dom +.RE +.TP +.BI #innet " file" +For each line in the named +4BSD-style internet networks +.IR file , +add a database entry of the form +.RS +.IP +.IB ip-net-address ,in\0 +.I netname +.RE +.TP +.BI #include " file" +Interpret +the contents of +.IR file +in the same format +as +.BR ns.db . +.PP +In all cases, +.I file +may be followed by +a list of +.I value,attribute +pairs to be included with any +database entries caused by that file. +If the filename doesn't begin with +.LR / , +it is prefixed with +.BR /usr/ipc/lib . +.PP +Blank lines +and +lines beginning with +.L # +followed by a space or tab +are ignored. +.PP +Any other lines are taken as literal database entries: +a collection of +.I value,attribute +pairs separated by spaces. +Each line is a single entry. +.PP +The database is ephemeral; +it is rebuilt whenever +.I ns +starts, +when requested by +.BR "qns reset" , +or when +.I ns +notices that +.B ns.db +or one of the files named therein +has changed. +Rebuilding can take several minutes, +especially on a busy machine. +During a rebuild, +the server appears active but does not answer requests; +calls will block until the rebuild finishes. +.PP +.I Ns +leaves remarks in file +.FR /usr/ipc/log/ns . +There are more remarks if the +.B -d +option was used. +.SH FILES +.F /usr/ipc/lib/ns.db +.SH SEE ALSO +.IR ipc (3), +.IR qns (7) diff --git a/static/v10/man8/postbgi.8 b/static/v10/man8/postbgi.8 new file mode 100644 index 00000000..48e2742f --- /dev/null +++ b/static/v10/man8/postbgi.8 @@ -0,0 +1,138 @@ +.TH POSTBGI 8 local +.SH NAME +postbgi \- PostScript translator for BGI (Basic Graphical Instructions) files +.SH SYNOPSIS +.B postbgi +[ options ] [ files ] +.SH DESCRIPTION +.I Postbgi +translates BGI (Basic Graphical Instructions) +.I files +into PostScript and writes the results on the +standard output. +If no +.I files +are specified, or if \- is one of the input +.I files, +the standard input is read. +The following +.I options +are understood: +.TP 1.0i +.BI \-c num +Print +.I num +copies of each page. +By default only one copy is printed. +.TP 1.0i +.BI \-f name +Print text using font +.I name. +Any PostScript font can be used, +although the best results will only be +obtained with constant width fonts. +The default font is Courier. +.TP 1.0i +.BI \-m num +Magnify each logical page by the factor +.I num. +Pages are scaled uniformly about the origin, +which by default is located at the center of +each page. +The default magnification is 1.0. +.TP 1.0i +.BI \-n num +Print +.I num +logical pages on each piece of paper, +where +.I num +can be any positive integer. +By default +.I num +is set to 1. +.TP 1.0i +.BI \-o list +Print pages whose numbers are given in the comma-separated +.IR list . +The list contains single numbers +.I N +and ranges +.IB N1 \- N2. +A missing +.I N1 +means the lowest numbered page, a missing +.I N2 +means the highest. +.TP 1.0i +.BI \-p mode +Print +.I files +in either +.B portrait +or +.B landscape +.I mode. +Only the first character of +.I mode +is significant. +The default +.I mode +is portrait. +.TP 1.0i +.BI \-w num +Set the line width used for graphics to +.I num +points, where a point is approximately 1/72 +of an inch. +By default +.I num +is set to 0.0 points, which forces lines to be +one pixel wide. +.TP 1.0i +.BI \-x num +Translate the origin +.I num +inches along the positive x axis. +The default +coordinate system has the origin fixed at the +center of the page, with positive +x to the right and positive y up the page. +Positive +.I num +moves everything right. +The default offset is 0 inches. +.TP 1.0i +.BI \-y num +Translate the origin +.I num +inches along the positive y axis. +Positive +.I num +moves everything up the page. +The default offset is 0 inches. +.TP 1.0i +.BI \-A file +Append a simple accounting record to +.I file +after all the input +.I files +have been successfully translated. +By default no accounting data is produced. +.TP 1.0i +.BI \-L file +Use +.I file +as the PostScript prologue, +which by default is /usr/lib/postscript/postbgi.ps. +.SH DIAGNOSTICS +0 exit status is returned if +.I files +were successfully processed. +.SH BUGS +The default line width is too small for 'write to white' +print engines, like the one used by the PS-2400. +.SH FILES +/usr/lib/postscript/postbgi.ps +.SH SEE ALSO +dpost(1), postprint(1), posttek(1), postdmd(1) diff --git a/static/v10/man8/postio.8 b/static/v10/man8/postio.8 new file mode 100644 index 00000000..fdd5721e --- /dev/null +++ b/static/v10/man8/postio.8 @@ -0,0 +1,205 @@ +.TH POSTIO 8 +.CT 1 sa_auto +.SH NAME +postio \- serial interface for postscript printers +.SH SYNOPSIS +.B /usr/bin/postscript/postio +[ +.I option ... +] [ +.I file ... +] +.SH DESCRIPTION +.I Postio +sends +.I files +to a PostScript printer. +It is usually called by the innards of +.IR lp (1). +If no files are named, +the standard input is sent. +.PP +Mandatory argument +.B -l +names the printer. +If +the first character of +.I line +is +.LR / , +it is assumed to be a local filename like +.LR /dev/tty37 . +Otherwise it is taken to be a network address, +with default network +.LR dk , +to which the printer is connected. +.PP +These options are probably the most useful: +.nr xx \w'\fL-b\ \fIspeed\ 'u +.TP \n(xxu +.BI \-b speed +Transmit data +at baud rate +.I speed, +one of 1200, 2400, 4800, 9600 (default), and 19200. +.TP +.B \-q +Disable status queries while +.I files +are being sent to the printer. +When status queries are disabled a dummy message is appended +to the log file before each block is transmitted. +.TP +.BI \-B num +Set the internal buffer size for reading and writing +.I files +to +.I num +bytes, 2048 by default. +.TP +.B \-D +Debug mode: +copy everything read from the printer +to the log file +or standard error. +.TP +.BI \-L file +Log data read from the printer in +.IR file . +Standard error is the default. +Normally only messages indicating a change in the printer's state are logged. +.TP +.BI \-P string +Send +.I string +to the printer before any input +.IR files . +The default +is PostScript code that disables timeouts. +.TP +.BI \-R num +If +.I num +is +.LR 1 , +run as a single process; +if +.LR 2 , +use separate processes for reading and writing. +.PP +These options are not useful to spoolers like +.IR lp . +.TP \n(xxu +.B \-i +Interactive mode: +send the +.I files +to the printer, +then copy standard input to the printer +and printer output to standard error. +Overrides many other options. +To have a friendly chat with the printer, +begin by typing +.L executive +on a line by itself. +.TP +.B \-t +Copy printer output that doesn't look like +status information to the standard output; +intended for use with PostScript programs that write results. +.PP +This option should be used only as a last resort: +.TP \n(xxu +.B \-S +Take special measures to send data slowly. +Limits the internal buffer to 1024 bytes, +implies +.B -R1 +and disables +.BR -q +and +.BR -i . +Expensive in CPU time. +.PP +When +.I postio +starts, +it attempts to force the printer into IDLE state +by sending a sequence of +.RB control- t +(status query), +.RB control- c +(interrupt), +and +.RB control- d +(end of job) +characters. +When the printer is idle, +the files are transmitted +with an occasional +.RB control- t +interspersed +(except under +.BR -q ). +After all data have been sent, +.I postio +waits until the printer appears to have finished +before exiting. +Fatal error messages from the printer +cause +.I postio +to exit prematurely. +.SH EXAMPLES +.TP +.L +postio -l/dev/tty01 file1 file2 +Runing as a single process at 9600 baud, send file1 and file2 +to printer +.LR /dev/tty01 . +.TP +.L +postio -R2 -B4096 -l/dev/tty01 -Llog file1 file2 +Similarly, +but use two processes +and a 4096-byte buffer, +and copy printer messages to file +.BR log . +.TP +.L +postio -t -l/dev/tty22 -Llog program >results +Send the PostScript +.L program +to printer +.BR /dev/tty22 , +place any data in +.BR results , +put error messages in +.BR log . +.TP +.L +postio -i -l/cs/dk!my/printer +Connect interactively to the printer at network address +.BR /cs/dk!my/printer . +.SH SEE ALSO +.IR lp (1), +.IR postscript (8) +.SH DIAGNOSTICS +Exit status 1 means a system error +(e.g. can't open the printer), +2 means a PostScript error, +3 means both. +Status 2 is usually caused by a syntax error in an input file. +.SH BUGS +Multiple +files +with PostScript end-of-job marks +are not guaranteed to work. +.PP +If a network is involved, +.B \-b +may be ineffective and attempts by +.I postio +to flow-control data in both directions may not work. +Option +.B \-q +can help if the printer is connected to Radian Datakit. diff --git a/static/v10/man8/postreverse.8 b/static/v10/man8/postreverse.8 new file mode 100644 index 00000000..4b16537e --- /dev/null +++ b/static/v10/man8/postreverse.8 @@ -0,0 +1,97 @@ +.TH POSTREVERSE 8 local +.SH NAME +postreverse \- reverse the page order in a postscript file +.SH SYNOPSIS +.B postreverse +[ options ] [ file ] +.SH DESCRIPTION +.I Postreverse +reverses the page order in a minimally conforming PostScript +.I file +and writes the results on the standard output. +If no +.I file +is specified, the standard input is read. +The following +.I options +are understood: +.TP 1.0i +.BI \-o list +Select pages whose numbers are given in the comma-separated +.IR list . +The list contains single numbers +.I N +and ranges +.IB N1 \- N2. +A missing +.I N1 +means the lowest numbered page, a missing +.I N2 +means the highest. +.TP 1.0i +.B \-r +Don't reverse the pages in +.I file. +.TP 1.0i +.BI \-T dir +Use +.I dir +as the temporary file directory when +reading from the standard input. +By default +.I dir +is set to /tmp. +.PP +.I Postreverse +can handle files the violate page independence, +provided all global definitions are bracketed by +\&\f(CW%%BeginGlobal\fP and \&\f(CW%%EndGlobal\fP +comments. +In addition files that mark the end of each page +with \&\f(CW%%EndPage: label ordinal\fP comments +will also reverse properly, provided the prologue and +trailer sections can be located. +If the end of the prologue isn't found, the entire +.I file +is copied, unmodified, to the standard output. +.PP +Since global definitions are pulled out of individual +pages and put in the prologue, the output file can be +minimally conforming, even if the input +.I file +wasn't. +.SH EXAMPLES +Select pages 1 to 100 from +.B file +and reverse the pages, +.PP +.RS +\f(CWpostreverse -o1-100 file\fP +.RE +.PP +Print 4 logical pages on each physical page +and reverse all the pages, +.PP +.RS +\f(CWpostprint -n4 file | postreverse\fP +.RE +.PP +Produce a minimally conforming file from output +generated by dpost without reversing the pages, +.PP +.RS +\f(CWdpost file | postreverse -r\fP +.RE +.PP +.SH DIAGNOSTICS +0 exit status is returned if +.I file +was successfully processed. +.SH BUGS +No attempt has been made to deal with redefinitions of global +variables or procedures. +If standard input is used, the input +.I file +will be read three times before being reversed. +.SH SEE ALSO +dpost(1), postprint(1), posttek(1), postbgi(1), postdmd(1) diff --git a/static/v10/man8/postscript.8 b/static/v10/man8/postscript.8 new file mode 100644 index 00000000..2143c6b2 --- /dev/null +++ b/static/v10/man8/postscript.8 @@ -0,0 +1,283 @@ +.TH POSTSCRIPT 8 +.CT 1 sa_auto +.SH NAME +dpost, postdaisy, postdmd, postprint \- filters to produce postscript +.SH SYNOPSIS +.B /usr/bin/postscript/dpost +[ +.I option ... +] [ +.I file ... +] +.PP +.B /usr/bin/postscript/postdaisy +[ +.I option ... +] [ +.I file ... +] +.PP +.B /usr/bin/postscript/postdmd +[ +.I option ... +] [ +.I file ... +] +.PP +.B /usr/bin/postscript/postprint +[ +.I option ... +] [ +.I file ... +] +.PP +.B /usr/bin/postscript/posttek +[ +.I option ... +] [ +.I file ... +] +.SH DESCRIPTION +These programs convert files of various formats into +PostScript. +The input formats are +.nr xx \w'\fL-p\ \fImode\ 'u +.TP \n(xxu +.I dpost +.IR troff (1) +output +.TP +.I postdaisy +Diablo 1640 daisy-wheel +.TP +.I postdmd +.IR bitfile (9.5) +files, as produced by +.IR blitblt (9.1) +.TP +.I postprint +.SM +ASCII +text +.TP +.I posttek +Tektronix 4014 graphics +.PP +Except as noted, +the options are common to all the programs: +.TP \n(xxu +.BI \-c num +Print +.I num +copies of each page. +By default only one copy is printed. +.TP +.BI \-m num +Magnify each logical page by the factor +.I num. +Pages are scaled uniformly about the origin, +located near the upper left corner of +the page. +The default magnification is 1.0. +.TP +.BI \-n num +Print +.I num +logical pages on each piece of paper. +The default is 1. +.TP +.BI \-o list +Print only pages specified in +the comma-separated +.I list +of numbers and ranges. +A range +.IB N - M +means pages +.I N +through +.IR M ; +an initial +.BI - N +means +from the beginning to page +.IR N ; +and a final +.IB N - +means +from +.I N +to the end. +Print only pages whose numbers are given in the comma-separated +.IR list . +The list contains single numbers +.I N +and ranges +.IB N1 \- N2. +A missing +.I N1 +means the lowest numbered page, a missing +.I N2 +means the highest. +.TP +.BI \-p mode +Print +in +.I mode +.B p +(portrait) +or +.B l +(landscape). +The default is +.BR p . +.TP +.BI \-x num +Translate the origin +.I num +inches along the positive x axis. +By default, +the origin is +fixed near the +upper left corner of the page, with positive +x to the right and positive y down the page. +Positive +.I num +moves everything right. +The default offset is 0 inches. +.TP +.BI \-y num +Translate the origin +.I num +inches along the positive y axis. +Positive +.I num +moves text down the page. +The default offset is 0. +.TP +.BI \-A file +Append a simple accounting record to +.I file +after all input +.I files +have been successfully translated. +By default no accounting data is produced. +.TP +.BI \-L file +Use +.I file +as the PostScript prologue. +.TP +.BI \-f name +Print +.I files +using font +.I name. +Any PostScript font can be used, +but constant width fonts yield the best results. +The default font is Courier. +.RI ( postdaisy, +.IR postprint, +and +.IR posttek +only) +.TP +.BI \-f +Flip the sense of the bits in +.I files +before printing the bitmaps. +.RI ( postdmd +only) +.PP +In addition, three options allow the insertion of arbitrary PostScript +at controlled points in the translation process: +.TP \n(xxu +.BI \-C file +Copy +.I file +to the output file. +.I File +follows the prologue but +precedes any job initialization commands. +.I File +becomes part of the job's global environment +and must contain legitimate PostScript commands. +.TP +.BI \-P string +Like +.BR -C , +using a +.I string +instead of the contents of a file. +.TP +.BI \-R action +Requests special +.I action +(e.g. manualfeed) on a per page or global basis. +The +.I action +string has the general form +.IB request : page : file, +from which +.BI : page : file +or +.B : file +can be omitted. +An omitted or 0 page number +applies to all pages. +If file is omitted the request +lookup is done in +.FR /usr/lib/postscript/ps.requests . +The collection of recognized requests can be modified or extended +by changing this file. +Multiple occurrences of the +.B \-R +option behave as expected. +.SH FILES +.TF /usr/lib/font/devpost/charlib/* +.TP +.F /usr/lib/font/devpost/*.out +.TP +.F /usr/lib/font/devpost/charlib/* +.TP +.F /usr/lib/postscript/*.ps +default prologues +.TP +.F /usr/lib/tmac/tmac.pictures +.I troff +macros for PostScript +.SH SEE ALSO +.IR lp (1), +.IR postio (8) +.SH DIAGNOSTICS +Exit status 2 +usually means a syntax error in some input file. +.SH BUGS +Output files +will often violate Adobe's +file structuring conventions. +Pipe the output of +.I dpost +through +.I postreverse +to produce a minimally conforming PostScript file. +.PP +Although +.I dpost +can handle files formatted for any +.IR troff +device, emulation is expensive and +can easily double the print time and the size of the output file. +.PP +No attempt has been made to implement the character sets +or fonts available on all devices supported by +.I troff. +Missing characters are replaced by white space; +unrecognized fonts are replaced by one of the Times fonts. +.PP +.I Dpost +requires an +.B x res +command before the first +.B x init +and any file data. diff --git a/static/v10/man8/privserv.8 b/static/v10/man8/privserv.8 new file mode 100644 index 00000000..8029ddb4 --- /dev/null +++ b/static/v10/man8/privserv.8 @@ -0,0 +1,60 @@ +.TH PRIVSERV 8 +.SH NAME +privserv \- privilege server +.SH SYNOPSIS +.B lmask nuxl /etc/privserv +[ +.I option ... +] +.SH DESCRIPTION +.I Privserv +is the keeper and interpreter of the +.IR privs (5) +file. +.I Priv (1) +calls on +.I privserv +to hand out privileges in accordance with the rules given in +.I privs. +.I Privserv +is a permanent process, normally started by the boot script +.IR rc (8). +It receives service requests through the mounted pipe +.FR /cs/priv . +The options are +.TP +.BI -p " name +The file name of the server, +.B /etc/privserv +by default +(used to reinvoke the priv server when the +.IR privs (5) +file is modified by a +.B PRIVEDIT +request.) +.TP +.BI -m " mountpt +The file system mount point for privilege service, +.F /cs/priv +by default. +.TP +.BI -l " logfile +The file in which to record logging information, +.F /usr/adm/privlog +by default. +.TP +.BI -f " privs +The data base of privileges, +.F /etc/privs +by default. +Unless +.I privs +is itself a privileged file, +.I privserv +will not actually grant the privileges there specified. +.SH FILES +.F /etc/privs +.br +.F /cs/priv +.SH SEE ALSO +.IR priv (1) diff --git a/static/v10/man8/ps.8 b/static/v10/man8/ps.8 new file mode 100644 index 00000000..fcab9ac7 --- /dev/null +++ b/static/v10/man8/ps.8 @@ -0,0 +1,77 @@ +.pa 1 +.he 'PS (VIII)'1/20/73'PS (VIII)' +.ti 0 +NAME ps -- process status +.sp +.ti 0 +SYNOPSIS /usr/adm/ps [ -xlt____ ] +.sp +.ti 0 +DESCRIPTION +.br +.in 8 +ps__ +prints certain facts about active +processes. +The information is columnar and consists of: + +.in +3 +The (numerical) ID of the user associated +with the process; + +The last character of the control typewriter of the process +or "x" if there is no control typewriter; +"x" lines are suppressed unless the "x" option +is given. + +The number of 512-byte disk blocks holding the core +image of the process; + +The process's unique ID (only with "l" option) + +The number of hours (mod 100) and minutes of system, disk, and +user-process time accumulated by the process and +all its terminated descendants (only with "t" option) + +An educated guess as to the command line which caused the +process to be created. + +.in -3 +Some caveats: + +The guess as to the command name and arguments is obtained by examining +the process's stack. +The process is entitled to destroy this information. +Also, only processes whose core images are on disk have +visible names. +The ps__ command in particular +does not, nor does any other process which happens to +be in core at the same time. +ps__ tries to overcome this limitation by spawning +a subprocess designed to take up the other core +slot, and is usually successful. +Because ps__ examines a dynamically changing data structure, +it can produce incorrect results, for example if +a process's core image moves between the time +ps__ gets its disk address and reads its stack. + +Besides its utility for simple spying, +ps__ is the only plausible +way to find the process number of someone you are trying +to kill (VIII). +.sp +.in 16 +.ti 0 +FILES /dev/rf0, +/sys/sys/unix (to get magic numbers). +.sp +.ti 0 +SEE ALSO kill (VIII) +.sp +.ti 0 +DIAGNOSTICS "Bad RF", if +a bad swap address turns up; +various missing-file diagnostics. +.sp +.ti 0 +BUGS As described. diff --git a/static/v10/man8/pstat.8 b/static/v10/man8/pstat.8 new file mode 100644 index 00000000..61942bbf --- /dev/null +++ b/static/v10/man8/pstat.8 @@ -0,0 +1,418 @@ +.TH PSTAT 8 +.CT 1 sa_mortals +.SH NAME +pstat \- print system facts +.SH SYNOPSIS +.B /etc/pstat +[ +.B \-afipstuxT +] +[ +.I suboptions +] +[ +.I file +] +[ +.I namelist +] +.SH DESCRIPTION +.I Pstat +interprets the contents of certain system tables. +If +.I file +is given, the tables are sought there, otherwise +in +.FR /dev/kmem . +The required namelist is taken from +.IR namelist , +default +.FR /unix . +Options are +.TP +.B -a +Under +.BR -p , +describe all process slots rather than just active ones. +.TP +.B -i +Print the inode table with the these headings: +.RS +.PD 0 +.TF SIGNAL +.TP +.B LOC +The core location of this table entry. +.TP +.B FLAGS +Miscellaneous state variables encoded thus: +.RS +.TP +.B L +locked +.TP +.B U +modified time +.RI ( filsys (5)) +must be corrected +.TP +.B A +access time must be corrected +.TP +.B O +file was opened +.TP +.B W +wanted by another process +.RB ( L +flag is on) +.TP +.B T +contains an active text +.RE +.TP +.B CNT +Number of active references to this inode. +.TP +.B FS +File system type, see +.IR fmount (2). +.TP +.B DEVICE +Device number of file system in which +this inode resides. +.TP +.B INO +I-number within the file system. +.TP +.B MODE +Mode, see +.IR stat (2). +.TP +.B NLN +Number of links to this inode. +.TP +.B UID +Userid of owner. +.TP +.B SPTR +Core location of corresponding stream header, +0 if this is not a stream. +.TP +.B SIZ/DEV +Number of bytes in an ordinary file, or +device number of a special file. +.TP +.B MROOT +Core location of root inode +of file system mounted here, +0 if none. +.PD +.RE +.TP 0 +.B -x +Print the text table with these headings: +.PD 0 +.RS +.TF SIGNAL +.TP +.B LOC +The core location of this table entry. +.TP +.B FLAGS +Miscellaneous state variables encoded thus: +.RS +.TP +.B P +resulted from demand-page-from-inode exec format, see +.IR exec (2) +.TP +.B T +traced through +.IR proc (4) +.TP +.B W +text not yet written to swap device +.TP +.B L +loading in progress +.TP +.B K +locked +.TP +.B w +wanted +.RB ( L +flag is on) +.RE +.TP +.B DADDR +Disk address in swap, in multiples of 512 bytes. +.TP +.B CADDR +Head of a linked list of loaded processes using this text segment. +.TP +.B RSS +Size of physical memory occupied +by text segment, +in multiples of 512 bytes. +.TP +.B SIZE +Size of text segment, in multiples of 512 bytes. +.TP +.B IPTR +Core location of corresponding inode. +.TP +.B CNT +Number of processes using this text segment. +.TP +.B CCNT +Number of processes in core using this text segment. +.PD +.RE +.TP 0 +.B -p +Print process table for active processes with these headings: +.RS +.TP +.B LOC +The core location of this table entry. +.PD 0 +.TF SIGNAL +.TP +.B S +Run state encoded thus: +.RS +.TP +.B 0 +no process +.TP +.B 1 +waiting for some event +.TP +.B 3 +runnable +.TP +.B 4 +being created +.TP +.B 5 +being terminated +.TP +.B 6 +stopped under trace +.RE +.TP +.B F +Miscellaneous state variables, or-ed together (hexadecimal): +.RS +.TF SIGNAL +.TP +.B 0000001 +loaded in memory +.TP +.B 0000002 +special system process (swapper or pager) +.TP +.B 0000004 +being swapped out +.TP +.B 0000008 +obscure swapout flag +.TP +.B 0000010 +traced +.TP +.B 0000020 +used in tracing +.TP +.B 0000040 +locked in core +.TP +.B 0000080 +waiting for pagein +.TP +.B 0000100 +prevented from swapping during +.IR fork (2) +.TP +.B 0000200 +gathering pages for raw i/o +.TP +.B 0000400 +exiting +.TP +.B 0008000 +associated text is demand paged from file +.TP +.B 0030000 +anomalous paging behaviour expected, +see +.IR vlimit +in +.IR deprecated (2) +.TP +.B 0040000 +in a sleep which will time out +.TP +.B 0400000 +in +.IR select (2) +.TP +.B 0800000 +traced via +.IR proc (4) +.TP +.B 1000000 +i/o via +.IR proc +in progress +.TP +.B 2000000 +stop on exec +.TP +.B 4000000 +wanted by +.I proc +after pagein +.RE +.TF SIGNAL +.TP +.B ADDR +The core location of the page table entry for the first page of the `u-area.' +.TP +.B PRI +Scheduling priority; +smaller numbers run first. +.TP +.B SIG +Signals received; signals 1-32 coded in bits 0-31. +.TP +.B UID +Real userid. +.TP +.B SLP +Time blocked in seconds; +times over 127 coded as 127. +.TP +.B TIM +Time resident in seconds; +times over 127 coded as 127. +.TP +.B CPU +Weighted integral of CPU time, for scheduler. +.TP +.B NI +Nice level, +see +.IR nice (2). +.TP +.B PGRP +Process group number. +.TP +.B PID +Process ID number. +.TP +.B PPID +Process ID of parent process. +.TP +.B RSS +Number of physical page frames allocated +to this process. +.TP +.B SRSS +RSS at last swap, 0 if never swapped. +.TP +.B SIZE +Virtual size of process image (data+stack) in multiples of 512 bytes. +.TP +.B WCHAN +Event address if waiting. +.TP +.B LINK +Pointer to next entry in list of runnable processes. +.TP +.B TEXTP +If text is pure, pointer to location of text table entry. +.TP +.B CLKT +Countdown for +.IR alarm (2) +measured in seconds. +.PD +.RE +.TP 0 +.B -u +Print information about a user process; +the next argument is its address as given +by +.L ADDR +under +.B -p +above. +The process must be in main memory, or the file used can +be a core image +.RI ( core (5)) +and the address 0. +.TP +.B -f +Print the open file table with these headings: +.PD0 +.RS +.TF SIGNAL +.TP +.B LOC +The core location of this table entry. +.PD 0 +.TP +.B FLG +Miscellaneous state variables encoded thus: +.RS +.TP +.B R +open for reading +.TP +.B W +open for writing +.RE +.TP +.B CNT +Number of processes that know this open file. +.TP +.B INO +The core location of the inode table entry for this file. +.TP +.B OFFS +The file offset, see +.IR lseek (2). +.PD +.RE +.TP 0 +.B -s +Print information about swap space usage: +the number of 1024 byte pages used +and free, +and the number of pages belonging +to text images. +.TP +.B -T +Print the number of used and free slots in several system tables; +useful to see if they are nearly full. +.SH FILES +.TF /dev/kmem +.TP +.F /unix +namelist +.TP +.F /dev/kmem +default source of tables +.SH SEE ALSO +.IR ps (1), +.IR stat (2), +.IR filsys (5) +.br +M. J. Bach, +.IR "The Design of the UNIX Operating System" , +Prentice-Hall, 1986 +.SH BUGS +This program is never up to date. diff --git a/static/v10/man8/pwserv.8 b/static/v10/man8/pwserv.8 new file mode 100644 index 00000000..bb7fb90e --- /dev/null +++ b/static/v10/man8/pwserv.8 @@ -0,0 +1,77 @@ +.TH PWSERV 8 +.CT 1 sa_auto +.SH NAME +pwserv \- password verification service +.SH SYNOPSIS +.B /etc/pwserv +.SH DESCRIPTION +.I Pwserv, +normally started from +.IR rc (8), +handles password verification requests initiated by (say) +.IR pwquery (3) +through the conventional +process mount point +.FR /cs/pw . +When a request is made a file descriptor (called the `line' below) +is passed to +.I pwserv +together with a user name and an optional parameter string. +Normally, +.I pwserv +writes a prompt on the line, reads a reply, and returns +an indication of success to the invoking client. +Valid passwords are taken from the file +.FR /etc/pwfile , +which lists for each user an ordinary (encrypted, +.IR crypt (3)-style) +password and an +SNK (Secure Net Key) challenge-response key. +Before prompting, an +.B FIOPX +IO control is attempted to render the line to the end user private; +see +.IR pex (4). +If this succeeds +either a classical or an Atalla password is accepted. +If the pex bid fails, the prompt warns that the line +is not private, and only an SNK response is accepted. +.PP +In the pexed case the prompt looks like +.B Password(pjw:31416): +and in the unpexed case like +.B "Password(TAPPED LINE:01492): +The five digit string after the colon is the Atalla challenge string. +Only the first five digits of the Atalla response string are significant. +Hex digits in the response must be typed in lower case. +.PP +Possible values of the optional parameter string are +.TP +.B pex +(specified by opening the server with +.B ipcopen("/cs/pw!pex") ) +Accept passwords only if the +.B FIOPX +succeeds. +.PP +When the line's stream identifier asserts previous confirmation +of the same password, +.I pwserv +answers affirmatively without demanding a password; see +.IR session (1) +and +.IR src (5). +.SH FILES +.nf +.F /etc/pwserv +.F /etc/pwfile +.fi +.SH "SEE ALSO" +.IR pwquery (3), +.IR ipc (3), +.IR pex (4), +.IR stream (4), +.IR pwfile (5), +.IR passwd (1) +.SH BUGS +Jammable. diff --git a/static/v10/man8/quot.8 b/static/v10/man8/quot.8 new file mode 100644 index 00000000..dca6bbad --- /dev/null +++ b/static/v10/man8/quot.8 @@ -0,0 +1,135 @@ +.TH QUOT 8 +.CT 1 sa_mortals +.SH NAME +quot, findo \- file system usage and hogs +.SH SYNOPSIS +.B /etc/quot +[ +.I option ... +] +[ +.I filesystem +] +.PP +.BI findo +[ +.B -f +] +[ +.B -n +] +[ +.B -u +.I userid +] +.I device mount-directory +.SH DESCRIPTION +.I Quot +prints the number of blocks in the named +.I filesystem +device currently owned by each user. +If no +.I filesystem +is named, +.F /dev/usr +is assumed. +The options are: +.TP +.B -n +Use as in the example below to list all files and owners. +.TP +.B -c +Print three columns giving file size in blocks, number of +files of that size, and cumulative total of blocks +in files of that size or smaller. +.TP +.B -f +Print count of number of files as well as space owned by each user. +.TP +.B -b +Print space-time product in block-years in addition to space owned by +each user. +.PP +.I Findo +discovers files you might want to delete on the +given block +.I device, +which must be mounted on the given directory. +It lists, on the standard output, the +sizes, ages in days, and names of files +with any of the following characteristics: +.IP - +.IR Troff (1) +output files older than 24 hours. +The names are marked +.L troff: +in the output. +.IP - +Week-old files named +.BR core , +.BR a.out , +.BR mon.out , +.BR .pilog , +.BR junk* , +.BR temp* , +.BR ed.hup , +.BR qed.hup:* , +.BR jim.recover , +.BR sam.save , +.BR sam.err , +.BR ~~sam~~ , +.BR [a-z] , +.BR dead.letter , +.BR foo[0-9]* , +.BR rst[0-9]+ , +.BR .jx* , +.BR *.dvi , +and files whose names +resemble +.IR apnews (7) +spool entries. +.IP - +Files over a month old named +.BR *.o . +The names are marked +.LR old: . +.IP - +Files owned by users selected with option +.BR -u ; +the names are marked +.LR user: . +.PP +The options are +.TP +.B -f +List files owned by users not in the password file. +.TP +.BI -u " userid +List files over 2 days old owned by the user with the given numeric +.I userid. +.TP +.B -n +List files of any age owned by the specified users. +.SH EXAMPLES +.TP +.L +ncheck filesystem | sort -n | quot -n filesystem +List all files and their owners. +.SH FILES +.F /etc/passwd +to get user names +.SH "SEE ALSO" +.IR ls (1), +.IR du (1), +.IR icheck (8), +.IR fstab (5) +.SH BUGS +.I Quot +counts holes in files as if they actually occupied space. +.br +Patterns specifying the names and ages are compiled into +.I findo. +.br +.I Findo's +age distinction for files owned by a specific user is a +historical dreg. diff --git a/static/v10/man8/rarepl.8 b/static/v10/man8/rarepl.8 new file mode 100644 index 00000000..5d9fabef --- /dev/null +++ b/static/v10/man8/rarepl.8 @@ -0,0 +1,115 @@ +.TH RAREPL 8 +.CT 1 sa_nonmortals +.SH NAME +rarepl, rarct \- replace bad blocks on MSCP disks +.SH SYNOPSIS +.B /etc/rarct +[ +.B -c +] +[ +.B -h +] +.I special ... +.PP +.B /etc/rarepl +.I special +.I lbn ... +.SH DESCRIPTION +.I Rarct +prints status information +about MSCP disk drives +like the RA60 and RA81. +Normally the replacement table (RCT) +is listed, +as lines of the form +.IP +.IB rbn : \0flags : \0lbn +.PP +where +.I rbn +is the replacement block number, +.I lbn +is the logical block number +replaced by +.IR rbn , +and +.I flags +are constructed from the following bits: +.TP +.PD 0 +.B 01 +alternate (not primary) replacement block +.TP +.B 02 +normal, allocated replacement block +.TP +.B 04 +this replacement block is bad +.TP +.B 010 +this replacement block does not exist +.PD +.PP +Entries whose +.I flags +are zero, +indicating a good, +unused replacement block, +are not listed. +.PP +The options suppress the RCT listing and perform other functions: +.TP +.B -h +Print some header data +from the first block of the RCT. +The system does not use this information. +.TP +.B -c +Print geometry information for the drive. +.PP +.I Rarepl +causes logical block +.I lbn +on device +.I dev +to be marked as bad +and replaced. +The nearest available replacement block +is used. +The contents of +.I lbn +are copied into the replacement block if possible; +if +.I lbn +is unreadable, +the replacement block +is initialized with zeros. +.PP +Both programs +work only +on the raw devices. +.I Rarepl +should be used only +on a device +which covers the entire drive +(usually partition 7). +.SH SEE ALSO +.IR ra (4), +.IR smash (8) +.SH BUGS +There are various controller- and drive-dependent anomalies. +Some controllers, +like the RQDX3, +report an RCT +but don't allow forwarding. +On many controllers, +the RCT exists +only so programs in the host can look at it; +the controller ignores its contents. +There is no way to read the controller's `real' forwarding data, +only a way to set it for a particular block. +Hence if the RCT is corrupted, +the disk may still be used, +but must be reformatted +before additional bad blocks are remapped. diff --git a/static/v10/man8/rc.8 b/static/v10/man8/rc.8 new file mode 100644 index 00000000..f46cff12 --- /dev/null +++ b/static/v10/man8/rc.8 @@ -0,0 +1,77 @@ +.TH RC 8 +.CT 1 sa_auto +.SH NAME +rc \- boot script +.SH SYNOPSIS +.B /etc/rc +.SH DESCRIPTION +.I Rc +is the command script +invoked by +.IR init (8) +to control reboots. +During an automatic reboot, +.I rc +is invoked with the argument +.BR autoboot ; +typically this invokes +.L /etc/fsck -p +to repair minor filesystem inconsistencies. +If +.I rc +exits with a successful status, +.I init +proceeds to multi-user mode. +.PP +When the system enters multi-user mode, +either during an auto-reboot +or after the single-user shell terminates, +.I rc +is invoked without arguments. +This usually causes it to +mount filesystems, +start daemons, +clear +.FR /tmp , +and perform other housekeeping. +.PP +If any call to +.I rc +returns a nonzero status, +.I init +reverts to single-user mode. +.SH EXAMPLES +A typical +.I rc +script: +.PP +.EX +date +case $1 in +autoboot) + echo Autoboot: + /etc/fsck -p || {echo "error in reboot"; exit 1} +esac +/etc/ldpcs /etc/pcs750.bin +>/etc/mtab +/etc/mount -a +/etc/savecore /tmp/dump /dev/ra11 +/etc/swapon -a +trap "" 1 2 3 +/etc/update +/etc/cron & +rm -f /tmp/* +/usr/lib/asd/rmlocks +date >> /usr/adm/lastboot +/etc/accton /tmp/acct > /tmp/acct +/usr/ipc/mgrs/svcmgr +/etc/kdiload +/usr/ipc/mgrs/dkhup; sleep 10 +/usr/ipc/mgrs/dkmgr +/usr/netb/setup.go +/usr/net/face.go +wwv -s +.EE +.SH SEE ALSO +.IR init (8), +.IR reboot (8) diff --git a/static/v10/man8/reboot.8 b/static/v10/man8/reboot.8 new file mode 100644 index 00000000..50e1c453 --- /dev/null +++ b/static/v10/man8/reboot.8 @@ -0,0 +1,127 @@ +.TH REBOOT 8 +.CT 1 sa_auto +.SH NAME +reboot \- bootstrapping procedures +.SH DESCRIPTION +.PP +Here are some recipes for booting and crashing the operating system +on VAXes. +.SS Rebooting a running system +The preferred way to reboot is to log in on the console as super-user, +invoke +.B kill 1 +to take the system to single user, +unmount file systems with +.B /etc/umount -a +and halt and restart the system +as described below under `Console boots.' +.SS Power fail and crash recovery +The system will reboot itself at power-up or after crashes if +auto-boot is enabled on the machine front panel +or in the console software. +If auto-restart is enabled, +the system will first attempt to save a copy of physical memory +on a reserved piece of disk. +An automatic consistency check of the file systems is performed. +Unless this fails the system will resume multi-user operations. +.SS Console boots +Sync the disks if necessary and possible. +To recover hardware control of the console, type a +.RB control- P . +This will yield a +.L >>> +prompt from the VAX +console subsystem (sic). +The command +.IP +.B >>> H +.LP +will halt the CPU +(except on the 11/750, +where +.RB control- P +halts the CPU right away). +.PP +On MicroVAXes, +.RB control- P +doesn't work; +hit the +.SM BREAK +key instead. +.PP +To boot multi-user with an automatic file system check, +give the console command +.IP +.B >>> B +.LP +Commands to boot single-user vary. +On the VAX-11/750 and on MicroVAXes, +use +.IP +.B >>> B/3 +.LP +On the VAX-11/780 and VAX 8550 and 8700, +use +.IP +.B >>> B MAN +.LP +This will prompt with +.LR * +for the name of the file to boot. +The filename should be an executable image +in the root directory +of the filesystem at the beginning of the disk. +.SS System core images +If the system crashes +and auto-restart is enabled, +a copy of physical memory is written +to a reserved piece of disk. +To save a core image of a hung system, type on the console (after +.RB control- P +if necessary): +.IP +.EX +>>> S 80000010 +.EE +.PP +The system will write the core image, +then reboot automatically. +.PP +If the core image was written on +.LR /dev/ra11 , +the following incantation will print a stack traceback +from the time of the crash: +.IP +.EX +adb /unix /dev/ra11 +$<crash +$c +.EE +.PP +To save disk space, +the core image is sometimes overlaid on part of the swap area, +where normal system operation will soon overwrite it. +.IR Savecore (8) +will copy the core image +to an ordinary disk file. +.SH FILES +.TP +.F /unix +default system binary +.SH "SEE ALSO" +.IR fsck (8), +.IR init (8), +.IR rc (8), +.IR savecore (8) +.SH BUGS +Older boot programs with different syntax are still around in a few places, +especially on machines with Emulex UNIBUS disk controllers, +for which silly boot ROMs are common. +.PP +There are commands +.B /etc/reboot +and +.B /etc/halt +which attempt to reboot and halt the system; +their function is indeterminate +and likely to change. diff --git a/static/v10/man8/recnews.8 b/static/v10/man8/recnews.8 new file mode 100644 index 00000000..59a707ef --- /dev/null +++ b/static/v10/man8/recnews.8 @@ -0,0 +1,24 @@ +.TH RECNEWS 8 +.SH NAME +recnews \- receive unprocessed articles via mail +.SH SYNOPSIS +.BR /usr/lib/news/recnews " [ " +.IR newsgroup " [ " sender " ] ] " +.SH DESCRIPTION +.I Recnews +reads a letter from the standard input; determines the article title, +sender, and newsgroup; and gives the body to inews with the right +arguments for insertion. +.PP +If +.I newsgroup +is omitted, the to line of the letter will be used. If +.I sender +is omitted, the sender will be determined from the from line of the letter. +The title is determined from the subject line. +.SH SEE ALSO +inews(1), +uurec(8), +sendnews(8), +readnews(1), +checknews(1) diff --git a/static/v10/man8/reloc.8 b/static/v10/man8/reloc.8 new file mode 100644 index 00000000..a34054c6 --- /dev/null +++ b/static/v10/man8/reloc.8 @@ -0,0 +1,45 @@ +.th RELOC VIII 2/7/73 +.sh NAME +reloc \*- relocate object files +.sh SYNOPSIS +.bd reloc +file octal [ +.bd \*- +] +.sh DESCRIPTION +.it Reloc +modifies the named object program file so that it will operate correctly +at a different core origin than the one for which +it was assembled or loaded. +.s3 +The new core origin is the old origin +increased by +the given +.it octal +number (or decreased if the number has a `\*-' sign). +.s3 +If the object file was generated by +.it ld, +the +.bd \*-r +and +.bd \*-d +options must have been given to +preserve the relocation information and define any common symbols +in the file. +.s3 +If the optional last argument is given, then any +.it setd +instruction at the start of the file +will be replaced by a no-op. +.s3 +The purpose of this command is to simplify the +preparation of object programs for systems +which have no relocation hardware. +It is hard to imagine a situation +in which it would be useful to attempt directly to execute +a program treated by +.it reloc. +.sh "SEE ALSO" +as(I), ld(I), a.out(V) +.sh BUGS diff --git a/static/v10/man8/renice.8 b/static/v10/man8/renice.8 new file mode 100644 index 00000000..0f08f491 --- /dev/null +++ b/static/v10/man8/renice.8 @@ -0,0 +1,31 @@ +.TH RENICE 8 +.CT 1 sa_nonmortals +.SH NAME +renice \- change priority of running process +.SH SYNOPSIS +.B /etc/renice +[ +.BI - priority +] +.I pid ... +.SH DESCRIPTION +.I Renice +increments the scheduling priority +of the processes with the named +.I process-ids +by +.IR pri . +The default +.IR pri +is 19, +making the process least likely to run. +.PP +Only the owner of the process +or the super-user may change the priority. +Only the super-user may use negative increments. +.SH FILES +.BI /proc +.SH SEE ALSO +.IR nice (1), +.IR nice (2), +.IR proc (4) diff --git a/static/v10/man8/restor.8 b/static/v10/man8/restor.8 new file mode 100644 index 00000000..359164a1 --- /dev/null +++ b/static/v10/man8/restor.8 @@ -0,0 +1,112 @@ +.th RESTOR VIII 11/24/73 +.sh NAME +restor \*- incremental file system restore +.sh SYNOPSIS +.bd restor +key [ arguments ] +.sh DESCRIPTION +.it Restor +is used to read magtapes dumped with the +.it dump +command. +The +.it key +argument specifies what is to be done. +.it Key +is a character from the set +.bd trxw. +.s3 +.lp +5 3 +\fBt\fR The date that the tape was made and the date that +was specified in the +.it dump +command are printed. +A list of all of the i-numbers on the tape +are also given. +.s3 +.lp +5 3 +\fBr\fR The tape +is read and loaded into the file system +specified in +.it arguments. +This should not be done lightly (see below). +.s3 +.lp +5 3 +\fBx\fR Each file on the +tape is individually extracted into +a file whose name is the file's i-number. +If +there are +.it arguments, +they are interpreted as i-numbers and only they are +extracted. +.s3 +.lp +5 3 +\fBw\fR In conjunction with the +.bd x +option, +before each file is extracted, +its i-number is typed out. +To extract this file, +you must respond with +.bd y. +.s3 +.i0 +The +.bd r +option should only be used to restore +a complete dump tape onto a clear file system +or to restore an incremental dump tape onto this. +Thus +.s3 + /etc/mkfs /dev/rp0 40600 +.br + restor r /dev/rp0 +.s3 +is a typical sequence to restore a complete dump. +Another +.it restor +can be done to get an incremental dump +in on top of this. +.s3 +A +.it dump +followed by a +.it mkfs +and a +.it restor +is used to +change the size of a file system. +.sh FILES +/dev/mt0 +.sh "SEE ALSO" +dump, mkfs, check, clri (VIII) +.sh DIAGNOSTICS +There are various diagnostics +involved with reading the tape and writing the disk. +There are also diagnostics if the i-list or the free list +of the file system is not large enough to hold the dump. +.sh BUGS +There is redundant information on the tape +that could be used in case of tape reading problems. +Unfortunately, +.it restor's +approach is to exit if anything is wrong. +.s3 +Files that have been deleted are +not removed when incremental tapes are loaded. +It will be necessary to +.it check +the restored file system and +.it clri +any files that show up with +a 201 delta diagnostic. +.s3 +The current version of +.it restor +does not free space occupied +by files that are overwritten. +Thus a +.it check +will have to be performed to reclain the missing +space. diff --git a/static/v10/man8/route.8 b/static/v10/man8/route.8 new file mode 100644 index 00000000..1f99f156 --- /dev/null +++ b/static/v10/man8/route.8 @@ -0,0 +1,95 @@ +.TH ROUTE 8 +.CT 1 sa_auto +.SH NAME +route, routed, remroutes \- IP gateway routing +.SH SYNOPSIS +.B /usr/ipc/mgrs/routed +[ +.B -v +] [ +.B -t +] [ +.B -q +] [ +.BI - hops +] [ +.I addr ... +] +.br +.B route add +.I "dest gateway" +.br +.B route delete +.I "dest" +.B +.br +.B /etc/remroutes +.br +.SH DESCRIPTION +.I Routed +runs the 4BSD RIP routing protocol on an IP network. +It broadcasts routing information to the network at large, +listens for routing messages from elsewhere, +and informs the system of the routes it receives. +.PP +The options are +.TP +.BI \-v +Log transmitted messages on the standard output. +.TP +.BI \-t +Log received messages on the standard output. +.TP +.BI \-q +Accept routing information but do not broadcast any. +.TP +.BI \- hops +Add +.I hops +(a decimal number) +to the hop count +when broadcasting routes. +.PD +.LP +Information received for any named +.I addrs +is ignored. +.PP +.I Routed +is usually run without options on gateway machines, +and with the +.B -q +option on non-gateway machines. +.PP +.I Route +sets up specific routes, +to establish static routing +or to adjust that set up by +.IR routed . +The +.B add +command informs the system that +internet address +.I dest +may be reached through +internet address +.IR gateway ; +.B delete +removes any routing for +.IR dest . +The special +destination +.L * +represents the default routing: +.B route add * +.I gate +sets the default, +.B route delete * +removes any default. +.PP +.I Remroutes +removes all known routes. +.SH FILES +.F /usr/ipc/log/routed +.SH "SEE ALSO" +.IR ipconfig (8) diff --git a/static/v10/man8/sa.8 b/static/v10/man8/sa.8 new file mode 100644 index 00000000..45c77ec9 --- /dev/null +++ b/static/v10/man8/sa.8 @@ -0,0 +1,185 @@ +.TH SA 8 +.CT 1 sa_nonmortals +.SH NAME +sa, accton \- system accounting +.SH SYNOPSIS +.B /etc/sa +[ +.B -abcdDfgijkKlnrstuv +] +[ +.B -e prefix +] +[ +.I file +] +.PP +.B /etc/accton +[ +.I file +] +.SH DESCRIPTION +With an argument naming an existing +.I file, +.I accton +causes system accounting information for +every process executed to be placed at the end of the file. +If no argument is given, accounting is turned off. +.PP +.I Sa +reports on, cleans up, and generally maintains +accounting files. +.PP +.I Sa +is able to condense +the information in +.F /usr/adm/acct +into a summary file +.F /usr/adm/savacct +which contains a count of the +number of times each command was called and the time resources +consumed. +This condensation is desirable because on a large system +.F /usr/adm/acct +can grow by 10000 blocks per day. +The summary file is normally read before the accounting file, +so the reports include all available information. +.PP +If a file name is given as the last argument, +that file will be treated +as the accounting file; +.F /usr/adm/acct +is the default. +.PP +Output fields are labeled: +.L cpu +for the sum of user and system times +(in minutes), +.L re +for real time (also in minutes), +.L k +for cpu-time averaged core usage (in 1K units), +.L avio +for average number of IO operations per execution. +With options fields labelled +.L tio +for total IO operations, +.L k*sec +for cpu storage integral (kilo-core seconds), +.L u +and +.L s +for user and system cpu time alone (both in minutes) will sometimes +appear. +.PP +There are zillions of options: +.TP +.B a +Place all command names containing unprintable characters +and those used only once under the name +.LR ***other . +.TP +.B b +Sort output by sum of user and system time divided by number of +calls. +Default sort is by sum of user and system times. +.TP +.B c +Besides total user, system, and real time for each command print percentage +of total time over all commands. +.TP +.B d +Sort by average number of disk IO operations. +.TP +.B D +Sort by total number of disk IO operations. +.TP +.B e +Set the prefix for accounting file names to the next argument +.RB ( /usr/adm/ +is the default). +.TP +.B f +Assume answer +.L y +for option +.BR -v . +.TP +.B g +Ignore +.BR /usr/adm/acct . +Useful for processing only +.L savacct +and +.LR usracct . +.TP +.B i +Don't read in summary file. +.TP +.B j +Instead of total minutes time for each category, +give seconds per call. +.TP +.B k +Sort by cpu-time average memory usage. +.TP +.B K +Print and sort by cpu-storage integral. +.TP +.B l +Separate system and user time; normally they are combined. +.TP +.B m +(money) Print number of processes and number of CPU minutes for each user. +.TP +.B n +Sort by number of calls. +.TP +.B r +Reverse order of sort. +.TP +.B s +Merge accounting file into summary file +.F /usr/adm/savacct +when done. +.TP +.B t +For each command report ratio of real time to the sum of user and +system times. +.TP +.B u +Superseding all other flags, +print for each command in the accounting file the +userid and command name. +.TP +.B v +Followed by a number +.I n, +types the name of +each command used +.I n +times or fewer. +Await a reply from the terminal; +if it begins with +.LR y , +add the command to +the category +.LR **junk** . +This is used to strip out garbage. +.SH FILES +.TF /usr/adm/usracct +.TP +.F /usr/adm/acct +raw accounting +.TP +.F /usr/adm/savacct +summary +.TP +.F /usr/adm/usracct +per-user summary +.SH "SEE ALSO" +.IR ac (8), +.IR acct (2) +.SH BUGS +.I Sa +needs more options. diff --git a/static/v10/man8/salv.8 b/static/v10/man8/salv.8 new file mode 100644 index 00000000..cf9d808f --- /dev/null +++ b/static/v10/man8/salv.8 @@ -0,0 +1,86 @@ +.pa 1 +.he 'SALV (VIII)'1/20/73'SALV (VIII)' +.ti 0 +NAME salv -- file system salvage +.sp +.ti 0 +SYNOPSIS /etc/salv_________ filesystem [ -akfs_____ ] +.sp +.ti 0 +DESCRIPTION +.br +.in 8 +salv____ +will place a given file system +in a consistent state with +almost no loss of information. +This is the first step in putting things +together after a bad crash. +Salv performs the following functions: +.sp +.in +3 +A valid free list is constructed. + +.in -3 +The previous step is always performed; the following steps +are performed only if the "a" option is given. +If the file system's only defect is missing blocks, +"a" should not be specified. +.in +3 +.sp +All bad pointers in the file system are zeroed. +.sp +All duplicate pointers to the same block +are resolved by changing one of the pointers +to point at a new block containing a copy of the data. +.sp +Inodes (not directory entries) for special files +are generated (mode 16). + +Files whose size is too large for the number of +blocks they contain (after bad pointers are zeroed) +have their size revised downward. + +.in -3 +The file system should be unmounted while it is +being salvaged. +In cases of extreme need the permanently mounted +file system may be salvaged; in such a case +the system must be rebooted before it +has a chance to write out the old, bad super-block. + +The "k", "f", and "s" options +tell salv what magic numbers to use to generate +the size of the free list and the i-node map. +"k" is default (RK disk); "f" is RF; "s" is RK with +swap space on it. +If salv is to be used away +from the mother system its code should be cheked +to verify the numbers. +.sp +After a salv, files may be safely created +and removed without causing +more trouble. +If the "a" option had to be used, +a dcheck (VIII) should be done to find the degree +of the damage to the hierarchy. +.sp +.in 16 +.ti 0 +FILES /dev/rk0 +.sp +.ti 0 +SEE ALSO check(I), ds(I) +.sp +.ti 0 +DIAGNOSTICS -- +.sp +.ti 0 +BUGS In +only one (known) way does salv____ destroy information: +if some random block appears to be an indirect block +for a file, +all "bad pointers" (for example, ASCII text) in it +will be zeroed. If +the block also appears in another file, it may be +scribbled on before it is copied. diff --git a/static/v10/man8/savecore.8 b/static/v10/man8/savecore.8 new file mode 100644 index 00000000..37ace4af --- /dev/null +++ b/static/v10/man8/savecore.8 @@ -0,0 +1,83 @@ +.TH SAVECORE 8 +.CT 1 sa_auto +.SH NAME +savecore \- save a core image of the operating system +.SH SYNOPSIS +.B /etc/savecore +.I target +.I dump +.SH DESCRIPTION +.I Savecore +copies the core image +saved after an operating system crash +to an ordinary file. +This is worth doing +so that the crash image will not be overwritten +immediately by another crash, +or sometimes because the crash image was written +in a place where normal system operation will overwrite it +(e.g. in the swap area). +.PP +The crash image is taken from +.I dump +and written to +.IR target . +If +.I target +exists and is a directory, +the image is copied to +a file in that directory +with the first nonexistent name +in the sequence +.BR "z.0 z.1 z.2 ..." ; +otherwise +.I target +is created or overwritten. +.PP +The crash image to be copied +is checked for a magic number +in a known location. +If the magic number is correct, +it is followed by the size of the image, +and the time it was written; +these numbers are printed +before the dump is copied. +If the magic number is wrong, +the image is not copied. +.I Savecore +overwrites the magic number in +.I dump +after a successful copy. +.PP +The program runs faster +if +.I dump +is the raw device. +.PP +For compatibility with an older program of the same name, +the +.I dump +argument may be omitted; +.I savecore +will noisily examine each device specified for swapping in +.IR fstab (5) +and each of several popular default swap devices +for a valid magic number. +The first device that looks right +is taken to be the crash image. +.PP +.I Savecore +is usually called when the system is booted, +from +.IR rc (8). +.SH EXAMPLE +.EX +/etc/savecore /tmp/dump /dev/rra11 +.EE +.SH SEE ALSO +.IR reboot (8) +.SH BUGS +The argument convention +(the file to be written comes first) +is unfortunate; +it stems from compatibility. diff --git a/static/v10/man8/scsish.8 b/static/v10/man8/scsish.8 new file mode 100644 index 00000000..b1c9b08a --- /dev/null +++ b/static/v10/man8/scsish.8 @@ -0,0 +1,222 @@ +.TH SCSISH 8 +.CT 1 sa_nonmortals +.SH NAME +scsish \- SCSI shell +.SH SYNOPSIS +.B /usr/lib/worm/scsish +.SH DESCRIPTION +.I Scsish +is a command interpreter for SCSI commands executed through +.B /dev/scsi +(see +.IR scsi (4)). +Many commands are applicable to more or less all SCSI devices; +some are specific to the SONY WDA-3000-10 optical disk jukebox. +Any details not found here are in the manual for the jukebox. +.PP +Typically commands are sent to a particular drive +(a number between 0 and 7 inclusive) +on a particular device +(normally a number between 0 and 5 inclusive). +Most commands take a drive parameter (a number). +The device number is set by the +.B id +command. +.PP +Occasionally, commands fail and will print the result of a +.B sense +command which is normally needed to clear the error status. +.PP +All input is in lower case and keywords and numbers are separated by white space. +Commands are separated by a newline or semicolon. +.SS "General SCSI Commands" +.TF "disk eject drive" +.TP +.BI capacity " drive" +Report the capacity of +.I drive +as +.BR "nblocks x blocksize" . +.TP +.BI "disk eject" " drive" +Eject the disk +(or other removable medium) +from +.IR drive . +.TP +.BI echo " number" +Print +.I number +on standard output. +.TP +.B help +Print a summary of the available commands. +.TP +.BI id " n" +Set the destination SCSI bus device number. +By default, it is 2 which is the normal device number for the SONY jukebox. +.TP +.BI inquiry " drive" +Print various bits of status about +.IR drive . +For example, +.IP +.EX +drive 2,0: WORM device, ' SONY WDA-3000-10 2.D' + disk,write protect,,,ready (0x9) +.EE +.IP +If +.I drive +is omitted, an inquiry is performed for drives 0 through 7. +.TP +.BI read " drive block" +Print the contents of the 1024 byte block at +.I block +on +.I drive +in hexadecimal. +.TP +.BI "read id" " drive" +Print the string starting at byte 42 in block 1 on +.IR drive . +This corresponds to the initial +.I vol_id +for +.IR worm (8) +disks. +.TP +.B reset +Attempt to reset the SCSI interface. +.TP +.BI sense " drive" +Print the sense data for +.IR drive . +Some of the interpretations of the sense bytes are idiosyncratic to SONY. +.TP +.BI "ext sense" " drive" +Print the extended sense data for +.IR drive . +Most of the interpretations of the extended sense bytes are idiosyncratic to SONY. +.TP +.BI sleep " n" +Sleep for +.I n +seconds. +.TP +.BI start " drive" +Start +.I drive +spinning. +.TP +.BI stop " drive" +Stop +.IR drive . +.TP +.BI test " drive" +Test unit ready for +.IR drive . +.PD +.SS "SONY Commands" +.TP +.BI alternate " drive" +Print the replacement block tables from the disk. +.TP +.BI media " drive blkno nblks" +Print a summary of the media quality in +.I drive +for the +.I nblks +blocks starting at block number +.IR blkno . +For example, a dirty disk can yield +.IP +.EX +drive 0: media check for 1000 blocks [0-999], upper drive +849 good, 1 unwritten, 147 <50% burst, 3 >96% burst, +.EE +.IP +Please report any instances of messages including +.B "rare error" +to the jukebox guru. +.PD +.TP +.BI "ext media" " drive blkno nblks" +A verbose form of the +.B media +command. +.PD +.SS "Jukebox Commands" +.TP +.B config +Print the configuration data for the jukebox. +.TP +.BI "rel" " drive shelf side" +Release the disk from +.I drive +to +.IR shelf . +The value of +.I side +indicates whether it should be inverted on the way +.RB ( b ) +or not +.RB ( a ). +If +.I shelf +and +.I side +are absent, +the disk is restored to its former shelf. +.PD0 +.TP +.BI "set" " shelf side drive" +Put the disk from +.I shelf +into +.IR drive . +The value of +.I side +indicates whether it should be inverted on the way +.RB ( b ) +or not +.RB ( a ). +.TP +.BI internal " n" +Execute various internal reports and diagnostics. +.B "internal -1" +with no argument will print a list of available diagnostics. +.TP +.BI "status" " drive" +Print the status for +.IR drive . +An absent +.I drive +is taken as 0. +As the status is for the jukebox as a whole, +the value of +.I drive +doesn't matter. +A sample status output shows the jukebox hides the mapping +of logical drive number and actual drive: +.IP +.EX +drive 0: ready,disk in LUN,power on,disk in drive 0, return shelf 2 +drive 1: not ready,no disk in LUN,power on,disk in shelf 0 +drive 2: not ready,no disk in LUN,power on,disk in shelf 0 +drive 3: ready,disk in LUN,power on,disk in drive 1, return shelf 0 +drive 4: not ready,no disk in LUN,power on,disk in shelf 0 +drive 5: not ready,no disk in LUN,power on,disk in shelf 0 +drive 6: not ready,no disk in LUN,power on,disk in shelf 0 +drive 7: not ready,no disk in LUN,power on,disk in shelf 0 +0: no disk +1: no disk +2: disk, +I/O shelf: no disk +carrier: disk shelf=0 +upper drive: disk, LUN=0 +lower drive: disk, LUN=3 +.EE +.SH "SEE ALSO" +.IR worm (8), +.IR scsi (4) diff --git a/static/v10/man8/sendcover.8 b/static/v10/man8/sendcover.8 new file mode 100644 index 00000000..04be2b38 --- /dev/null +++ b/static/v10/man8/sendcover.8 @@ -0,0 +1,28 @@ +.TH SENDCOVER 8 +.CT 1 writing_output +.SH NAME +sendcover \- send cover sheet to the library +.SH SYNOPSIS +.B sendcover +.I file ... +.SH DESCRIPTION +.I Sendcover +sends a document cover sheet to the +Bell Laboratories library for their document database. +It is invoked automatically as a byproduct of +running +.I troff -mcs. +.PP +The cover sheet is translated from the form of +.IR mcs (6) +to a form used in the library +and certain other protocol information is added. +The destination is not the same as that of +.IR docsubmit (1). +.SH FILES +.F /usr/lib/tmac/tmac.cs +.br +.F /usr/lib/tmac/cstrans +.SH "SEE ALSO" +.IR docsubmit (1), +.IR mcs (6) diff --git a/static/v10/man8/sendnews.8 b/static/v10/man8/sendnews.8 new file mode 100644 index 00000000..6aba6dee --- /dev/null +++ b/static/v10/man8/sendnews.8 @@ -0,0 +1,60 @@ +.TH SENDNEWS 8 +.SH NAME +sendnews \- send news articles via mail +.SH SYNOPSIS +sendnews +[ +.B \-o +] +[ +.B \-a +] +[ +.B \-b +] +[ +.B \-n +newsgroups +] +destination +.SH DESCRIPTION +.I sendnews +reads an article from it's standard input, performs a set of changes +to it, and gives it to the mail program to mail it to +.I destination. +.PP +An `N' is prepended to each line for decoding by +.I uurec(1). +.PP +The +.B \-o +flag handles old format articles. +.PP +The +.B \-a +flag is used for sending articles via the +.B ARPANET. +It maps the article's path from +.I uucphost!xxx +to +.I xxx@arpahost. +.PP +The +.B \-b +flag is used for sending articles via the +.B Berknet. +It maps the article's path from +.I uucphost!xxx +to +.I berkhost:xxx. +.PP +The +.B \-n +flag changes the article's newsgroup to the specified +.I newsgroup. +.SH SEE ALSO +inews(1), +uurec(8), +recnews(8), +readnews(1), +checknews(1) diff --git a/static/v10/man8/ship.8 b/static/v10/man8/ship.8 new file mode 100644 index 00000000..2901d1c9 --- /dev/null +++ b/static/v10/man8/ship.8 @@ -0,0 +1,118 @@ +.TH SHIP 8 +.CT 1 comm_mach sa_nonmortals +.SH NAME +ship, shipstat \(mi automatic software distribution +.SH SYNOPSIS +.B ship +[ +.I option ... +] +[ +.I file ... +] +.PP +.B shipstat +.SH DESCRIPTION +.I Ship +distributes the named files to other computers, where +the files are installed under the same names. +Shipping privileges are determined +by the network manager on the receiving machine; +see +.IR svcmgr (8). +.PP +Destinations are taken from environment variable +.BR dest , +or from +.F /usr/lib/asd/dest/default +if +.B dest +is empty. +If a destination is the name of a file in +.FR /usr/lib/asd/dest , +it is replaced by the contents of that file, +each word of which is then examined in the same way. +Otherwise the destination is a network address. +The sending machine is omitted unless explicitly named in +the environment variable, +or unless option +.B -f +is present or environment variable +.B force +has a non-empty value. +.PP +.I Ship +uses +.I inspkg +and +.IR mkpkg (8) +to do its work. +Links among the named files are imitated +on the receiving computer, and +named files that do not exist on the sending +computer are deleted on the receiving computer. +Other options are the same as those of +.IR mkpkg : +.PP +.TP \w'\-X file 'u +.B -v +Emit running commentary on the standard error file. +.TP +.BI -D path1 = path2 +Pretend that any +.I file +name that begins with +.I path1 +really begins with +.IR path2 . +Relative pathnames are extended to full pathnames before comparison. +.TP +.BI -x command +.br +.ns +.TP +.BI -X file +Include in the package instructions to execute the shell +.I command +or run the shell script +.I file +after all files have been installed. +Only one of these options may occur. +The +.I file +name in +.BR -X +is affected by +.BR -D . +.PP +Shipments are generally acknowledged by mail after each destination +has been tried at least once; +see +.IR asd (8) +for details. +.PP +.I Shipstat +reports the status of all its caller's +incomplete shipments, +with the most recent first. +.SH FILES +.TF/usr/lib/asd/dest/default +.TP +.F /usr/lib/asd/dest/* +distribution lists +.TP +.F +/usr/lib/asd/dest/default +default distribution list +.TP +.BI /usr/spool/asd/ logname +outgoing spool directories +.SH SEE ALSO +.IR mkpkg (8), +.IR asd (8), +.IR svcmgr (8) +.SH BUGS +The +.B -f +option, if given, must be the first option and +must not be combined with any other. diff --git a/static/v10/man8/showq.8 b/static/v10/man8/showq.8 new file mode 100644 index 00000000..cf46ea27 --- /dev/null +++ b/static/v10/man8/showq.8 @@ -0,0 +1,56 @@ +.TH SHOWQ 8 +.CT 1 sa_nonmortals +.SH NAME +showq \- status of stream input/output system +.SH SYNOPSIS +.B /etc/showq +[ +.B "-v -V -s -m +] +[ +.I system +] +[ +.I mem +] +.SH DESCRIPTION +.I Showq +reports connectivity and contents of I/O streams. +By default, it lists the maximum number of stream blocks +(of various sizes) ever used, then each stream and the queue modules +in each stream, and then blocks that are unaccounted for (not on any +queue or the free list). +.PP +By default, the system namelist is +.B /unix +and the place the streams are kept is +.BR /dev/mem . +.PP +The options are: +.TP +.B -v +Verbose. +Show more, in particular the contents of data and control blocks on each queue. +.TP +.B -V +Very verbose. +Show all blocks on every queue instead of giving up after a while. +.TP +.B -s +Silent. +Examine queues for consistency, printing only a summary. +.TP +.B -m +Missing. +Show the contents of missing blocks. +(Perhaps this will give a clue about who lost them.) +.SH FILES +.F /unix +.br +.F /dev/mem +.SH SEE ALSO +.IR stream (4), +.IR netstat (8) +.br +.IR mesgld (4) +for a list of message types diff --git a/static/v10/man8/shutdown.8 b/static/v10/man8/shutdown.8 new file mode 100644 index 00000000..bfee17cb --- /dev/null +++ b/static/v10/man8/shutdown.8 @@ -0,0 +1,9 @@ + +.TH SHUTDOWN 8 +.UC 4 +.SH NAME +shutdown \- take system down gracefully +.SH DESCRIPTION +To be supplied. +.SH "SEE ALSO" +reboot(8) diff --git a/static/v10/man8/smash.8 b/static/v10/man8/smash.8 new file mode 100644 index 00000000..5f076ad7 --- /dev/null +++ b/static/v10/man8/smash.8 @@ -0,0 +1,43 @@ +.TH SMASH 8 +.CT 1 sa_nonmortals +.SH NAME +smash \- rewrite bad disk sectors +.SH SYNOPSIS +.B /etc/smash +.I device sector +.SH DESCRIPTION +.I Smash +attempts to read the named (decimal, 512-byte) +.I sector +from the named +.IR device , +and prints the error status from the read +and the data read, +in octal, +regardless of the error status. +It then prompts +.LR write? , +to which there are three answers: +.TP +.B y +Write the data back to the sector. +.TP +.B c +Write zeros to the sector. +.TP +anything else +Quit. +.PP +After the sector is written, +it is read again +and the cycle repeats. +.PP +Writing the sector, +even if its contents could be correctly read, +will recompute the error correcting code. +This may make soft ECC errors vanish, +and will recover what can be recovered +(sometimes not much) +from hard ECC errors. +.SH SEE ALSO +.IR rarepl (8) diff --git a/static/v10/man8/smstat.8 b/static/v10/man8/smstat.8 new file mode 100644 index 00000000..b4cce1ab --- /dev/null +++ b/static/v10/man8/smstat.8 @@ -0,0 +1,24 @@ +.TH SMSTAT 8 +.CT 1 comm_mach +.SH NAME +smstat \- list smtp queues +.SH SYNOPSIS +.B smstat +.SH DESCRIPTION +.I Smstat +prints a summary of pending mail messages +queued by +the programs in +.IR smtp (8). +Each line contains the name of a spooling directory; +the number of outbound messages, +followed by +.LR C ; +and the number of inbound messages, +followed by +.LR X . +.SH FILES +.F /usr/spool/smtpq/* +spool directories +.SH SEE ALSO +.IR smtp (8) diff --git a/static/v10/man8/smtp.8 b/static/v10/man8/smtp.8 new file mode 100644 index 00000000..b6c6315d --- /dev/null +++ b/static/v10/man8/smtp.8 @@ -0,0 +1,200 @@ +.TH SMTP 8 +.CT 1 sa_auto +.SH NAME +smtp, smtpqer, smtpd, smtpsched \- handle simple mail transfer protocol +.SH SYNOPSIS +.B /usr/lib/upas/smtp +[ +.I option ... +] +.I replyaddr +.I dest +.I recipient ... +.PP +.B /usr/lib/upas/smtpqer +[ +.I option ... +] +.I replyaddr +.I dest +.I recipient ... +.PP +.B /usr/lib/upas/smtpd +[ +.B -n +] [ +.B -H +.I host +] +.PP +.B /usr/lib/upas/smtpsched +[ +option ... +] [ +.I queue ... +] +.SH DESCRIPTION +.I Smtp +reads a mail message from the standard input, +and sends it with the Internet SMTP protocol +to the named +.I recipients +at +network address +.IR dest . +.I Dest +has default network +.B tcp +and default +service +.B tcp.25 +(the conventional Internet SMTP port). +Error reports are mailed to local address +.IR replyaddr . +.PP +.I Smtp +operates in two modes, `Internet' (default) and `Unix'. +In Internet mode +.I recipient +addresses should be in full domain form. +.L From: +and +.L Date: +headers will be inserted as necessary +to conform to Internet standards. +In Unix mode +addresses and message contents +are not touched. +The options are +.TP +.B -u +Run in Unix mode. +.TP +.BI -H " host" +Use +.I host +as the name of the sending system (taken from +.IR whoami (5) +by default). +.TP +.BI -d " domain +Append the specified domain suffix to +incomplete addresses. +.PP +.I Smtpqer +reads a mail message from the standard input +and stashes it away +to be sent later +by +.IR smtpsched . +By default, +.I smtpsched +is started immediately; +option +.B -n +prevents this. +Other options and arguments are the same as for +.IR smtp . +.PP +.I Smtpd +receives a message by +speaking the server part of SMTP +on the standard input and output. +The message is stashed in a queue for later delivery +as by +.IR smtpqer . +Option +.B -n +prevents +.I smtpsched +from running immediately; +option +.B -H +is as for +.I smtp. +.PP +.I Smtpsched +processes the queues assembled by +.I smtpqer +and +.IR smtpd , +calling +.IR mail (1) +for local messages and +.I smtp +for others. +It should be run occasionally from +.IR cron (8). +.PP +The +.I queue +arguments name particular queue directories to be processed; +if no queue is named, +all queues are processed. +The options are +.TF "-s\0nproc" +.TP +.BI -w " days" +Send a warning about each message more than +.I days +old to the reply address. +.TP +.BI -r " days" +Mail an error reply about each message more than +.I days +old, +and discard the message. +.TP +.BI -s " nproc" +Do not run more than +.I nproc +simultaneous copies of +.I smtpsched +started with this option. +.TP +.B -c +Remove empty directories and inconsistent files. +.TP +.B -t +Log actions without performing them. +.TP +.B -C +Process `C' command files +.RI ( smtp +calls) only. +.TP +.B -X +Process `X' command files +.RI ( rmail +calls) only. +.TP +.B -v +Enable verbose logging. +.PD +.PP +The queues are kept in subdirectories of +.FR /usr/spool/smtpq , +named by splitting the lower case remote system name +into components separated by +periods, +concatenating the last two or fewer components, +taking the last 14 characters, +and stripping leading periods. +.SH FILES +.TF /usr/spool/smtpq/smtpqsched.log +.TP +.B /usr/spool/smtpq +spooling directory +.TP +.B /usr/spool/smtpq/smtpqsched.log +logging +.TP +.B /usr/spool/smtpq/.consumers +list of process IDs running +.I smptqsched -s +.SH SEE ALSO +.IR mail (1), +.IR upas (8), +.IR smstat (8) +.br +DARPA standards RFC 822, RFC 976 diff --git a/static/v10/man8/sticky.8 b/static/v10/man8/sticky.8 new file mode 100644 index 00000000..e9d9e1a5 --- /dev/null +++ b/static/v10/man8/sticky.8 @@ -0,0 +1,44 @@ +.TH STICKY 8 +.UC 4 +.SH NAME +sticky \- executable files with persistent text +.SH DESCRIPTION +While the `sticky bit', mode 01000 (see +.IR chmod (2)), +is set on a sharable executable file, +the text of that file will not be removed from the system swap area. +Thus the file does not have to be fetched from the file system +upon each execution. +As long as a copy remains in the swap area, the +original text cannot be overwritten in the file system, +nor can the file be deleted. +(Directory entries can be removed so long as one link remains.) +.PP +Sharable files are made by the +.B \-n +and +.B \-z +options of +.IR ld (1). +.PP +To replace a sticky file that has been used do: +(1) Clear the sticky bit with +.IR chmod (1). +(2) Execute the old program to flush the swapped copy. +This can be done safely even if others are using it. +(3) Overwrite the sticky file. +If the file is being executed by any process, +writing will be prevented; it suffices to simply remove the file +and then rewrite it, being careful to reset the owner and mode with +.I chmod +and +.IR chown (2). +(4) Set the sticky bit again. +.PP +Only the super-user can set the sticky bit. +.SH BUGS +Are self-evident. +.PP +Is largely unnecessary on the VAX; matters only for large programs that +will page heavily to start, since text pages are normally cached incore +as long as possible after all instances of a text image exit. diff --git a/static/v10/man8/su.8 b/static/v10/man8/su.8 new file mode 100644 index 00000000..99721bb9 --- /dev/null +++ b/static/v10/man8/su.8 @@ -0,0 +1,34 @@ +.pa 1 +.he 'SU (VIII)'1/20/73'SU (VIII)' +.ti 0 +NAME su -- become privileged user +.sp +.ti 0 +SYNOPSIS su__ +.sp +.ti 0 +DESCRIPTION su +allows one to become the super-user, who has +all sorts of marvelous (and correspondingly dangerous) powers. +In order for su to do its magic, the user must +supply a password. +If the password is correct, su +will execute the shell with the UID set to +that of the super-user. +To restore normal UID privileges, +type an end-of-file to the super-user shell. + +To remind the super-user of his responsibilities, +the shell substitutes "#" for its usual prompt "%". +.sp +.ti 0 +FILES -- +.sp +.ti 0 +SEE ALSO sh(I) +.sp +.ti 0 +DIAGNOSTICS "Sorry" if password is wrong +.sp +.ti 0 +BUGS -- diff --git a/static/v10/man8/svcmgr.8 b/static/v10/man8/svcmgr.8 new file mode 100644 index 00000000..2b9ab3a8 --- /dev/null +++ b/static/v10/man8/svcmgr.8 @@ -0,0 +1,331 @@ +.TH SVCMGR 8 +.CT 1 sa_auto +.SH NAME +svcmgr \- service remote computing requests +.SH SYNOPSIS +.B /usr/ipc/mgrs/svcmgr +[ +.B -d +] +.SH DESCRIPTION +.I Svcmgr +performes services +such as login and command execution, +often in response to requests from network listeners +like +.IR dkmgr +and +.IR tcpmgr (8). +It should be run once from +.IR rc (8). +.PP +.I Svcmgr +is controlled by several files in directory +.FR /usr/ipc/lib : +services are defined in files +.B serv +and +.BR serv.local , +authorization in +.B auth +and +.BR auth.local . +The +.B .local +files are searched first. +The idea is that +.B serv +and +.B auth +will be the same throughout an administrative cluster of machines, +and anything peculiar to specific systems +will be kept in +.B serv.local +and +.BR auth.local . +.PP +Each service is announced +as a name in directory +.F /cs +using the routines in +.IR ipc (3). +When a connection is requested to one of these services, +.I svcmgr +receives a file descriptor +connected to the requester. +A new process is created +to perform the actions listed for that service +in the +.I serv +files, +usually resulting in a +.IR login (8) +with standard input, output, and error files +attached to the connection. +Often +there are flags to +.I login +specifying a local user name +or a command to be executed. +Environment variable +.SM CSOURCE +is set to a string +of the form +.IP +.BI source= remote-machine +.BI user= ruser +.BI line= lineinfo +.PP +.I Remote-machine +and +.I ruser +are supplied in the connection message; +.I lineinfo +network-dependent stuff +of varying interest and meaning. +If a particular command was specified +(the +.B cmd +or +.B exec +action), +.I login +sets +environment variable +.SM REXEC +to +.LR 1 . +.PP +The +.I auth +files are used to translate remote user names to local ones. +They contain lines with four fields: +.RS +service name +.br +calling system name +.br +calling user name +.br +local user name +.RE +.LP +The service, calling system, and calling user names +are regular expressions +in the style of +.IR regexp (3). +The calling system and calling user fields may be omitted; +.L .* +is assumed. +The local user name +is a literal name, +.L & +to repeat the calling user name provided in the request, +or +.L : +to explicitly reject a call. +If the local user name is omitted, +.L & +is assumed. +.PP +Several service actions `look up the connection in the +.I auth +files.'\0 +This means to +find the first line in +.B auth.local +or +.B auth +for which the service, +calling system, +and calling user +match the patterns, +and return the local user name in that line +(the same as the calling user if +.LR & ). +If no matching line is found, +or if the first match has local user name +.LR : , +the lookup fails. +.PP +The +.I serv +files contain lines with three fields: +.RS +service name +.br +a list of actions, +separated by +.L + +.br +the calling system name +.RE +.PP +The calling system name is a regular expression as in +the +.I auth +file. +The line matching an incoming call is the first whose service +matches the requested service and whose regular expression +matches the calling machine. +.PP +The possible actions are: +.de XP +.TP +.ie '\\$2'' .L "\\$1" +.el .L "\\$1(\f2\\$2\fP)" +.. +.TF password +.PD +.XP user x +Use local username +.IR x . +.XP auth +Look up the connection +in the +.I auth +files. +If a match is found, +use the resulting local user. +Otherwise reject the call. +.XP v9auth +Look up the connection +in the +.I auth +files; +if a match is found, +send +.L OK +to the caller, +and use the result. +If there is no match, send +.LR NO , +and read a string of the form `login,passwd\\n'. +If the login and password +describe a valid local user, +send +.L OK +and use that user; +otherwise send +.L NO +and try again +(until the caller gives up). +This is the authentication protocol used by +.IR ipclogin +(see +.IR ipc (3)), +hence by +.IR con (1), +.IR push (1), +and +.IR pull. +.XP inauth +Read two null-terminated strings +from the caller. +If they aren't the same, +reject the call. +Otherwise look up the service, +calling system, +and the null-terminated string +(as a user name) +in the +.I auth +files, +use the resulting local user if there's a match, +reject the call otherwise. +This is the authentication protocol used by +.IR ipcrogin, +hence by +.IR rsh +and +.IR rlogin ; +see +.IR ipc (3) +and +.IR con (1). +.XP ttyld +Push the terminal line discipline +.IR ttyld (4) +onto the connection. +.XP mesgld +Push the reverse message line discipline +(see +.IR mesgld (4)) +onto the connection. +.XP term +Read a null-terminated string from the caller, +and set environment variable +.SM TERM +to the result. +.XP args +Read a null-terminated string from the caller, +and save the result as arguments to a possible command. +.XP s5parms +Extract arguments from the destination address +in a way compatible with the +DKHOST network software +used by System V Datakit implementations, +and save for later use. +.XP cmd x +Execute shell command +.IR x , +with any saved arguments, +and with the connection as standard input, output, and error. +.XP login +Provide a login session with the connection as standard input, output, and error. +.XP password +Provide a login session, +but ignore any local user name; +always demand a login and password. +.XP exec +Use any saved arguments +as a shell command to be executed. +.XP gateout gateway +Call network address +.IR gateway +and send the connection info there, +If all is well, +pass the new connection's file descriptor +to the original caller: +the result is a connection through the gateway. +.I Gateway +should be a +.I svcmgr +service, +perhaps on some other machine, +with action +.BR gateway . +.XP gateway localout +The intended target for +.BR gateout : +read new connection info from the connection, +and place a call to the new destination; +if it succeeds, +loop passing data between the new connection and the original one. +.PP +If the file +.F /usr/ipc/log/svc +can be opened, +.I svcmgr +prints miscellaneous chatter there, +including a record of each service request. +The +.B -d +(debug) +option increases the chatter. +...SH EXAMPLES +...to be supplied +.SH FILES +.nf +.F /usr/ipc/lib/serv +.F /usr/ipc/lib/serv.local +.F /usr/ipc/lib/auth +.F /usr/ipc/lib/auth.local +.F /usr/ipc/log/svc +.fi +.SH "SEE ALSO" +.IR con (1), +.IR ipc (3), +.IR dkmgr (8), +.IR tcpmgr (8), +.IR ipc (3) diff --git a/static/v10/man8/swapon.8 b/static/v10/man8/swapon.8 new file mode 100644 index 00000000..7193e909 --- /dev/null +++ b/static/v10/man8/swapon.8 @@ -0,0 +1,37 @@ +.TH SWAPON 8 +.CT 1 sa_auto +.SH NAME +swapon \- specify swapping device +.SH SYNOPSIS +.B "/etc/swapon" +.B -a +.br +.B "/etc/swapon" +.I name ... +.SH DESCRIPTION +.I Swapon +specifies additional devices on which paging and swapping +are to take place. +The system begins by using a single device; +.I swapon +must be used to enable others. +.PP +Usually there is a call to +.L "swapon -a" +in +.IR rc (8). +Specific swap devices may be nominated with the second form. +.SH SEE ALSO +.IR rc (8), +.I vswapon +in +.IR deprecated (2) +.SH BUGS +There is no way to stop paging and swapping on a device. +It is therefore not possible to make use of devices which may be +dismounted during system operation. +.br +Possible swap devices +must be listed in a table configured into the system; +.I swapon +can only enable devices in the table. diff --git a/static/v10/man8/swtmp.8 b/static/v10/man8/swtmp.8 new file mode 100644 index 00000000..e19ed31c --- /dev/null +++ b/static/v10/man8/swtmp.8 @@ -0,0 +1,24 @@ +.pa 1 +.he 'SWTMP (VIII)'2/11/73'SWTMP (VIII)' +.ti 0 +NAME swtmp -- update accounting file +.sp +.ti 0 +SYNOPSIS swtmp_____ +.sp +.ti 0 +DESCRIPTION This +shell sequence concatenates /tmp/wtmp onto /usr/adm/wtmp +and truncates /tmp/wtmp. +It should be used before +using acct(VIII) +and every so often in any case if accounting +is to be maintained. +.sp +.ti 0 +FILES /tmp/wtmp, +/usr/adm/wtmp +.sp +.ti 0 +SEE ALSO acct(VIII), +wtmp(V) diff --git a/static/v10/man8/symorder.8 b/static/v10/man8/symorder.8 new file mode 100644 index 00000000..9d2668dc --- /dev/null +++ b/static/v10/man8/symorder.8 @@ -0,0 +1,23 @@ +.TH SYMORDER 8 +.UC +.SH NAME +symorder \- rearrange name list +.SH SYNOPSIS +.B symorder +orderlist symbolfile +.SH DESCRIPTION +.I Orderlist +is a file containing symbols to be found in symbolfile, +1 symbol per line. +.PP +.I Symbolfile +is updated in place to put the requested symbols first +in the symbol table, in the order specified. This is done +by swapping the old symbols in the required spots with the +new ones. If all of the order symbols are not found, an +error is generated. +.PP +This program was specifically designed to cut down on the +overhead of getting symbols from /vmunix. +.SH "SEE ALSO" +nlist(3) diff --git a/static/v10/man8/sync.8 b/static/v10/man8/sync.8 new file mode 100644 index 00000000..d95c8ad8 --- /dev/null +++ b/static/v10/man8/sync.8 @@ -0,0 +1,18 @@ +.th SYNC VIII 11/1/73 +.sh NAME +sync \*- update the super block +.sh SYNOPSIS +.bd sync +.sh DESCRIPTION +.it Sync +executes the +.it sync +system primitive. +If the system is to be stopped, +.it sync +must be called to insure +file system integrity. +See sync(II) for details. +.sh "SEE ALSO" +sync(II) +.sh BUGS diff --git a/static/v10/man8/syslog.8 b/static/v10/man8/syslog.8 new file mode 100644 index 00000000..da1f5040 --- /dev/null +++ b/static/v10/man8/syslog.8 @@ -0,0 +1,172 @@ +.TH SYSLOG 8 +.CT 1 sa_nonmortals +.SH NAME +syslog, logpr \- system security logging +.SH SYNOPSIS +.B priv syslog +.I command +[ +.I arg2 +[ +.I arg3 +] +] +.PP +.B /etc/logpr +.I file +[ +.I offset +] +.SH DESCRIPTION +.I Syslog +controls the mandatory logging scheme. +License +.B T_LOG +is required. +The variety of different commands and command formats +reflects the full complexity of the +protean +.IR syslog (2) +system call. +In the usages given below a +.I mask +argument is a combination of letters +.BR NILESDATUPX , +meaning: +.TP +.PD0 +.B N +Record all uses of file names. +.TP +.B S +Record all seek calls. +.TP +.B U +Record all writes to the `u area'. +.TP +.B I +Record all accesses of inode contents. +.TP +.B D +Record possession and use of file descriptors. +.TP +.B P +Record process history: +.IR exec (2), +.IR fork (2), +.IR kill (2), +.IR exit (2). +.TP +.B L +Record all explicit changes of labels by +.IR setflab +(see +.IR getflab (2)) +and +.IR setplab +(see +.IR getplab (2)). +.TP +.B A +Record all changes of labels. +.TP +.B X +Record all uses of privilege. +.TP +.B E +Record all +.B ELAB +error returns. +.TP +.B T +Record all uses of a traced file or process. +.PD +.PP +Valid arguments to +.I syslog +are: +.TP +.BI "on " file " " logdev +Nominate +.I file +as repository for user generated +logging records written to logging special file +.IR logdev . +.I File +must be a full path name, and must be openable for writing. +If +.IR logdev 's +minor device number is zero, +.I file +will also receive mandatory (kernel generated) logging records. +.I Logdev +may be a full path name or a minor device number. +.PD0 +.TP +.BI "off " logdev +Cancel the effect of an +.B on +command. +.TP +.BI "get " n +Print the value of the +.IR n -th +log mask. +Values of +.I n +are 0, 1, 2, or 3 +for the `poison' masks; 4 is `global' mask. +.TP +.BI "set " n " " mask +Set the value of the +.IR n -th +log mask. +.TP +.BI "fget " file +Print the poison level of +.IR file , +one of the integers 0, 1, 2, or 3. +.I File +must be the full path name of a readable file. +.TP +.BI "fset " file " " n +Set the poison level of +.I file +to +.IR n . +.I File +must be the full path name of a readable file. +.TP +.BI "pget " pid +Print the logging mask of process +.IR pid . +.TP +.BI "pset " pid " " mask +Set the logging mask of process +.I pid +to +.IR mask . +.PD +.PP +.I Logpr +converts to cryptic +.SM ASCII +the cryptic binary format of a log file described in +.IR log (5). +The optional numerical byte offset tells where in the file printing +is to start. +.SH FILES +.TF /dev/log/log00 +.TP +.F /dev/log/log00 +where +.I syslog +makes voluntary entries +.SH "SEE ALSO" +.IR syslog (2), +.IR log (4), +.IR log (5). +.SH DIAGNOSTICS +`Covert channel warning': the log file has +a label that is neither top nor flagged +.BR L_NO . diff --git a/static/v10/man8/tcpmgr.8 b/static/v10/man8/tcpmgr.8 new file mode 100644 index 00000000..ce77d7be --- /dev/null +++ b/static/v10/man8/tcpmgr.8 @@ -0,0 +1,73 @@ +.TH TCPMGR 8 +.CT 1 sa_auto +.SH NAME +tcpmgr \- accept and place calls via the TCP protocol +.SH SYNOPSIS +.B /usr/ipc/mgrs/tcpmgr +[ +.BI -m " outnet" +] +.SH DESCRIPTION +.I Tcpmgr +receives and places TCP calls on an Internet TCP/IP network. +Outbound TCP calls may be placed by calling +.I ipcopen +with network name +.B tcp +(see +.IR ipc (3)). +Inbound calls to TCP port +.I n +are handed to the local service +listed for that port in +.FR /usr/ipc/lib/inservices , +or to service +.BI tcp. n +if there is no listing. +.PP +Option +.B -m +tells +.I tcpmgr +to claim to place outbound calls for network +.I outnet +rather than +.BR tcp . +.PP +The TCP protocol runs atop one or more IP networks. +.I Tcpmgr +arranges to receive all inbound TCP calls on all active IP networks, +but other arrangements +must be used to activate the IP networks themselves; +see +.IR ipconfig (8). +.PP +.I Tcpmgr +records its activity +in file +.I outnet +in directory +.BR /usr/ipc/log , +default +.BR /usr/ipc/log/tcp . +.PP +This command is usually run once from +.IR rc (8). +.SH FILES +.TP 2i +.PD 0 +.F /usr/ipc/log/tcp +.TP +.FR /dev/tcp* +TCP network devices +.TP +.F /dev/iptcp +IP channel for the TCP protocol +.TP +.F /usr/ipc/lib/inservices +mapping between service name and port number +.SH "SEE ALSO" +.IR con (1), +.IR ipconfig (8), +.IR svcmgr (8), +.IR ipc (3) diff --git a/static/v10/man8/tm.8 b/static/v10/man8/tm.8 new file mode 100644 index 00000000..4240c173 --- /dev/null +++ b/static/v10/man8/tm.8 @@ -0,0 +1,48 @@ +.pa 1 +.he 'TM (VIII)'3/15/72'TM (VIII)' +.ti 0 +NAME tm -- provide time information +.sp +.ti 0 +SYNOPSIS tm__ +.sp +.ti 0 +DESCRIPTION tm__ +is used to provide timing information. +Output like the following +is given: +.sp +.in +5 + tim 371:51:09 2:00.8 + ovh 20:00:33 17.0 + swp 13:43:20 4.6 + dsk 27:14:35 4.5 + idl 533:08:03 1:33.3 + usr 24:53:50 1.2 + der 0, 54 0, 0 +.sp +.in -5 +The first column of numbers gives totals in the named categories +since the last time the system was cold-booted; the second +column gives the changes since the last time tm__ was invoked. +The top left number is badly truncated and should be ignored. +ovh___ is time spent +executing in the system; +swp___ is time waiting for swap I/O; +dsk___ is time spent waiting for +file system disk I/O; idl___ is idle time; usr___ is user execution +time; der___ is RF disk error count (left number) and RK disk error +count (right number). + +.ti 0 +FILES /dev/rf0 (for absolute times); +/tmp/ttmp for differential timing history. +.sp +.ti 0 +SEE ALSO time(I), file system(V) +.sp +.ti 0 +DIAGNOSTICS -- +.sp +.ti 0 +BUGS -- diff --git a/static/v10/man8/tp.8 b/static/v10/man8/tp.8 new file mode 100644 index 00000000..7e27f382 --- /dev/null +++ b/static/v10/man8/tp.8 @@ -0,0 +1,175 @@ +.TH TP 8 +.SH NAME +tp \- manipulate tape archive +.SH SYNOPSIS +.B tp +[ key ] [ name ... ] +.SH DESCRIPTION +.PP +.I Tp +saves and restores files +on DECtape or magtape. +Its actions are controlled by the +.I key +argument. +The key is a string of characters containing +at most one function letter and possibly +one or more function modifiers. +Other arguments to the command are file or directory +names specifying which files are to be dumped, restored, +or listed. +In all cases, appearance of a directory name refers to +the files and (recursively) subdirectories of that directory. +.PP +The function portion of +the key is specified by one of the following letters: +.TP 8 +.B r +The named files +are written +on the tape. +If files with the same names +already exist, they are replaced. +`Same' is determined by string comparison, so +`./abc' can never be the same as `/usr/dmr/abc' even +if `/usr/dmr' is the current directory. +If no file argument is given, `\fB.\fR' is the default. +.TP 8 +.B u +updates the tape. +.B u +is like +.B r, +but a file is replaced only if its +modification date is later than the date stored on the tape; +that is to say, if it has changed since it was dumped. +.B u +is the default command if none is given. +.TP 8 +.B d +deletes the named files from +the tape. +At least one name argument must be given. +This function is not permitted on magtapes. +.TP 8 +.B x +extracts the named files from the tape to the file system. +The owner and mode are restored. +If no file argument is given, the entire contents of the +tape are extracted. +.TP 8 +.B t +lists the names of the specified files. +If no file argument is given, +the entire contents of the tape is listed. +.PP +The following characters may be used in addition to the letter +which selects the function desired. +.TP 10 +.B m +Specifies magtape as opposed to DECtape. +.TP 10 +.B 0,...,7 +This +modifier selects the drive on which the tape is mounted. +For DECtape, +.B x +is default; for magtape +`0' is the default. +.TP 10 +.B v +Normally +.I tp +does its work silently. +The +.B v +(verbose) +option causes it to type the name of each file it treats +preceded by the function letter. +With the +.B t +function, +.B v +gives more information about the +tape entries than just the name. +.TP 10 +.B c +means a fresh dump is being created; the tape directory +is cleared before beginning. +Usable only with +.B r +and +.B u. +This option is assumed with magtape since +it is impossible to selectively overwrite +magtape. +.TP 10 +.B i +Errors reading and writing the +tape are noted, but no action is taken. +Normally, errors cause a return to the command level. +.TP 10 +.B f +Use the first named file, rather than a tape, +as the archive. +This option currently acts like +.BR m ; +.I i.e. +.BR r +implies +.BR c , +and neither +.BR d +nor +.BR u +are permitted. +.TP 10 +.B w +causes +.I tp +to pause before treating each file, type +the indicative letter and the file name (as with +.BR v ) +and await the user's response. +Response +.B y +means `yes', so the file is treated. +Null response +means `no', and the file does not take part +in whatever is being done. +Response +.B x +means `exit'; +the +.I tp +command terminates immediately. +In the +.B x +function, +files previously asked about +have been extracted already. +With +.B "r, u," +and +.B d +no change has been made to the tape. +.PP +.SH FILES +/dev/tap? +.br +/dev/rmt? +.SH SEE ALSO +ar(1), tar(1) +.SH DIAGNOSTICS +Several; the non-obvious one is +`Phase error', which means the file changed after it was selected for +dumping but before it was dumped. +.SH BUGS +A single file with several links to it is treated like several files. +.PP +Binary-coded control information makes +magnetic tapes written by +.I tp +difficult to carry to other machines; +.IR tar (1) +avoids the problem. diff --git a/static/v10/man8/umount.8 b/static/v10/man8/umount.8 new file mode 100644 index 00000000..a69a5b8d --- /dev/null +++ b/static/v10/man8/umount.8 @@ -0,0 +1,31 @@ +.pa 1 +.he 'UMOUNT (VIII)'1/20/73'UMOUNT (VIII)' +.ti 0 +NAME umount -- dismount file system +.sp +.ti 0 +SYNOPSIS /etc/umount___________ special +.sp +.ti 0 +DESCRIPTION umount______ +announces to the system that the removable file system previously +mounted on special file special_______ is to be removed. + +The user must take care not +only that all I/O activity on the file system has ceased, +but that no one has his current directory on it. + +Only the super-user may issue this command. +.sp +.ti 0 +FILES -- +.sp +.ti 0 +SEE ALSO mount(VIII) +.sp +.ti 0 +DIAGNOSTICS "?" +.sp +.ti 0 +BUGS This +command is not, in fact, restricted to the super-user. diff --git a/static/v10/man8/unspk.8 b/static/v10/man8/unspk.8 new file mode 100644 index 00000000..af99d8c1 --- /dev/null +++ b/static/v10/man8/unspk.8 @@ -0,0 +1,43 @@ +.pa 1 +.he 'UNSPK (VIII)'4/13/73'UNSPK (VIII)' +.ti 0 +NAME unspk -- decode voice synthesizer text +.sp +.ti 0 +SYNOPSIS unspk_____ [ -_ ] [ input [ output ] ] +.sp +.ti 0 +DESCRIPTION unspk_____ +is inverse to +.ul +speak. +It translates coded voice synthesizer input, as created by +.ul +speak, +into phonetic strings +of the sort accepted by +.ul +speak. +Standard output or input is assumed when one or the other +is unspecified. +.sp +The -_ option produces output in a different phonetic code +for another vocal tract synthesizer [C. H. Coker, +Speech synthesis by modelling the human articulatory +system, MM69-1232-29]. +.sp +unspk_____ lives in /crp/vs +.sp +.ti 0 +FILES -- +.sp +.ti 0 +SEE ALSO speak(I), vsp(VII) +.sp +.ti 0 +DIAGNOSTICS "Input file." -- can't open it +.br +"Output file." -- can't create it +.sp +.ti 0 +BUGS -- diff --git a/static/v10/man8/upas.8 b/static/v10/man8/upas.8 new file mode 100644 index 00000000..8cf496bd --- /dev/null +++ b/static/v10/man8/upas.8 @@ -0,0 +1,275 @@ +.TH UPAS 8 +.CT 1 sa_auto sa_mortals +.SH NAME +upas, rmail, translate \- mail delivery system +.SH SYNOPSIS +.B rmail +.I person ... +.PP +.B /usr/lib/upas/translate +.I name +.PP +.B /usr/lib/upas/auth +.I sender +.I receiver +.SH DESCRIPTION +Users send mail by +.IR mail (1). +Remote machines use +.I rmail. +Both call on +.I upas +programs. +.PP +Mail addresses are interpreted +according to rewrite rules as +described below. +When the addresses for a +.I mail +or +.I rmail +command have been interpreted, they are bundled by +network and passed to network-specific handlers, +such as +.IR route.inet . +.PP +.I Translate +looks up a mail +.I name +in an alias list (see +.IR mail (6)) +and places the result on standard output. +.PP +.I Auth +is called by +.I upas +to authorize mail delivery for each +.I sender, receiver +pair. +The mail is accepted if +the previous hop was a trusted gateway machine in +.FR /usr/lib/upas/gateways , +or all the machines in the source or destination path are in +.FR /usr/lib/upas/attlist . +.SS Rewrite rules +Each line of the file +.F /usr/lib/upas/rewrite +is a rule. +Blank lines and lines beginning with +.B # +are ignored. +.PP +Each rewriting rule consists of (up to) 4 strings: +.TP +.I pattern +A regular expression in the style of +.IR regexp (3). +The +.I pattern +is applied to mail destination addresses. +The pattern match is case-insensitive +and must match the entire address. +.TP +.I type +The type of rule; see below. +.TP +.I arg1 +An +.IR ed (1) +style replacement string, with +.BI \e n +standing for the text matched by the +.IR n th +parenthesized subpattern. +.TP +.I arg2 +Another +.IR ed (1) +style replacement string. +.PP +In each of these fields the substring +.L \es +is replaced by the login id of the +sender and the substring +.L \el +is replaced by the name of the local machine. +.PP +When delivering a message, +.I mail +starts with the first rule and continues down the list until a pattern +matches the destination address. +It then performs one of the following actions depending on rule type: +.PD 0 +.TP +.B >> +Append the mail to the file indicated by expanding +.IR arg1 , +provided that file appears to be a valid mailbox. +.TP +.B | +Pipe the mail through the command formed from concatenating the +expanded +.I arg1 +and +.I arg2. +.TP +.B alias +Replace the address by the address(es) specified +by expanding +.I arg1 +and recur. +.TP +.B translate +Replace the address by the address(es) output by the +command formed by expanding +.I arg1 +and recur. +.TP +.B auth +Call the program in expanded +.I arg1 +and authorize(reject) the mail if it returns a zero(non-zero) return code. +.PD +.PP +.I Mail +expands the addresses recursively until each address has matched a +.L >> +or +.L | +rule or until the recursion depth indicates a rewriting loop +(currently 32). +.PP +An +.L auth +operator is only applied once per address. +If no +.L auth +rule is encountered, the mail is accepted. +.PP +If several addresses match +.L | +rules and result in the same +expanded +.IR arg1 , +the message is delivered to all those addresses +by a single command, +composed by concatenating the common +expanded +.I arg1 +and each expanded +.IR arg2 . +This is meant to make less work of +a message to several recipients on the same machine. +For example, the rule +.IP +.L +([^!]+)!(.+) | "uux - -a \\s \\1!rmail" \\2 +.LP +causes +.L mail r70!pjw r70!ken +to generate the single delivery command +.LR "uux -a rob r70!rmail pjw ken" . +.SH EXAMPLES +A sample rewrite file: +.PP +.EX +.ta \w'([^!]+)[%@]([^!@%]+) 'u +\w'alias 'u +# local mail +[^!@%]+ translate "exec translate '&'" +local!([^!@%]+) >> /usr/spool/mail/\e1 +\el!(.+) alias \e1 +.EE +.PP +.EX +# convert %@ format to ! format +(_822_)!((.+)!)?([^!]+)[%@]([^!%@]+) \e + alias \e1!\e2\e5!\e4 +([^!]+)[%@]([^!@%]+) alias _822_!\e2!\e1 +_822_!(.+) alias \e1 +.EE +.PP +.EX +# special domains +[^!]+wisc\e.edu!.+ alias xunet!& +.EE +.PP +.EX +# network gateways +(csnet|bitnet)!(.+) alias inet!& +acsnet!.+ +.EE +.PP +.EX +# real networks +inet!([^!]+)!(.+) | "/usr/lib/upas/route.inet '\es' '\e1'" "'\e2'" +([^!]+)!(.+) | "/usr/lib/upas/route '\es' '\e1'" "'\e2'" +.EE +.PP +.EX# anything else goes to research +.* alias research!& +.EE +.SH FILES +.TF /n/bowell/usr/lib/upas/mkfile +.TP +.F /usr/lib/upas/namefiles +list of files to search +.TP +.F $HOME/lib/names +private aliases +.TP +.F /usr/lib/upas/rewrite +rewriting rules +.TP +.F /usr/lib/upas/attlist +known AT&T machines +.TP +.F /usr/lib/upas/gateways +machines that check mail authorization reliably +.TP +.F /usr/lib/upas/translate +alias lookup +.TP +.F /usr/lib/upas/route.* +mail interfaces to specific networks +.TP +.F /usr/lib/upas/route +interface to local (i.e. AT&T) Datakit network +.TP +.F /bin/mail +shell file that calls the mailer +.TP +.F /usr/lib/upas/send +actually delivery program +.TP +.F /bin/rmail +linked to /usr/lib/upas/send +.TP +.F /usr/spool/mail/* +mailboxes +.TP +.F /usr/spool/mail/mail.log* +delivery logs +.TP +.F /n/bowell/usr/lib/upas/mkfile +updates various mail and uucp files +.TP +.F /etc/passwd +authentication +.TP +.F /tmp/ma* +temp file +.TP +.F /tmp/ml* +lock file +.TP +.F $HOME/dead.letter +unmailable text +.SH "SEE ALSO" +.IR uucp (1), +.IR mail (1), +.IR mail (6), +.IR smtp (8) +.br +D. L. Presotto and W. R. Cheswick, +`Upas\(ema simpler approach to network mail', +this manual, Volume\ 2 diff --git a/static/v10/man8/update.8 b/static/v10/man8/update.8 new file mode 100644 index 00000000..a670606c --- /dev/null +++ b/static/v10/man8/update.8 @@ -0,0 +1,25 @@ +.th UPDATE VIII 11/1/73 +.sh NAME +update \*- periodically update the super block +.sh SYNOPSIS +.bd update +.sh DESCRIPTION +.it Update +is a program that executes +the +.it sync +primitive every 30 seconds. +This insures that the file system +is fairly up to date in case of a crash. +This command should not be executed directly, +but should be executed out of the +initialization shell command file. +See sync(II) for details. +.sh "SEE ALSO" +sync(II), init(VII) +.sh BUGS +There is a system bug which, it is suspected, +may be aggravated by this program. +Until further notice, +.it update +should not be run. diff --git a/static/v10/man8/uucico.8 b/static/v10/man8/uucico.8 new file mode 100644 index 00000000..ba88daa7 --- /dev/null +++ b/static/v10/man8/uucico.8 @@ -0,0 +1,205 @@ +.TH UUCICO 8 +.CT 1 sa_auto +.SH NAME +uucico, uusched, uuxqt, kick, debug \- uucp file transport and execution +.SH SYNOPSIS +.B /usr/lib/uucp/uucico +[ +.B -r1 +.B -s +.I system +] +[ +.B -x +.I debug +] +[ +.B -d +.I spool_directory +] +.PP +.B /usr/lib/uucp/uusched +[ +.B -x +.I debug +] +[ +.B -u +.I debug +] +.PP +.B /usr/lib/uucp/kick +.I system +.PP +.B /usr/lib/uucp/debug +.I system +.PP +.B /usr/lib/uucp/uuxqt +[ +.B -s +.I system +] +[ +.B -x +.I debug +] +.SH DESCRIPTION +.I Uucico +transfers files between systems +for +.IR uucp (1). +It is normally invoked by +.I login +for +an incoming connection +(a slave), +or by +.IR uusched +to call out to another system +(a master). +The options are +.TP \w'\f5-s\ \fIsystem\ 'u +.B -r1 +This is a master; +option +.B -s +is required. +In the absence of +.B -r1 +the process is a slave and expects to speak to a master on +standard input and standard output. +.TP \w'\f5-s\ \fIsystem\ 'u +.BI -s " system +Call the named +.I system. +.TP +.BI -x " debug +Turn on debugging output; +.I debug +is a single digit, larger for more output. +.ig +.PP +For example, +the shell +.I Uutry +starts +.I uucico +with debugging turned on. +.. +.PP +.I Uusched +invokes +.I uucico +for each system +with work pending. +It is called by +.IR uucp +and +.IR uux (1) +after work is queued, +and should be invoked regularly by +.IR cron (8). +The options are +.TP \w'\f5-s\ \fIsystem\ 'u +.BI -x " debug +As for +.I uucico. +.TP +.BI -u " debug +Invoke +.I uucico +with option +.B -x +.I debug. +.PP +.I Kick +invokes +.I uucico +in the background +to call out to the specified +.IR system . +.I Debug +causes a call with +a moderate amount +of debugging output +.RB ( -x4 ). +Both attempt to remove +existing system status information +for +.IR system , +so that a call will be attempted +regardless of recent failures. +.PP +.I Uuxqt +executes commands requested remotely by +.IR uux (1). +It searches the +.I uucp +spool directories looking for +filenames starting with +.BR X. , +checks the +.I Permissions +file to see that all required data files are available +and accessible +and that the requested command is permitted for the +requesting system, +and invokes the command if all is well. +.PP +Before a command is invoked, +the file creation mask +.RI ( umask (2)) +is set to 0 and these +environment variables are set: +.TF UU_MACHINE +.TP +.B UU_MACHINE +the name of the last sending machine +.TP +.B UU_USER +the user that sent the job +.TP +.B PATH +set to +.LR /bin:/usr/bin +.TP +.B USER +set to +.L uucp +.PD +.SH FILES +.TF /usr/lib/uucp/Maxuuscheds +.TP +.F /usr/lib/uucp/Systems* +.TP +.F /usr/lib/uucp/Permissions +.TP +.F /usr/lib/uucp/Devices +.TP +.F /usr/lib/uucp/Maxuuscheds +how many copies of +.I uusched +may be active at once +.TP +.F /usr/lib/uucp/Maxuuxqts +ditto for +.I uuxqt +.TP +.F /usr/spool/uucp/* +.TP +.F /usr/spool/uucppublic/* +.TP +.F /usr/spool/uucp/LCK* +.fi +.SH "SEE ALSO" +.IR uucp (1), +.IR uux (1), +.IR uustat (1) +.br +D. A. Nowitz, +`UUCP Administration', +this manual, Volume 2 +.SH BUGS +System and user names received by +.I uuxqt +should not be believed. diff --git a/static/v10/man8/uucleanup.8 b/static/v10/man8/uucleanup.8 new file mode 100644 index 00000000..650af0d7 --- /dev/null +++ b/static/v10/man8/uucleanup.8 @@ -0,0 +1,103 @@ +.TH UUCLEANUP 8 +.CT 1 sa_auto +.SH NAME +uucleanup \- uucp spool directory clean-up +.SH SYNOPSIS +.B /usr/lib/uucp/uucleanup +[ +.I options +] +.SH DESCRIPTION +.I Uucleanup\^ +removes old files from the +.I uucp +spool directories. +It is typically called by +.FR /usr/lib/uucp/uudemon.cleanu , +which may be run regularly by +.IR cron (8). +The options are: +.TF -mstring +.TP +.BI -C days\^ +Remove +.B C. +(control) files that are at least +.I days +old, +and send a message to the user who queued the job. +.PD +.TP +.BI -D days\^ +Remove +.B D. +(data) files that are at least +.I days +old. +If the data file appears to contain a mail message, +an attempt will be made to deliver it; +if it contains a netnews article +from another system, +it will be handed to +.IR rnews . +.TP +.BI -W days\^ +Send a warning to the user who queued any jobs +.RB ( C. +files) +at least +.I days +old. +If one of the data files for the job appears to be a mail message, +the message is included in the warning. +.TP +.BI -X days\^ +Remove any +.B X. +(remote execution) files at least +.I days +old. +.TP +.BI -m string\^ +Include +.I string +in warning messages. +The default is +`See your local administrator to locate the problem.' +.TP +.BI -o days\^ +Remove any other files +that are at least +.I days +old. +.TP +.BI -s system\^ +Examine only files associated with +.IR system . +.PP +By default, +.B C. +files generate a warning when +one day old, +and are removed after 7 days; +.B D. +files are removed after 7 days; +and +.B X. +and other files +are removed after 2 days. +.SH FILES +.TF /usr/spool/uucp +.TP +.F /usr/lib/uucp +directory with commands used by +.I uucleanup +.TP +.F /usr/spool/uucp +spool directory +.SH SEE ALSO +.IR uucp (1) +.br +D. A. Nowitz, +`UUCP Administration', +this manual, Volume 2 diff --git a/static/v10/man8/uurec.8 b/static/v10/man8/uurec.8 new file mode 100644 index 00000000..38dae752 --- /dev/null +++ b/static/v10/man8/uurec.8 @@ -0,0 +1,18 @@ +.TH UUREC 8 +.SH NAME +uurec \- receive processed news articles via mail +.SH SYNOPSIS +uurec +.SH DESCRIPTION +.I uurec +reads news articles on the standard input sent by +.I sendnews(8), +decodes them, and gives them to +.I inews(1) +for insertion. +.SH SEE ALSO +inews(1), +readnews(1), +recnews(8), +sendnews(8), +newscheck(1) diff --git a/static/v10/man8/vipw.8 b/static/v10/man8/vipw.8 new file mode 100644 index 00000000..05f46458 --- /dev/null +++ b/static/v10/man8/vipw.8 @@ -0,0 +1,23 @@ +.TH VIPW 8 +.UC 4 +.SH NAME +vipw \- edit the password file with vi +.SH SYNOPSIS +.B vipw +.SH DESCRIPTION +.I Vipw +edits the password file while setting the appropriate locks, +and does any necessary processing after the password file is unlocked. +If the password file is already being edited, then you will be told +to try again later +.SH SEE ALSO +chfn(1), chsh(1), passwd(1), passwd(5), adduser(8) +.SH FILES +/etc/vipw.lock +.SH BUGS +.I Vipw +does not remove the vipw.lock file; this is not a bug, but people tend +to think it is. +.PP +No one deals with left-over /etc/ptmp (the real lock) files after a system +crash. diff --git a/static/v10/man8/vmstat.8 b/static/v10/man8/vmstat.8 new file mode 100644 index 00000000..dd267fb0 --- /dev/null +++ b/static/v10/man8/vmstat.8 @@ -0,0 +1,143 @@ +.TH VMSTAT 8 +.CT 1 sa_mortals +.SH NAME +vmstat \- report virtual memory statistics +.SH SYNOPSIS +.B vmstat +[ +.B -st +] +[ +.I interval +[ +.I count +] +] +.SH DESCRIPTION +.I Vmstat +reports statistics about certain system activity. +.ig x +Option +.B -f +reports on +.I forks +since system startup and the number of pages of virtual memory involved. +.x +Option +.B -s +prints totals for miscellaneous events +since the last boot. +Option +.B -t +reports on paging events. +.PP +In the absence of other options, the optional +.I interval +argument causes +.I vmstat +to report once each +.I interval +seconds, repeated +.I count +times or forever. +.PP +The default format fields are: +.TF faults +.TP +.B procs +information about numbers of processes in various states: +.RS +.PD 0 +.TP +.B r +in run queue +.TP +.B b +blocked for resources (I/O, paging, etc.) +.TP +.B w +runnable or short sleeper (< 20 secs) but swapped +.RE +.PD +.TP +.B memory +use of virtual and real memory: +.RS +.PD 0 +.TP +.B avm +number of +pages belonging to processes that have run +in the last 20 seconds +.TP +.B fre +size of memory free list +.RE +.PD +.TP +.B page +paging activity, +averaged each five seconds, in units per second: +.RS +.PD 0 +.TP +.B re +page reclaims (simulating reference bits) +.TP +.B at +text pages recovered from memory +.TP +.B pi +page-in events +.TP +.B po +page-out events +.TP +.B fr +pages freed per second +.TP +.B de +anticipated short term memory shortfall +.TP +.B sr +scan rate: pageout daemon rpm +.RE +.PD +.TP +.B faults +trap rates, averaged each five seconds, in units per second: +.RS +.PD 0 +.TP +.B sy +system calls +.TP +.B cs +process context switches +.RE +.PD +.TP +.B cpu +percentage use of CPU time: +.RS +.PD 0 +.TP +.B us +user time, both normal and low priority +.TP +.B sy +system time +.TP +.B id +cpu idle time +.TP +.B st +stream queue processing time +.RE +.PD +.SH FILES +.F /dev/kmem +.br +.F /unix +.SH BUGS +This program is never up to date. diff --git a/static/v10/man8/vpac.8 b/static/v10/man8/vpac.8 new file mode 100644 index 00000000..6acf1fce --- /dev/null +++ b/static/v10/man8/vpac.8 @@ -0,0 +1,49 @@ +.TH VPAC 8 2/21/80 +.UC 4 +.SH NAME +vpac \- print raster printer/ploter accounting information +.SH SYNOPSIS +.B /etc/vpac +[ +.B \-W +] [ +.B \-s +] [ +.B \-r +] [ +.B \-t +] [ name ... ] +.SH DESCRIPTION +.I Vpac +reads the raster printer/plotter accounting files, accumulating the number +of pages (for narrow fan-fold devices) or feet (for wide, roll paper devices) +of paper consumed by each user, and printing out +how much each user consumed in pages or feet and dollars (billed at +2 cents / page or 8 cents / foot). If any +.I names +are specified, then statistics are only printed for those users; +usually, statistics are printed for every user who has used any paper. +.PP +The +.B \-W +flag causes accounting to be done for a wide roll paper device. The default is +to do accounting for a narrow, fan-fold device. +The +.B \-t +flag causes the output to be sorted by feet of paper; usually the +output is sorted alphabetically by name. The +.B \-r +flag reverses the sorting order. +The +.B \-s +flag causes the accounting information to be summarized on the +summary accounting file; this summarization is necessary since on a +busy system, the accounting file can grow by several lines per day. +.SH FILES +.ta 2i +/usr/adm/v?acct raw accounting files +.br +/usr/adm/v?_sum summary accounting files +.SH BUGS +The relationship between the computed price and reality is +as yet unknown. diff --git a/static/v10/man8/wall.8 b/static/v10/man8/wall.8 new file mode 100644 index 00000000..57918100 --- /dev/null +++ b/static/v10/man8/wall.8 @@ -0,0 +1,23 @@ +.TH WALL 8 +.CT 1 sa_nonmortals +.SH NAME +wall \- write to all users +.SH SYNOPSIS +.B /etc/wall +.SH DESCRIPTION +.I Wall +reads its standard input until an end-of-file. +It then sends this message, +preceded by +`Broadcast Message ...', +to all logged in users. +.PP +The sender should be super-user to override +any protections the users may have invoked. +.SH FILES +.F /etc/utmp +.SH "SEE ALSO" +.IR write (1) +.SH DIAGNOSTICS +`Cannot send to ...' when the open on +a user's tty file fails. diff --git a/static/v10/man8/worm.8 b/static/v10/man8/worm.8 new file mode 100644 index 00000000..004f4a05 --- /dev/null +++ b/static/v10/man8/worm.8 @@ -0,0 +1,436 @@ +.TH WORM 8 "wild" +.CT 1 sa_nonmortals +.SH NAME +worm, jukebox \- optical disk utilities +.SH SYNOPSIS +.B "worm mkfs" +[ +.BI -f device +] [ +.BI -c comments +] [ +.BI -b blksz +] [ +.BI -n nblks +] [ +.BI -v newvol_id +] +.I vol_id +.PP +.B "worm stat" +[ +.BI -f device +] [ +.BI -F n +] [ +.B -v +] [ +.I vol_id +] +.PP +.B "worm ls" +[ +.BI -f device +] [ +.B -l +] [ +.I file ... +] +.PP +.B "worm rm" +[ +.BI -f device +] +.I vol_id +[ +.I file ... +] +.PP +.B "worm mv" +[ +.BI -f device +] +.I vol_id +.I "src dest" +.PP +.B "worm write" +[ +.BI -f device +] +.I vol_id +[ +.I file ... +] +.PP +.B "worm read" +[ +.BI -f device +] [ +.B -dm +] +.I vol_id +[ +.I file ... +] +.PP +.B "worm cat" +[ +.BI -f device +] +.I vol_id +.I file +.PP +.B "worm copy" +[ +.B -v +] [ +.BI -m min_free +] [ +.BI -f src_dev +] +.I src_vol_id +.I dest_dev +.I dest_vol_id +.PP +.B "worm offline" +[ +.BI -f device +] +.PP +.B "worm btree" +[ +.BI -f device +] +.I vol_id +.PP +.B "worm dir" +[ +.BI -f device +] +.I vol_id +.PP +.B "worm tmpdir" +[ +.BI -f device +] +.I vol_id +.PP +.B "worm mount" +[ +.BI -w secs +] [ +.I vol_id +] +.PP +.B "jukebox" +[ +.B -aemprsuU +] [ +.BI -w secs +] [ +.I vol_id +] +.SH DESCRIPTION +The +.I worm +programs manipulate arbitrary files. +They are intended for use with the raw device associated +with a Write-Once Read-Many (WORM) optical disk. +The default device is +.FR /dev/worm0 . +Other devices are specified by +.BI -f device +and a device name of a single digit +.I n +is taken as an abbreviation for +.FR /dev/worm \f2n\fP. +Most of the commands implement a simple file system. +Programs just wanting a raw device should still use +.B "worm mkfs" +so that the disk is properly labeled. +The +.IR vol_id , +or label, +should be unique and by convention, the vol_id's +for the A and B sides of a disk should be the same string suffixed by +a lowercase +.B a +and +.B b +respectively. +.PP +.I "Worm mkfs" +labels an optical disk. +The +.I comments +field is limited to 256 chars. +It is purely descriptive and is printed by +.IR "worm stat \-v" . +The (default) blocksize is 1024 for our SONY disks. +The number of blocks on a disk can be found by +.IR ra (4) +or +.IR scsish (8); +the default size +(1,600,000 for single density, 3,250,000 for double density) +sets aside 30MB or so as a hedge against oversights. +If the disk has already been initialised, its vol_id must match +.IR vol_id . +A new vol_id can be set with +.BR -v . +.PP +.I "Worm stat" +prints out labeling information +including the amount of free space left on the disk. +Option +.I vol_id +turns off all output except exit status: zero if +.I vol_id +matches that of the disk, +one otherwise. +Option +.B -F +similarly exits with status zero if the disk has more than +.I n +free blocks, otherwise three. +Option +.B -v +produces more output. +.PP +.I "Worm ls" +simulates an emasculated +.IR ls (1). +.PP +.I "Worm rm" +makes the specifed files unavailable to the rest of the +.I worm +commands. +.PP +.I "Worm mv" +renames +.I src +to +.IR dest . +.PP +.I "Worm write" +copies files onto the WORM. +If no file arguments are given, +filenames are read one per line from standard input. +The total number of files and bytes is printed on standard output. +.PP +.I "Worm read" +restores files from the WORM. +If no file arguments are given, +filenames are read one per line from standard input. +Option +.B -d +causes directories to be created as needed. +Option +.B -m +restores the original modification times. +.PP +.I "Worm cat" +copies the named file from the WORM to the standard output. +.PP +.I "Worm copy" +copies files directly from one disk to another. +The names of the files to be copied are taken from standard input; +groups (separated by blank lines) will be kept together. +The names are typically generated by +.BR "worm ls" . +The +.B -v +option prints out progress and summary information. +The copy will terminate before copying a group that would leave the destination +volume with less than +.I minfree +(deafult value is 40000) blocks free. +.PP +.I "Worm offline" +makes the WORM go offline, ready for ejecting. +This command is harmless; +accessing an offline drive will cause it to spin up and go online +without operator intervention. +.I "Worm offline" +only takes effect after the last close of the WORM +and as a bonus, applies to any MSCP device such as an RA81. +.PP +.I "Worm tmpdir" +saves a copy of the directory in +.BI /usr/worm/tmp/ vol_id +if the directory +.F /usr/worm/tmp +exists. +This will speed up subsequent access substantially, +although it will still be slower than +.I "worm btree" +below. +On the other hand, +.I worm tmpdir +typically takes 5 minutes to run (on a VAX 11/750) +whereas +.I worm btree +takes about 45 minutes. +.PP +.I "Worm btree" +constructs a new directory for the whole disk (in the form of a +.IR cbt (1) +database). +The new superblock is at zero. +All the worm commands go faster with such an index but it is intended to be done +just once, after the disk is complete. +The directory occupies of the order of 10MB but may be more. +If you really have to add more files to the disk, +you need to write zeros on the first 1K block of the WORM before using +.IR "worm write" . +.PP +.I "Worm dir" +takes the btree directory from the disk and stores in +.FR /usr/worm/dirs . +Future uses of the disk will be much faster. +.PP +.I "Worm mount" +returns the device on which the disk labelled +.I vol_id +is mounted. +If the drive(s) are busy and you have a jukebox, the +.BI -w s +option tells how many seconds to wait before failing. +The default is wait forever. +If no +.I vol_id +is given, print the drive status. +.PP +.I "Jukebox" +manages the disks in the SONY jukebox. +There are several options (default is +.BR -s ): +.TP 10 +.B -a +Allocate a blank disk and label it +.IR vol_id . +Use +.I "worm mkfs" +to change any fields from their default value. +.TP +.B -e +Eject the disk labeled +.I vol_id. +To physically retrieve the disk, +press the +.B OUT +button (the +.B "OUT READY" +light should be on). +Repeat until the +.B "IN READY" +light goes on. +.TP +.B -m +Mount the disk labelled +.I vol_id +in some drive and print the drive number on standard output. +.TP +.B -p +Print the list of disks in the jukebox. +.TP +.B -r +Rebuild the list of disks by examining each disk in the jukebox. +Do not do this unless you are sure you need to. +If +.I vol_id +is given, it should be one of the following letters and governs +how disks are assigned shelf numbers. +The default is to leave the shelf number unchanged. +Other options (mainly useful for demos) are +.B c +(compresses the disks in the jukebox towards the bottom or lower numbered shelves), +.B r +(distributes the disks randomly), and +.B s +(sorts the disks by vol_id). +.TP +.B -s +Print the status of the jukebox. +.TP +.B -u +Unload offline disks back onto their shelves. +.TP +.B -U +Unload all disks (offline or not) back onto their shelves. +.TP +.BI -w secs +This option only affects the behavior of +.BR -m . +If all drives are busy, try again for +.I secs +seconds before failing. +.PP +To load a disk into the jukebox, press the +.B IN +button on the jukebox when the +.B "IN READY" +light is on. +After the shutter opens, push the disk in firmly. +The disk (blank or initialised) is not examined immediately but on demand. +.SS Etiquette +Vol_ids should be unique as discussed above. +The file +.F /n/wild/usr/worm/vol_ids +contains known vol_ids. +The commands for reading and writing require vol_id's +to guard against accessing the wrong disk. +.PP +The recommended protocol for changing disks is +if no one appears to be using the drive +(by using +.IR ps (1)), +execute +.I "worm offline" +and go to the drive. +If, and only if, the drive has the DRIVE OFF (middle) light on, +hit the EJECT button and change disks. +If the light is not on, then +someone is still using the disk and you should wait until they are done +before hitting EJECT. +.SS Programming considerations +Programs should not depend on writing any block more than once; however, +our SONY optical disks implement a small number of multiple writes +via bad block replacement. +A +.IR read (2) +of an unwritten block returns with an errno of +.BR ENXIO . +On Vaxes, the WORM is an MSCP device; +thus geometry information can be fetched as in +.IR ra (4). +.PP +For maximum speed, read and write in large blocks (preferably 63K) +and avoid seeks. +A seek across the whole disk takes about 1 second. +.PP +The device +.F /dev/worm? +is simply an appropriate raw +.IR ra (4) +device, partition 7 (the whole disk). +.SH EXAMPLES +.EX +worm mkfs -c"512x512x24 movies" tdmoviesa +worm write tdmoviesa < filenames +worm read -d tdmoviesa bumblebee/act2/frame1 +.EE +.SH FILES +.F /dev/worm? +.br +.F /n/wild/usr/worm/vol_ids +.br +.F /n/wild/usr/worm/jukedir +.SH SEE ALSO +.IR backup (8), +.IR scsish (8), +.IR backup (1) +.SH BUGS +The output of +.I "worm ls" +is not necessarily sorted. diff --git a/static/v10/man8/xs.8 b/static/v10/man8/xs.8 new file mode 100644 index 00000000..7c7339d2 --- /dev/null +++ b/static/v10/man8/xs.8 @@ -0,0 +1,63 @@ +.TH XS 8 +.CT 1 sa_nonmortals +.SH NAME +xs \- checksums +.SH SYNOPSIS +.B xs +[ +-s +] +[ +-k +.I keystring +] +[ +-f +.I official-list +] +.IR file ... +.SH DESCRIPTION +.I Xs +computes and reports +checksums of named files, +one report per line, in the form +.IP +filename s1 s2 s3 s4 +.LP +where the checksum comprises four groups of four hex digits each. +The checksum algorithm may be perturbed by specifying a +.I keystring +argument. +The +.B -s +argument causes the file's mode, label, owner and group +to enter into the checksum calculation. +.PP +The +.B -f +argument causes +.I xs +to verify checksums of files against +values +given +in the +.I official-list +file, which has the format of the output of an earlier +.I xs +run: +lines consisting of +one file name followed by four groups of hex digits per line. +Text after a +.L # +sign is ignored. +.PP +The checksum algorithm used is meant to be secure: to create a file +whose checksum agrees with that of another given file is very difficult. +.SH EXAMPLES +.EX +xs -s `find /bin -print` | xs /dev/stdin +.EE +.IP +This should return a different value if +.B /bin +changes in any way. diff --git a/static/v10/man8/xstr.8 b/static/v10/man8/xstr.8 new file mode 100644 index 00000000..681f2e2f --- /dev/null +++ b/static/v10/man8/xstr.8 @@ -0,0 +1,108 @@ +.TH XSTR 8 +.CT 1 prog_c +.SH NAME +xstr \- preprocessor for sharing strings in C programs +.SH SYNOPSIS +.B xstr +[ +.B -c +] +[ +.B - +] +[ +.I file +] +.SH DESCRIPTION +.I Xstr +maintains a file +.F strings +into which strings in component parts of a large program are hashed. +These strings are replaced with references to this common area. +This serves to implement shared constant strings, most useful if they +are also read-only. +.PP +The command +.IP +.L +xstr -c name.c +.PP +will extract the strings from the named C source, replacing +string references by expressions of the form +.BI (&xstr[ number ]) +for some +.I number. +An appropriate declaration of +.I xstr +is prepended to the file. +The resulting C text is placed in the file +.BR x.c . +The strings from this file are placed in the +.F strings +data base if they are not there already. +Repeated strings and strings which are suffixes of existing strings +do not cause changes to the data base. +.PP +After all components of a large program have been compiled a file +.B xs.c +declaring the common +.I xstr +space can be created by running +.B xstr +with no arguments. +This +.B xs.c +file should then be compiled and loaded with the rest +of the program. +If possible, the array can be made read-only (shared) saving +space and swap overhead. +.PP +Without option +.BR -c , +creates files +.I x.c +and +.I xs.c +as before, but does not use or affect any +.F strings +file in the same directory. +.PP +It may be useful to run +.I xstr +after the C preprocessor if any macro definitions yield strings +or if there is conditional code which contains strings +which may not, in fact, be needed. +.I Xstr +reads from its standard input when the argument +.L - +is given. +An appropriate command sequence for running +.I xstr +after the C preprocessor is: +.IP +.EX +cc -E name.c | xstr -c - +cc -c x.c +mv x.o name.o +.EE +.SH FILES +.TF /tmp/xs* +.TP +.F strings +Data base of strings +.TP +.F x.c +Massaged C source +.TP +.F xs.c +C source for definition of array +.L xstr +.TP +.F /tmp/xs* +Temp file +.SH BUGS +If a string is a suffix of another string in the data base, +but the shorter string is seen first by +.I xstr +both strings will be placed in the data base, when just +placing the longer one there will do. |