uucico [options]
The uucico daemon processes file transfer requests queued by
uucp and uux. It is started when uucp or
uux is run (unless they are given the `-r' or
`--nouucico' options). It is also typically started periodically
using entries in the `crontab' table(s).
When uucico is invoked with `-r1', `--master',
`-s', `--system', or `-S', the daemon will place a call
to a remote system, running in master mode. Otherwise the daemon will
start in slave mode, accepting a call from a remote system. Typically a
special login name will be set up for UUCP which automatically invokes
uucico when a remote system calls in and logs in under that name.
When uucico terminates, it invokes the uuxqt daemon,
unless the `-q' or `--nouuxqt' options were given;
uuxqt executes any work orders created by uux on a remote
system, and any work orders created locally which have received remote
files for which they were waiting.
If a call fails, uucico will normally refuse to retry the call
until a certain (configurable) amount of time has passed. This may be
overriden by the `-f', `--force', or `-S' options.
The `-l', `--prompt', `-e', or `--loop' options may
be used to force uucico to produce its own prompts of
`login: ' and `Password:'. When another uucico daemon
calls in, it will see these prompts and log in as usual. The login name
and password will normally be checked against a separate list kept
specially for uucico, rather than the `/etc/passwd' file
(see section Configuration File Names). It is possible, on some systems, to
configure uucico to use `/etc/passwd'. The `-l' or
`--prompt' options will prompt once and then exit; in this mode the
UUCP administrator, or the superuser, may use the `-u' or
`--login' option to force a login name, in which case uucico
will not prompt for one. The `-e' or `--loop' options will
prompt again after the first session is over; in this mode uucico
will permanently control a port.
If uucico receives a SIGQUIT, SIGTERM or
SIGPIPE signal, it will cleanly abort any current conversation
with a remote system and exit. If it receives a SIGHUP signal it
will abort any current conversation, but will continue to place calls to
(if invoked with `-r1' or `--master') and accept calls from
(if invoked with `-e' or `--loop') other systems. If it
receives a SIGINT signal it will finish the current conversation,
but will not place or accept any more calls.
Go to the first, previous, next, last section, table of contents.