|
|
| Previous | Table of Contents | Next |
A wide variety of programs and even troubleshooting can benefit from the use of the log files. They are not only a source of debugging information, but also a valuable resource in tracking connect times to other systems, and lists of files that have been sent and received.
Now that you have UUCP running, you need to maintain it. Log files constantly consume disk space. Unless they are cleaned out on some type of schedule, they will expand to fill your hard disk. To prevent this, usually a crontab file is supplied for the uucp owner. A sample uucp crontab file is shown in the following:
Here are some sample UUCP crontab entries that are used to start the various UUCP maintenance commands, that were described earlier. 45 23 * * * ulimit 5000; /bin/su uucp -c “/usr/lib/uucp/uudemon.cleanup” > /dev/ null 2>&1 41,11 * * * * /usr/lib/uucp/uudemon.hour > /dev/null 0,15,30,45 * * * * /usr/lib/uucp/uudemon.poll > /dev/null
The shell scripts uudemon.poll, uucleanup, uudemon.cleanu, and uudemon.hour are provided by Unix vendors to help the system administrator maintain his or her UUCP system. Each of these programs is called at various intervals to perform specific maintenance tasks.
The uudemon.poll program looks at the Poll file, as shown in the following, to determine what, if any, systems should be called:
# Lines starting with # are ignored. # NOTE a tab must follow the machine name gateway 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 thumper 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 wabbit 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
If a system should be called, this program schedules a dummy job to “fake” uucico into thinking that there is work to be done. This is primarily used to “poll” other UUCP systems that do not regularly call your system.
The uucleanup program, typically started by uudemon.cleanup, cleans up the UUCP spool directory (/usr/spool/uucp typically) somewhat intelligently. For systems that cannot be reached, a mail message is sent back to the originator. uucleanup works by deleting locally created rnews files, executing remotely created rnews files, and removing everything that shouldn’t be there. A number of options are used to alter the processing done by uucleanup. Unfortunately, each version of uucleanup is different, and you will be forced to check your vendor’s documentation for your version’s methods.
The uustat command enables the user or the system administrator to obtain various statistics on how the UUCP system is operating. This command can also be used to cancel individual UUCP jobs by using the -k option. To kill UUCP jobs with the uustat command, you must know the UUCP job number, and be the owner of the job, or root.
choreoN90cf 02/08-09:09 S choreo chare 27332 D.unila96b2919
02/08-09:09 S choreo chare rmail chare
# uustat -kchoreoN90cf
Job: choreoN90cf successfully killed
What uustat will not do is cancel all requests or cancel multiple UUCP jobs based on a user or a system.
Version 2 UUCP is not as common since BNU (Basic Networking Utilities) and HoneyDanBer UUCP were introduced, although it still can be found on some older versions of Unix.
Version 2 UUCP was the first commercial release of UUCP that was included in Unix. It was used widely within AT&T and other organizations until the Basic Networking Utilities were developed. Version 2 was the predominant version of UUCP shipped with the BSD Unix implementation for many years.
To determine if you have Version 2 UUCP, look in /usr/lib/uucp or /etc/uucp. If you find a file called L.sys, then you have Version 2 UUCP. If you find a file called Systems, then you have the Basic Networking Utilities.
Version 2 UUCP has a directory structure similar to that of HDB UUCP, with the majority of differences at the file level. Table 3.7 depicts the file layout seen in a typical version 2 implementation.
| Directory and File | Description | |
|---|---|---|
| /bin | Contains the cu command. Note that this command is in a different place than HDB. | |
| /usr/bin | Contains the user commands. Keep in mind that many Version 2 UUCP sites do not have the uuencode and uudecode commands. Commands in this directory include the following: | |
| uucp | * job scheduler | |
| uulog | * show UUCP log files | |
| uuname | * get UUCP names | |
| uupick | * pick files | |
| uustat | * get UUCP status | |
| uuto | * end files | |
| uux | * command execution | |
| uusub | * manage a UUCP sub-net work | |
| /usr/lib/uucp or /etc/uucp | The UUCP library and configuration file directory. | |
| L-devices | * device configuration | |
| L-dialcodes | * dialcode expansion file | |
| USERFILE | * security controls | |
| L.Cmds | * security controls | |
| L.sys | * calling system information | |
| L_stat, R_stat | \ statistics files used by the uustat command | |
| L_sub, R_sub | \ traffic statistics used by the uusub command | |
| uucheck | * check configuration files | |
| uucico | * transfer program | |
| uusched | * UUCP job scheduler | |
| uuxqt | * remote execution program | |
| uuclean | * administration support command | |
Now that you know the differences between Version 2 UUCP and BSD, configuring Version 2 UUCP should be easier.
To use Version 2 UUCP, the following files must be configured for a minimal UUCP network. These files must be configured before you can initiate a call to a remote system using either cu or uucico.
L.sys L-devices USERFILE L.cmds
| Previous | Table of Contents | Next |