UUCP (BNU) Helpful Information

About this document
Related documentation
UUCP configuration files
Setting up UUCP
Phases of UUCP communication
Status messages and what to do about them
Parameters for chat scripts

About this document

This document is an aid to setting up UUCP (BNU) on your system. Basic Networking Utilities (BNU) is the AIX version of UNIX-to-UNIX Copy Program (UUCP). The terms BNU and UUCP are used interchangeably in this document.

The information in this document applies to AIX Versions 4.x.

UUCP configuration files

Description of files

The setup files for AIX UUCP are:

/usr/lib/uucp/Systems
/usr/lib/uucp/Devices
/usr/lib/uucp/Permissions
/usr/lib/uucp/Dialers
/usr/lib/uucp/Dialcodes
/usr/lib/uucp/remote.unknown
/usr/lib/uucp/Poll

The Systems file lists remote computers with which the local system can communicate using BNU. This information is used by the uucico program to connect to the various systems. Consider this file the database of systems to which your machine can connect.

The Devices file lists each device on the local system that can dial out using BNU. The fields for each device include type, location, and speed. Only dial-out connections use the Devices file.

The Permissions file is used to create security control, with limitations, over machines attempting to communicate with your machine.

The Dialers file lists modems used by BNU and specifies the initial handshaking necessary for modem, TCP/IP, and remote communications. The most common types of dialers are "Hayes", "direct", and "TCP".

The Dialcodes file makes standardized names for certain parts of a phone number. For example, if you frequently make calls to a certain area code in San Francisco, you could create the following Dialcodes entry: "SFO9,1415".

The remote.unknown file is a shell script. The BNU program executes this file when a remote computer that is not listed in the local Permissions file attempts to communicate with that local system.

The Poll file schedules the polling of passing systems. Its format is similar to crontab. Poll format is <site name>, a tab, and the hours in which to poll (0-23) separated by spaces. Example:

   POLLDEMO   0 1 2 3 4 5 19 20 21 22 23

Correlation of files

The following diagram shows an example of the Systems, Devices, and Dialers files and shows how they relate to each other.

Systems file:
             <system_name>  Any  v32ibm  9600  555-1111
                 _______________/
Devices file:   /
             v32ibm  tty0  -  Any      ibm   \D
               ______________________/
Dialers file: /
             ibm   =, -, #" \d ATSFI\r\c#OK#AFE1SD3L2MIC0SCI\r\c#OK...

NOTE: Information in man pages gives a complete description of these files. (For example, type man Systems)

Sample setup of configuration files

The following is a sample setup for a modem connection.

The Systems file: 
 Danny Any v32ibm 9600 9,15551111 "" \d\d\d\r in:--in: uucp word: uucp 
The Devices file:
      v32ibm tty0 - Any ibm \D
The Dialers file:
      
      ibm   =,-,    "" \dAT\r\c OK \pATDT\T\r\c CONNECT
The Permissions file:
      MACHINE=Danny REQUEST=yes READ=/ WRITE=/  COMMANDS=ALL
      LOGNAME=uucp REQUEST=yes SENDFILES=yes READ=/ WRITE=/

With the above setup you could test the connection. Enter:

cu -d Danny

The cu command connects to another system, and the -d gives extra debug information.

Setting up UUCP

This section contains steps for setting up UUCP on your system. It is divided into the following parts:

Part One: Ensure UUCP is installed
Part Two: Add administrative and machine logins
Part Three: Activate the cron daemon
Part Four: Set up the BNU configuration files

Part One: Ensure UUCP is installed

Run the following command to ensure UUCP is installed on your system:

	lslpp -h bos.net.uucp

If UUCP is installed, you will see the following in the output:

	bos.net.uucp

If you do not see the preceding output, you will need to install it from the install tape.

Part Two: Add administrative and machine logins

With the following steps, edit /etc/passwd, /etc/group, /etc/security/login.cfg, and /etc/security/passwd to add the uucpadm login and other logins.

In /etc/passwd, add a login with the same group and user ID as uucp. This will be helpful for several administrative tasks and for debugging. In addition, make the home directory /usr/lib/uucp, and ensure that the new user's shell is NOT /usr/lib/uucp/uucico.
The suggested entry in /etc/passwd is:
```
  uucpadm:!:5:5::/usr/lib/uucp:/bin/ksh
```
Add machine logins to /etc/passwd. You have the option of maintaining separate logins or having one login for all UUCP connections. If you do need to maintain complete control over access by each individual machine, you must create separate login IDs as well as combine the MACHINE and LOGNAME entries in the Permissions file. Here are a few examples from the /etc/passwd file:
```
Umicrtk:!:105:5:micrtk uucp:/usr/spool/uucppublic:/usr/lib/uucp/uucico
Ufloydl:!:106:5:floydl uucp:/usr/spool/uucppublic:/usr/lib/uucp/uucico
Uicus:!:107:5:icus uucp:/usr/spool/uucppublic:/usr/lib/uucp/uucico
Urisctkr:!:108:5::/usr/spool/uucppublic:/usr/lib/uucp/uucico
```
If you want to have one set of permissions and do not want to maintain separate control for any of your UUCP connections, you can have a single login for all machines, such as the following:
```
   nuucp:!:6:5::/usr/spool/uucppublic:/usr/lib/uucp/uucico
```
Field requirements: Notice that the user ID (the third colon separated field) is unique. It would be a security risk to have this ID be the same as another in the /etc/passwd file. The group ID (the fourth colon separated field) MUST be 5 - the same as group uucp. You can change the home directory (the sixth field) to any valid directory, but the login shell (the seventh field) MUST be /usr/lib/uucp/uucico.
Add the new logins to /etc/group. An example of an entry in /etc/group is:
```
uucp:!:5:uucp,uucpadm,nuucp,Umicrtk,Uicus,Urisctakr
```
You may want to add any logins to group uucp that will be using modems to dial out with programs other than cu.
Set up passwords for the logins. You must be logged on as root to do this. Type the following to set up the password for uucpadm.
```
   passwd uucpadm
```
Add the login shell of your UUCP logins (/usr/lib/uucp/uucico) to the list of shells in /etc/security/login.cfg. Look for the shells = stanza and append /usr/lib/uucp/uucico to the end of the list.
Modify the default herald in /u/security/login.cfg. Sometimes the default herald, with all of its control-Js, will cause a uucico process which is trying to log in to give up. (You may see the message Enough already.) You can avoid that by commenting out (with "*"s) the defport stanza and by defining a stanza for your tty; something like the example below.
```
   /dev/tty0:
   herald = "
risc001 login: "
```
You may need to change the flags in /etc/security/passwd. If you changed a password from the root login, the flags entry in the stanza for the user will contain the following:
```
  flags = ADMCHG
```
Change it to:
```
  flags =
```
Otherwise, when the remote uucico logs in, it will be prompted to enter a new password, which it cannot do. Hence the login will fail.

Part Three: Activate the cron daemon

Log in as uucpadm
Run the following command to gather the current crontab line entry for uucp into a temporary file:
```
  crontab -l > /tmp/cron.uucp
```

Next, edit /tmp/cron.uucp and uncomment the entries (take out the "#"s at the beginning of the lines). The entries should look similar to:

20,50 * * * * /bin/bsh -c "/usr/lib/uucp/uudemon.poll > /dev/null"
25,55 * * * * /bin/bsh -c "/usr/lib/uucp/uudemon.hour > /dev/null"
45 23 * * * /bin/bsh -c "/usr/lib/uucp/uudemon.cleanu > /dev/null"
48 8,12,16 * * * /bin/bsh -c "/usr/lib/uucp/uudemon.admin > /dev/null"

Entries can be changed to suit your needs.

Now, to install the new edited version into uucp's crontab. Enter:
```
  crontab /tmp/cron.uucp
```
Check to ensure that your changes took effect. Enter:
```
  crontab -l
```

Part Four: Set up the BNU configuration files

You can use the /usr/lib/uucp/uucpadm command to initially set up the files and edit them to suit your exact needs.

Phases of UUCP communication

UUCP error messages can be linked to specific phases in the conversation flow. Use the following diagram and the error descriptions in the following section to help you diagnose your UUCP problems. Some of the following messages may not be sent by the AIX version of UUCP (BNU), but they are included in case another UUCP version is in use on a different system platform.

                     U U C P   or   U U X
                              |
                              |
                            uucico
                              |
                              |
   PHASE 1:           System Verification
                              |
                              |
   PHASE 2:            Device Selection
                              |
                              |
   PHASE 3:           Link Establishment
                              |
                              |
   PHASE 4:             Login Sequence
                              |
                              |
   PHASE 5:    Data Transfer and File Execution
                              |
                              |
   PHASE 6:                Hangup

Status messages and what to do about them

The following messages are linked to specific phases in the conversation flow. See the diagram in the preceding section.

Phase 1 - System verification

Assert Error
Your system is having problems. Check the error report for possible causes. (To check the report, type errpt -a | pg.)
System not in Systems
If you supply a remote system name that is not found in the Systems file, this status message is returned. UUCP will terminate. Use the uuname command to check the system name again.
Wrong time to call
The Systems file has restrictions on times to allow outgoing calls. UUCP will keep trying until the time is right. Check the Systems file.
Callback required
The network has restricted usage for either security or economic reasons and access is denied at this time.
Cannot call or No call
UUCP recently tried to call the remote system and failed. It will not immediately try again.

Phase 2 - Device selection

Dialer Script Failed
The Dialers file script did not complete successfully.
No device available or Can't access device
The modem or the outgoing phone line from your system is busy. Check for an error in the device entry of the Systems file. Also, check the Devices and Dialers files to be sure logical devices have physical devices associated with them. Is the device in use by some other program? Check the /etc/locks directory for a lock on the port.
Dial Failed or Failed (call to system)
These messages appear when your system dials another system successfully but the other system does not answer. It may also indicate a problem in the Devices file.
Execute the command uucico -r1 -x6 -s<system name>. It could be that UUCP is expecting some string that it is not receiving. Make the connection by hand to find out what needs to be incorporated into the Systems file entry to satisfy the request. Please keep timing in mind; perhaps some delays are needed.
OK or Auto Dial
These messages are just for your information; they do not indicate a problem.

Phase 3 - Link establishment

Handshake Failed (LCK)
The device is being used by someone else; the process could not create the LCK file. Sometimes LCK files must be manually removed by the administrator. After a number of retries, see your system administrator.
Login Failed or Timeout
Login failed due to a bad connection or slow machine. Timeout indicates that the remote system did not respond within a set period of time.
Succeeded (Call to System) or BNU (continued)
These messages are just for your information; they do not indicate a problem.

Phase 4 - Login sequence

Startup Failed or Remote reject after login
After login, uucico is started on the remote system. If there is a problem in initiating a conversation between the two systems, these messages are created. You may also have logged in using the wrong UUCP account. Contact the site administrator.
Wrong machine name
Either you called the wrong machine or the machine's name was changed.
Bad login/machine combination
The login for the remote system failed. The problem could be a wrong phone number, login/password, or chat script.
Remote has a LCK file for me
The remote was trying to call at the same time, so your request has failed temporarily.
OK or Talking
These messages are just for your information; they do not indicate a problem.
The login or password prompt is in all capital letters.

Problem: The modem may be in "echo" mode (which is E1 on Hayes compatibles). This causes the modem to echo back or send a "ring" to your system when an incoming call is received. When getty receives the string, it changes the login: or password: into all capital letters.
Solution: Change the "echo" mode to off. (Use ATE0 for Hayes compatible modems.) Keep in mind that once this change is made you should use ATE1 in the Dialers file chat script. If you do not, you will not get the expected OK back from the modem.
Remote port is set for "delay" or "getty -r" and chat scripts expect keyboard input.

Problem: Ports set for "delay" are expecting one or more carriage returns before proceeding with the login.
Solution: Try beginning the chat script in the Systems file on the dialing system with the following (the first "..." represents the items on the line before the chat script and the second "..." represents the rest of the chat script):
```
   ... "" \r\d\r\d\r\d\r in:--in:  ...
```
(Interpreted, the preceding reads: expect nothing, send return, delay, return, delay, return, delay, and return.)

Phase 5 - Data transfer and file execution

Alarm
uucico is having trouble with the connection. Either the connection is bad or "xon/xoff" is set to yes on the modem.
Remote access to path/file denied or Copy (failed)
These messages indicate a permission problem; check the file and path permissions.
Bad read
The remote system ran out of space (probably in the spool area).
Conversation failed
The modem is powered off, a cable is pulled or loose, the system crashed, or lightning struck and disrupted the connection or hardware.
Requested or Copy (succeeded)
These messages are just for your information; they do not indicate a problem.

Phase 6 - Hangup

OK (Conversation Complete)
The remote computer can deny the hangup request and reverse the roles (meaning the remote has work for the local system to do). Once both local and remote uucico, programs agree that no more work exists, they hang up.
Conversation succeeded
These messages are just for your information; they do not indicate a problem.

Parameters for chat scripts

A chat script is a login sequence - a list of expect-send sequences that a modem uses to establish a link with another modem. Chat scripts reside in the Systems file.

The following table is a list of parameters which can be edited into the chat scripts in the Systems file. The parameters listed in this table are the only parameters recognized for chat scripts in AIX.

Parameter Description

"" Null string

\N Null character

\b Backspace character

\c Suppress carriage return which is sent at end of send string

\d Delay 2 seconds

\p Pause for approximately 1/4 second

\K Send a break

\n Newline character

\r Carriage return character

\s Space character

\t Tab character

\\ Backslash character

BREAK Generate break signal (approx. 1/4 second)

EOT Send Control-D newline Control-D newline

\ddd Send octal character

\E Turn echo check on

\e Turn echo check off

WAIT=n Change to "n" seconds the timeout while waiting for the
next expect string (default is 45 sec)

Parameter	Description
""	Null string
\N	Null character
\b	Backspace character
\c	Suppress carriage return which is sent at end of send string
\d	Delay 2 seconds
\p	Pause for approximately 1/4 second
\K	Send a break
\n	Newline character
\r	Carriage return character
\s	Space character
\t	Tab character
\\	Backslash character
BREAK	Generate break signal (approx. 1/4 second)
EOT	Send Control-D newline Control-D newline
\ddd	Send octal character
\E	Turn echo check on
\e	Turn echo check off
WAIT=n	Change to "n" seconds the timeout while waiting for the next expect string (default is 45 sec)

[ Doc Ref: 90605225614694 Publish Date: Oct. 16, 2000 4FAX Ref: 1909 ]