[ Pobierz całość w formacie PDF ]
.This isan optional file, and if you want to use conversation counts, you must create it in /usr/lib/uucp.SQFILE must be owned by uucp, and have a file mode of 400.For this to work,SQFILE has an entry in it for each file that your system wants to have conversation checkswith.The remote system must also be configured to use SQFILE.When the file is created, edit it to include the names of the files you want to monitor, onesystem per line.After the first call, uucico adds the number of conversations, and the date andtime of the last contact.When one system calls another, uucico compares the SQFILE information on the two systems.If they don t agree, the login fails.The log files on the calling system will then add a messageindicating an SEQ number problem.To correct this, the two system administrators must gettogether and correct the files manually.Log FilesThe log files on V2 are quite different from HDB log files.Unlike HDB, all of the log entriesare placed into a single file in /usr/spool/uucp, appropriately named LOGFILE.A second fileexists called SYSLOG, which records the actual amount of data transferred and the time ittook to do it.The LOGFILE will grow continually.If you are running short of disk space, thisis the first place to check. 138 Part I: Managing Internet SecurityAn entry from LOGFILE looks like this:user system date/time commentroot unilabs (2/12-5:42) NO (AVAILABLE DEVICE)root unilabs (2/12-5:42) FAILED (call to unilabs )root unilabs (2/12-5:59) QUEUED (C.unilabsn0297)root unilabs (2/12-5:59) QUEUED (C.unilabsn0298)root unilabs (2/12-5:59) SUCCEEDED (call to unilabs )root unilabs (2/12-5:59) HANDSHAKE FAILED (LOGIN)unilabs unilabs (2/12-18:35) OK (startup)In the next few entries, you can see that the files /tmp/spool and /tmp/sys were sent to unilabs.Files that are sent show in a REQUEST entry with an S followed by the name of the file.root unilabs (2/12-18:35) REQUEST (S /tmp/spool ~ root)root unilabs (2/12-18:35) REQUEST (SUCCEEDED)root unilabs (2/12-18:35) REQUEST (S /tmp/sys ~ root)root unilabs (2/12-18:35) REQUEST (SUCCEEDED)root unilabs (2/12-18:35) OK (conversation complete)These log entries don t contain as much information as the log files in HDB, but fortunatelyyou have a second log file, SYSLOG, that can be examined for other important information.The SYSLOG file contains information of the actual transfer.The first few examples shownhere indicate that this machine received data from the remote machine, unilabs.user system date/time secs commentschare unilabs (11/21-22:56) (722404580) received data 148 bytes 2 secschare unilabs (11/21-22:56) (722404593) received data 1197 bytes 6 secschare unilabs (11/21-22:56) (722404601) received data 148 bytes 1 secsThese entries relate to the two files you saw transferred in the LOGFILE, namely /tmp/sys and/tmp/spool.These two files were sent from bugs to unilabs.root unilabs (2/12-18:35) (729560123) sent data 97 bytes 0 secsroot unilabs (2/12-18:35) (729560125) sent data 115 bytes 0 secsIt takes time to process and review logfile information.Consequently, an understanding of thisinformation is essential to the system troubleshooter.MaintenanceVersion 2 maintenance is simplified somewhat through the use of the uuclean command,which operates a lot like HDB.The uuclean command cleans up the UUCP spool directory(/usr/spool/uucp, typically) somewhat intelligently.For systems that cannot be reached, a mail Using UUCP 139message is sent back to the originator.uuclean works by deleting locally created rnews files,executing remotely created rnews files, and removing everything that shouldn t be there.The periodic removal of logfiles should also be performed to eliminate redundant UUCP loginformation and free up disk space.However, the original Version 2 UUCP implementationcannot perform this task automatically.Configuring UUCP over TCP/IPAlthough some feel that using the UUCP protocol over the TCP/IP transport is redundant, itcan be useful at times.If, for example, you have been using a Usenet news feed over UUCP,you can switch to a TCP/IP transport until you are ready to implement INN or some otherTCP/IP-based news server software using your existing implementation.UUCP use over TCP/IP is restricted to the Basic Networking Utilities, which are also known as HoneyDanBerUUCP.Two files need to be changed before TCP/IP can be used as the transport: the Systems andDevices files.Although the UUCP g protocol can be used, the UUCP e protocol is optimizedfor the transport characteristics of TCP/IP.The desired protocol type is included with thedevice identification.Because the UUCP g protocol has extensive error-checking built into it,it is considered to be a waste of resources when used with a high-speed connection such asTCP/IP.In this case, protocol e is often used.To define the protocol, follow the dataport witha comma and the protocol to use, as shown in the following example:TCPnet TCP,e.Aside from direct serial and modem connections, UUCP also supports connections over othertransports, such as TCP/IP and the Streams-based TLIS connections.Connections using theTLIS are not directly supported by all vendors of Unix.TLIS connections are configured in the Devices file.It is possible to configure TLIS to make aconnection with or without the Network Listener Service
[ Pobierz całość w formacie PDF ]