Книга: Linux Network Administrator Guide, Second Edition
Troubleshooting
This section describes what may go wrong with your UUCP connection and makes location suggestions to fix the error. Although these problems are encountered on a regular basis, there is much more that can go wrong than what we have listed.
If you have a problem, enable debugging with -xall, and take a look at the output in Debug in the spool directory. The file should help you to quickly recognize the problem. It is often helpful to turn on the modem's speaker when it doesn't connect. With Hayes-compatible modems, you can turn on the speaker by adding ATL1M1 OK to the modem chat in the dial file.
The first check should always be whether all file permissions are set correctly. uucico should be setuid uucp, and all files in /usr/lib/uucp, /var/spool/uucp, and /var/spool/uucppublic should be owned by uucp. There are also some hidden files in the spool directory which must be owned by uucp as well.[104]
When you're sure you have the permissions of all files set correctly, and you're still experiencing problems, you can then begin to take error messages more literally. We'll now look at some of the more common errors and problems.
- Troubleshooting Runlevel Problems
- Troubleshooting Connection Problems
- Troubleshooting DNS
- Troubleshooting Problems in Zone Files
- Tools for Troubleshooting
- Troubleshooting storage spaces
- Auditing and troubleshooting DHCP
- VI3 Monitoring and Troubleshooting Best Practices
- Troubleshooting Build Issues
- Troubleshooting Thread Synchronization Issues
- Parameter problem
- Problems loading modules