Go forward to Log File Names.
Go backward to Miscellaneous (config).
Go up to config File.
Configuration File Names
------------------------
`sysfile STRINGS'
Specify the system file(s). The default is the file `sys' in the
directory NEWCONFIGDIR. These files hold information about other
systems with which this system communicates; see See sys File.
Multiple system files may be given on the line, and the `sysfile'
command may be repeated; each system file has its own set of
defaults.
`portfile STRINGS'
Specify the port file(s). The default is the file `port' in the
directory NEWCONFIGDIR. These files describe ports which are used
to call other systems and accept calls from other systems; see
See port File. No port files need be named at all. Multiple
port files may be given on the line, and the `portfile' command
may be repeated.
`dialfile STRINGS'
Specify the dial file(s). The default is the file `dial' in the
directory NEWCONFIGDIR. These files describe dialing devices
(modems); see See dial File. No dial files need be named at
all. Multiple dial files may be given on the line, and the
`dialfile' command may be repeated.
`dialcodefile STRINGS'
Specify the dialcode file(s). The default is the file `dialcode'
in the directory NEWCONFIGDIR. These files specify dialcodes that
may be used when sending phone numbers to a modem. This permits
using the same set of phone numbers in different area-codes or
with different phone systems, by using dialcodes to specify the
calling sequence. When a phone number goes through dialcode
translation, the leading alphabetic characters are stripped off.
The dialcode files are read line by line, just like any other
configuration file, and when a line is found whose first word is
the same as the leading characters from the phone number, the
second word on the line (which would normally consist of numbers)
replaces the dialcode in the phone number. No dialcode file need
be used. Multiple dialcode files may be specified on the line,
and the `dialcodefile' command may be repeated; all the dialcode
files will be read in turn until a dialcode is located.
`callfile STRINGS'
Specify the call out login name and password file(s). The default
is the file `call' in the directory NEWCONFIGDIR. If the call out
login name or password for a system are given as `*' (
see Logging In.), these files are read to get the real login name or
password. Each line in the file(s) has three words: the system
name, the login name, and the password. The login name and
password may contain escape sequences like those in a chat script
expect string (see Chat Scripts.). This file is only used
when placing calls to remote systems; the password file described
under `passwdfile' below is used for incoming calls. The
intention of the call out file is to permit the system file to be
publically readable; the call out files must obviously be kept
secure. These files need not be used. Multiple call out files
may be specified on the line, and the `callfile' command may be
repeated; all the files will be read in turn until the system is
found.
`passwdfile STRINGS'
Specify the password file(s) to use for login names when `uucico'
is doing its own login prompting, which it does when given the
`-e', `-l' or `-w' switches. The default is the file `passwd' in
the directory NEWCONFIGDIR. Each line in the file(s) has two
words: the login name and the password (e.g., `Ufoo foopas').
They may contain escape sequences like those in a chat script
expect string (see Chat Scripts.). The login name is accepted
before the system name is known, so these are independent of which
system is calling in; a particular login may be required for a
system by using the `called-login' command in the system file
(see Accepting a Call.). These password files are optional,
although one must exist if `uucico' is to present its own login
prompts.
As a special exception, a colon may be used to separate the login
name from the password, and a colon may be used to terminate the
password. This means that the login name and password may not
contain a colon. This feature, in conjunction with the
`HAVE_ENCRYPTED_PASSWORDS' macro in `policy.h', permits using a
standard Unix `/etc/passwd' as a UUCP password file, providing the
same set of login names and passwords for both `getty' and
`uucico'.
Multiple password files may be specified on the line, and the
`passwdfile' command may be repeated; all the files will be read in
turn until the login name is found.