What to check if UUCP is abnormally slow
Because UUCP is a batching network, requests are not executed immediately.
Therefore, when users report that UUCP does not work,
the problem may be that the system is slow.
If the system is slower than usual, check for the following problems:
-
Check the spool directories,
/usr/spool/uucppublic and /usr/spool/uucp
for an overload of old work files and remove them.
-
Use
ps(C)
to verify that there are not too many
uucico processes going at once.
The limit to the number of communications
processes is specified in /usr/lib/uucp/Maxuuscheds
and /usr/lib/uucp/Maxuuxqts.
Check to see that the limit is not too high (the default is 1).
-
Make sure that the filesystem that contains the spool
directory is not out of space.
Refer to
``Maintaining free space in filesystems''
for more information.
-
The /usr/lib/uucp/uudemon.clean
script performs general cleanup by removing
old files that are trying unsuccessfully to execute.
To change the frequency of the cleanings, edit the
find statement in the uudemon.clean script.
Next topic:
What to do if UUCP works, but uux does not
Previous topic:
UUCP truncates system names to seven characters
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 03 June 2005