uucico - Transfers uucp command, data, and execute files to remote systems
uucico [-r role_number] [-x debug_level] [-s system_name]
Valid values for role_number are: 1 for server mode and 0 (zero) for
client mode. The default is 0. If uucico is started manually, set
this option to 1.
Displays debugging information on the screen of the local terminal.
The valid range for debug_level is 0 to 9. The higher the number, the
more detailed the final report. This option is useful in correcting
problems with the expect_send sequence in the Systems file.
The name of the remote system. Use only when starting uucico manually.
The system_name is supplied internally when uucico is started automati-
Note that system names must contain only ASCII characters.
The uucico daemon transports uucp Command (C.*), Data (D.*), and Execute
(E.*) files that are created by the uucp and uux commands to a specified
remote system. Both the local and remote systems run the uucico daemon, and
the daemons on the two systems communicate with each other to complete
The uucico daemon performs the following actions:
+ Scans the spooling directory (/usr/spool/uucp/system_name) on the
local system for transfer requests.
+ Selects the device used for the communications connection after check-
ing the /usr/lib/uucp/Devices file and the lock files in the
+ Places a call to the specified remote system using information in the
Systems, Dialers, and Dialcodes files located in the /usr/lib/uucp
+ Performs the required login sequence specified in the Systems file.
+ Checks permissions listed in the /usr/lib/uucp/Permissions file.
+ Checks scheduling limits in the Maxuuscheds and Maxuuxqts files
located in the /usr/lib/uucp directory.
+ Runs all transfer requests from both the local and the remote system,
placing the transferred files in the public directories
+ Logs transfer requests and completions in files in the
+ Notifies specified users of transfer requests.
Usually the uucico daemon is called by the uucp and uux commands when
needed, and is started periodically by the uucp scheduling daemon, uusched,
which is started by the cron daemon.
The uucico daemon can be started from the command line for debugging. The
uucp command uutry also starts uucico with debugging turned on.
In the case of a uux command request for the execution of a command on a
remote system, the uucico daemon transfers the files, and the uuxqt daemon
executes the command on the remote system.
1. To start the uucico daemon from the command line as a background pro-
cess and contact the remote system hera, enter:
/usr/lib/uucp/uucico -r 1 -s hera &&
2. To debug uucico connections, start the uucico daemon with the -x
option, and enter:
/usr/lib/uucp/uucico -r 1 -s venus -x 9
The following environment variables affect the execution of uucico:
Specifies the flow control used on the connection. Permitted values
are: HW (hardware), SW (software), HSW (hardware and software), and
NONE. The uugetty on the remote system must also use the same flow con-
Specifies the amount of time (in seconds) for uucico to try to estab-
lish a connection before it times out. A value of 0 (zero) indicates
an unlimited amount of time.
Specifies the command path
Contains all the configuration files for uucp
Contains information about available devices
Contains dial-code abbreviations
Specifies initial handshaking on a link
Limits scheduled jobs
Limits remote command executions
Describes access permissions for remote systems
Describes accessible remote systems
Lists uucico daemon errors that uucp cannot correct
Contains uucico daemon log files
Lists the last time a remote system was contacted and the minimum time
until the next retry
Contains C.*, D.*, and E.* files to be transferred by the uucico daemon
Contains files after transfer by the uucico daemon
Contains lock files that prevent multiple uses of devices and multiple
calls to systems
Commands: uucp(1), uustat(1), uutry(1), uuto(1), uux(1), cron(8)