9.S Uuxqt - Uucp Commagd Execution
9.10 Maintaining the System
This section indicates some events and files which must be maintained for the uucp system. Y w may do some maintenance with sheD command files, initiating the files with C'ronJ4b entries. Others wiD require manual modification. Some sample sheD files are given toward the end of this sectioo.
9-13
9.10.1 SEQF - sequence check &Ie
This file is sel up intheprog,am directory and COnlams an entry for each remote system with which you agree to perform conversation sequence checks. The initial enny is just the system name of the remote system. The first conversation will add two items to the line, the conversation count, and the dateltimc of the most reSCDl conversatioo.
These items wiU be updated with each conversation. If a &eqUCDCe cbect fails, the entry will have tobe adjusted.
U seofthis featurcis DDtrc:commend.
9.10.1 TM - tcmporU'J clata 6Ics
These files areaeated inthe spool directOl)' while files are being copied from a remote machine. Theiroameshavethc form
TM.pid.ddJ
where pidisa process-id andddd is a sequential three digit num~ starting at zero for each invocationof "",,;coaad inaemc .. ed fcreach &Ie received.
After the entire remCltC file is received. the Tlrl file is moved/copied to the requested destination. lfprocessing ilabmrmallytaminaled arthemovelcopy fails, the file will mnainin the spooIdiredOI)'.
The leftover files should beperiodicaDy removed; the l4IId«Jnprogram is useful in this regard. Thecommand
uuclean -pTM
removes aU 1M files older than three days.
9.10.3 LOG -
loa
airy filaI>\D'ing execution of programs, individual LOG files IR created in the spool directory with information about queued requests, caUs to remote systems, execution of IUU
commands and file copy resuhs. These files should beCmlbined into the LOGFlLEby using the rudog program. This program will put the new LOG files at the beginning of theexistingLOGFlLE. Thecommml
uuJos
performs the merge. Options are available to prim some or aU the log entries after the files are merged. The UXiFILE should be removed periodically since it iscopicd each time new LOG entries are put imothc file.
The LOG files are created initially with mode 0222. Ifthc program which creates the fileterminatesnormaDy,ilcbangesthemodelo0666. Abortedrunsmayleavethefiles with mode 0222 and the wJog program will not read or remove them. To remove them. either use "" , uuckan, or change the mode lO(XJ66 and let Uldog merge them with theWGFlLE.
9-14
9.10.4 STST - system status files
These Wes are create~ in the spool direClocy by the uuc;co program. They contain information of failures such as login. dialup or sequence check and wiD contain a talking status when to machines are conversing. The form of the file name is
STST.sys
where sys isthe rem<xe system name.
Fm- ordinary failures (dialup. login). the file will prevent repeated tries for about one hour. For sequence check failures. the We must bercmo'Yed befcweany future attempts to converse with that rcmOCC system.
If the file is left d-Je toanaboned run. it may contain a talking status. lnthiscase, the file must be removed before a conversalionis ananptcd.
'.10.5 LCK - led files
Lock files are created for each device in use (e.g. automatic calling unit) and each system conversing. This prevents duplicate conversations and multiple attempts to use the same devices. The form of the lock We name is
LCK .. str
where str is either a device or SYSlem name. The 6lesmay be left in the spool directory if runs abort. They will be ignored (reused) after a time of aboot 24 hours. When runs abort and calls are desired before the time limit. the tock files sbouldbe ImlOvecl.
'.10.6 CratiDg SheD Files
The uucp program will spool wort and attempt to start the uuc;co program. but the starting of uuc;co will sometimes fail. (No devices availabJe. login failures etc.).
Therefore. the uuc;co program should be periodically started. The command to start
uuc;co can be put in a sheD file with a command to merge WG files and started by a crontabentry on an hourly basis. The file could contain the commands
program luulog program luuclco -rJ
N<xethatthe-rloptionisrequiredtostantheuuc;coprograminMASTERmode.
Another shell fiJe may be set up on a daily basis to remove TM. ST. and LCK files and C. m-D. files fm-wort which can not be accomplished for reasons like bad phone number.loginchangesetc. AsbeUfilecontainingcommandslike
program luuclean -pTM -pC. -pD.
program luuclean -pST -pLCK -n12
can be used. Note the -nIl option causes the.rr and LCK files oldcrthan 12hours to bedeleted. Theabsenceofthe-noptionwiDuseathreedaytimelimit.
C)-IS
9.10.7 Defining LogiD Entries
One or more logins should be set up for UlK'p. Each of the JetcJ passwd entries should have programJuuc;co as the sheD to be executed (where program is the directory containing uwic"o). The login directory is not used, but if the system bas a special directory for use by the users for sending or receiving file. it should as the login entry.
The various logins are used in coqjuDction with the USERFILE to restrict file access.
Specifying the shell argumerllimits the login to the use of uucicoonly.
9.10.8
SettiDa
File ModesIt is suggested thal the OW'I'IQ and file modes of various program. aDd files be set as foDows.
The programs uucp, UIU • uucico, and UlUqt should be owned by the lIIICp login with the setuid bit set and only execute permissions (e.g. mode (4111). This wiD prevent outsiders from modifying the pogramsto get al a standard shell for the IUlt'p logins.
The L.sys. SQFfLE. and USERFILE files which arc put in the program direcIory should be owned by lbeuucp loainaDd set with mode 0400.