|Previous||Table of Contents||Next|
The /etc/uucp/Dialers file contains information that specifies the initial conversation that takes place on a line before it can be made available for transferring data. This conversation is usually a sequence of character strings that is transmitted and expected. The string often contains a telephone number that is dialed using an automatic call unit (ACU). Each entry in /etc/uucp/Dialers begins with a label identifying the type of the modem. The Solaris 2.x /etc/uucp/Dialers file contains support for many different modem types. Each type of caller included in the /etc/uucp/Devices file should be contained in the /etc/uucp/Dialers file except for built-in callers. You probably do not need to create an entry in this file. You do need to look in this file to verify that it contains an entry appropriate for your modem and to determine the type to use when you edit the /etc/uucp/Devices file.
Each line consists of three parts: the name of the caller, the table that translates the phone number into the code for the particular device, and a chat script to establish the connection. Comments at the beginning of the /etc/uucp/Dialers file explain the codes shown in the brief excerpt that follows:
penril =W-P \d > Q\c : \d- > s\p9\c )-W\p\r\ds\p9\c-) y\c : \E\TP > 9\c OK ventel--=&-% \r\p\r\c $ <K\T%%\r>\c ONLINE! vadic =K-K \ØØ5\p *-\ØØ5\p-*\ØØ5\p-* D\p BER? \E\T\e \r\c LINE develcon \pr\ps\c est:\ØØ7 \E\D\e \n\ØØ7 micom \s\c NAME? \D\r\c GO direct ########## # The following entry is for use with direct connections # using ttymon with the -b and -r options on both ends, # or the old uugetty with the -r option. ########## uudirect \r\d in:--in: # Rixon Intelligent Modem -- modem should be set up in the Rixon # mode and not the Hayes mode. # rixon =&-% \r\r\d $ s9\c )-W\r\ds9\c-) s\c : \T\r\c $ 9\c LINE # Hayes Smartmodem -- modem should be set with the configuration # switches as follows: # # S1 - UP S2 - UP S3 - DOWN S4 - UP # S5 - UP S6 - DOWN S7 - ? S8 - DOWN # hayes =,-, \dA\pTE1V1X1QØS2=255S12=255\r\c OK\r \EATDT\T\r\c CONNECT
The /etc/uucp/Devices file contains information for all of the devices that may be used to establish a link to remote systems. Provisions are made for several types of devices, such as ACUs, direct links, and network connections. You need to add an entry to the /etc/uucp/Devices file if you want to set up support for a bidirectional modem. Each entry in the Devices file has the following format:
type line line2 class dialer-token-pairs
The excerpt from the /etc/uucp/Devices file that follows shows the default:
TCP,et - - Any TCP - ACU cua/b - Any hayes Direct cua/b - Any direct
The type argument you supply when editing the /etc/uucp/Devices file is the name of the modem as displayed at the end of the entry from the /etc/ uucp/Devices file. It points to an entry in /etc/uucp/Dialers.
The SAF records port monitor behavior in the /var/saf/_log file. In addition, each ttymon port monitor has its own log file, /var/saf/pmtag/log, in which it records information, such as messages that it receives from sac and the services that it starts.
An example of the end of the /var/saf/_log file follows. This information shows that the system was rebooted three times and that the ttymon port monitor zsmon was started and enabled successfully each time.
oak% tail /var/saf/_log Mon Mar 15 14:23:12 1993; 199; port monitor <zsmon> changed state from STARTING to ENABLED Fri Mar 19 Ø9:43:18 1993; 199; *** SAC starting *** Fri Mar 19 Ø9:43:19 1993; 2Ø3; starting port monitor <zsmon> Fri Mar 19 Ø9:43:19 1993; 199; port monitor <zsmon> changed state from STARTING to ENABLED Wed Mar 24 15:24:24 1993; 437; *** SAC starting *** Wed Mar 24 15:24:25 1993; 443; starting port monitor <zsmon> Wed Mar 24 15:24:25 1993; 437; port monitor <zsmon> changed state from STARTING to ENABLED Thu Mar 25 2Ø:36:11 1993; 2Ø1; *** SAC starting *** Thu Mar 25 2Ø:36:12 1993; 2Ø8; starting port monitor <zsmon> Thu Mar 25 2Ø:36:13 1993; 2Ø1; port monitor <zsmon> changed state from STARTING to ENABLED oak%
Following is an example of the /var/saf/_log file from another system that has a listen tcp port monitor configured.
seachild% tail /var/saf/_log Wed Mar 24 12:Ø6:19 1993; 176; *** SAC starting *** Wed Mar 24 12:Ø6:2Ø 1993; 181; starting port monitor <tcp> Wed Mar 24 12:Ø6:2Ø 1993; 182; starting port monitor <zsmon> Wed Mar 24 12:Ø6:21 1993; 176; port monitor <zsmon> changed state from STARTING to ENABLED Wed Mar 24 12:Ø6:22 1993; 176; port monitor <tcp> changed state from STARTING to ENABLED Thu Mar 25 2Ø:47:44 1993; 177; *** SAC starting *** Thu Mar 25 2Ø:47:44 1993; 183; starting port monitor <tcp> Thu Mar 25 2Ø:47:45 1993; 184; starting port monitor <zsmon> Thu Mar 25 2Ø:47:45 1993; 177; port monitor <zsmon> changed state from STARTING to ENABLED Thu Mar 25 2Ø:47:46 1993; 177; port monitor <tcp> changed state from STARTING to ENABLED seachild%
|Previous||Table of Contents||Next|