uucico(1M) uucico(1M)
NAME
uucico - file transport program for the uucp system
SYNOPSIS
/usr/lib/uucp/uucico [options]
DESCRIPTION
The uucico command is the file transport program for uucp work
file transfers.
Files
/etc/uucp/Systems
/etc/uucp/Permissions
/etc/uucp/Devices
/etc/uucp/Devconfig
/etc/uucp/Sysfiles
/etc/uucp/Limits
/var/spool/uucp/*
/var/spool/locks/*
/var/spool/uucppublic/*
USAGE
The following options are available.
-ctype The first field in the Devices file is the ``Type''
field. The -c option forces uucico to only use
entries in the ``Type'' field that match the user
specified type. The specified type is usually the
name of a local area network.
-dspool_directory
This option specifies the directory spool_directory
that contains the uucp work files to be transferred.
The default spool directory is /var/spool/uucp.
-f This option is used to ``force execution'' of uucico
by ignoring the limit on the maximum number of
uucicos defined in the /etc/uucp/Limits file.
-iinterface
This option defines the interface used with uucico.
The interface only affects slave mode. Known
interfaces are UNIX (default), TLI (basic Transport
Layer Interface), and TLIS (Transport Layer
Interface with Streams modules, read/write).
Copyright 1994 Novell, Inc. Page 1
uucico(1M) uucico(1M)
-rrole_number
The role_number 1 is used for master mode.
role_number 0 is used for slave mode (default).
When uucico is started by a program or cron,
role_number 1 should be used for master mode.
-ssystem_name
The -s option defines the remote system
(system_name) that uucico will try to contact. It
is required when the role is master; system_name
must be defined in the Systems file.
-xdebug_level
Both uux and uucp queue jobs that will be
transferred by uucico. These jobs are normally
started by the uusched scheduler, for debugging
purposes, and can be started manually. For example,
the shell Uutry starts uucico with debugging turned
on. The debug_level is a number between 0 and 9.
Higher numbers give more detailed debugging
information.
If you need to use this option, you must first make
sure that the Connection Server (cs) is in debug
mode. To see if cs is in debug mode, enter
ps -eaf | grep cs
If you don't see output similar to the following:
root 236 1 0 June 08 ? 0.01 /usr/sbin/cs -x
you must kill the current cs process and restart cs
with the -x option by entering:
/usr/sbin/cs -x
To turn off cs debugging, you must kill the cs
process that is running the debug mode, and restart
cs normally.
REFERENCES
cron(1M), uusched(1M), Uutry(1M) uucp(1C), uustat(1C), uux(1C)
Copyright 1994 Novell, Inc. Page 2