+Each line is of the form
+.IP
+real-name\ \ alias-name
+.LP
+where
+.I real-name
+is the full, correct name for the host, and
+.I alias-name
+is the old or truncated name.
+.NH 2
+L.sys \- \*(Uu Systems File
+.LP
+Each entry in this file represents one system
+which can be called by the local uucp programs.
+The format for each entry is
+.IP
+system times caller class device/phone-number [login]
+.LP
+where;
+.RS
+.IP "system" 12
+is the hostname of the remote system.
+.IP times
+is a keyword-encoded string that indicates the days-of-the-week
+and times-of-day when the system may
+be called.
+For example \fBMoTuTh0800\-1730\fP would denote Monday, Tuesday,
+and Thursday, between 8 a.m. and 5:30p.m.
+.IP
+The day portion may be a list containing
+any of
+\fBSu\fP, \fBMo\fP, \fBTu\fP, \fBWe\fP, \fBTh\fP, \fBFr\fP, \fBSa\fP,
+or
+.B Wk
+for any week-day or
+.B Any
+for any day.
+.IP
+The time should be a range of times (as in \fB0800\-1230\fP).
+If no time portion is specified, any time
+of day is assumed to be acceptable for the call.
+.IP caller
+is one of the caller device-types listed in \fIL-devices\fP.
+.IP class
+is the line speed for the call (e.g., 300, 1200, 9600),
+plus an optional alphabetic prefix.
+Network devices use this field for the network port number.
+.IP phone
+is the the phone number to call (for \fBACU\fP devices) or the
+device filename.
+A phone number is made up of an optional
+alphabetic abbreviation and a numeric part.
+The abbreviation is one which appears in the
+.I L-dialcodes
+file (e.g. mh5900, boston995\-9980).
+.IP login
+is a script describing how to log in to the remote host.
+It is expressed as a series of
+fields and subfields in the format
+.IP "" 17
+expect\ \ send\
+[
+expect\ \ send
+]
+\ ...
+.IP "" 12
+where;
+.I expect
+is the string expected to be read and
+.I send
+is the string to be sent when the
+.I expect
+string is received.
+The
+.I send
+string is normally terminated with carriage-return;
+an empty
+.I send
+string will send only a carriage-return.
+.IP
+The expect field may be made up of subfields
+of the form
+.IP "" 17
+expect\fB[\fR\-send\-expect\fB]\fR...
+.IP "" 12
+where the
+.I send
+is sent if the prior
+.I expect
+is not successfully read
+and the
+.I expect
+following the
+.I send
+is the next expected string.
+.RE
+.LP
+A typical entry in the L.sys file would be
+.IP "" 6
+sys\ Any\ ACU\ 1200\ \ mh7654\ login:--login:\ uucp\ ssword:\ word
+.LP
+The expect algorithm looks at the last part of the
+string as illustrated in the password field.
+.NH 2
+L.cmds \- Commands Permissions File
+.LP
+This file contains a list of commands, one per line, that are permitted
+for remote execution via \fIuux\fP.
+This list should be chosen with great care, since commands that take filenames
+as arguments will allow users to easily circumvent \*(Uu's security.
+For most sites,
+.I L.cmds
+should only include the lines:
+.DS
+rmail
+ruusend
+.DE
+.NH 2
+SQFILE \- Sequence Check File (Optional)
+.LP
+This file contains an entry for each remote
+system with which this site agrees to perform conversation
+sequence checks.
+The initial entry is just the system name of
+the remote system.
+The first conversation will add two items to the line,
+the conversation count, and the date/time of the most
+resent conversation.
+These items will be updated with each conversation.
+If a sequence check fails, which could indicate that an unauthorized
+connection has been attempted, the entry will have to
+be adjusted.
+.LP
+This facility is technically no longer supported in 4.3BSD \*(Uu,
+since it was hardly ever used and consumed precious memory space on PDP-11
+systems.
+The compile-time #define GNXSEQ can be set to enable sequence checking
+should it be needed.
+.NH 2
+USERFILE \- Pathnames Permissions File
projects / unix-history / blobdiff