CHAT(8) System Manager's Manual CHAT(8) NAME chat - SYNOPSIS chat [ options ] script DESCRIPTION chat (pppd) pppd OPTIONS -f chat chat chat (mutually exclusive) (multiple lines) (horizontal tab) -t (expected string) (reply string) (alternate) chat -r Set the file for output of the report strings. If you use the keyword REPORT, the resulting strings are written to this file. If this option is not used and you still use REPORT keywords, the stderr file is used for the report strings. -e Start with the echo option turned on. Echoing may also be turned on or off at specific points in the chat script by using the ECHO keyword. When echoing is enabled, all output from the modem is echoed to stderr. -E Enables environment variable substituion within chat scripts using the standard $xxx syntax. -v chat (verbose) chat SYSLOG The default is to log through the SYSLOG; the logging method may be altered with the -S and -s flags. -V Request that the chat script be executed in a stderr verbose mode. The chat program will then log all text received from the modem and the output strings sent to the modem to the stderr device. This device is usually the local console at the station running the chat or pppd program. -s Use stderr. All log messages from '-v' and all error messages will be sent to stderr. -S Do not use the SYSLOG. By default, error messages are sent to the SYSLOG. The use of -S will prevent both log messages from '-v' and error messages from being sent to the SYSLOG. -T Pass in an arbitary string, usually a phone number, that will be substituted for the \T substitution metacharacter in a send string. -U Pass in a second string, usually a phone number, that will be substituted for the \U substitution metacharacter in a send string. This is useful when dialing an ISDN terminal adapter that requires two numbers. script script -f chat CHAT SCRIPT chat (expect- send) (pairs of string) (subexpect- subsend)(dash) ogin:-BREAK-ogin: ppp ssword: hello2u2 chat "ogin:" (break sequence) "ogin:" "ogin:" chat ppp "ssword:" hello2u2 (carriage return) (character sequence) (expect sequence) (time strings) (network iden- tification strings) (initial sequence) "ogin:" "login:" "l" "ogin:" "login:" "ssword" "password:" ogin: ppp ssword: hello2u2 ...ogin:, ppp, ...ssword:, hello2u2 (sub- sequences) ogin:--ogin: ppp ssword: hello2u2 login: , (return sequence) login: login (empty line) COMMENTS Comments can be embedded in the chat script. A comment is a line which starts with the # (hash) character in column 1. Such comment lines are just ignored by the chat program. If a '#' character is to be expected as the first character of the expect sequence, you should quote the expect string. If you want to wait for a prompt that starts with a # (hash) character, you would have to write something like this: # Now wait for the prompt and send logout string '# ' logout SENDING DATA FROM A FILE If the string to send starts with an at sign (@), the rest of the string is taken to be the name of a file to read to get the string to send. If the last character of the data read is a newline, it is removed. The file can be a named pipe (or fifo) instead of a regular file. This provides a way for chat to communicate with another program, for example, a program to prompt the user and receive a password typed in. ABORT STRINGS CONNECTED NO CARRIER BUSY BUSY NO CARRIER ABORT ABORT BUSY ABORT 'NO CARRIER' '' ATZ OK ATDT5551212 CONNECT ATZ OK OK ADTD5551212 CONNECT CONNECT BUSY (abort char- acter) (abort string) (fail) NO CARRIER chat CLR_ABORT STRINGS This sequence allows for clearing previously set ABORT strings. ABORT strings are kept in an array of a pre-determined size (at compilation time); CLR_ABORT will reclaim the space for cleared entries so that new strings can use that space. SAY STRINGS The SAY directive allows the script to send strings to the user at the terminal via standard error. If chat is being run by pppd, and pppd is running as a daemon (detached from its controlling terminal), standard error will normally be redirected to the file /etc/ppp/connect-errors. SAY strings must be enclosed in single or double quotes. If carriage return and line feed are needed in the string to be output, you must explicitely add them to your string. The SAY strings could be used to give progress messages in sections of the script where you want to have 'ECHO OFF' but still let the user know what is happening. An example is: ABORT BUSY ECHO OFF SAY "Dialling your ISP...\n" '' ATDT5551212 TIMEOUT 120 SAY "Waiting up to 2 minutes for connection ... " CONNECT '' SAY "Connected, now logging in ...0 ogin: account ssword: pass $ SAY "Logged in OK ...0 etc ... This sequence will only present the SAY strings to the user and all the details of the script will remain hidden. For example, if the above script works, the user will see: Dialling your ISP... Waiting up to 2 minutes for connection ... Connected, now logging in ... Logged in OK ... REPORT STRINGS A report string is similar to the ABORT string. The difference is that the strings, and all characters to the next control character such as a carriage return, are written to the report file. The report strings may be used to isolate the transmission rate of the modem's connect string and return the value to the chat user. The analysis of the report string logic occurs in conjunction with the other string processing such as looking for the expect string. The use of the same string for a report and abort sequence is probably not very useful, however, it is possible. The report strings to no change the completion code of the program. These "report" strings may be specified in the script using the REPORT sequence. It is written in the script as in the following example: REPORT CONNECT ABORT BUSY '' ATDT5551212 CONNECT '' ogin: account This sequence will expect nothing; and then send the string ATDT5551212 to dial the telephone. The expected string is CONNECT. If the string CONNECT is received the remainder of the script is executed. In addition the program will write to the expect-file the string "CONNECT" plus any characters which follow it such as the connection rate. CLR_REPORT STRINGS This sequence allows for clearing previously set REPORT strings. REPORT strings are kept in an array of a pre-determined size (at compilation time); CLR_REPORT will reclaim the space for cleared entries so that new strings can use that space. ECHO The echo options controls whether the output from the modem is echoed to stderr. This option may be set with the -e option, but it can also be controlled by the ECHO keyword. The "expect-send" pair ECHO ON enables echoing, and ECHO OFF disables it. With this keyword you can select which parts of the conversation should be visible. For instance, with the following script: ABORT 'BUSY' ABORT 'NO CARRIER' '' ATZ OK\r\n ATD1234567 \r\n \c ECHO ON CONNECT \c ogin: account all output resulting from modem configuration and dialing is not visible, but starting with the CONNECT (or BUSY) message, everything will be echoed. HANGUP The HANGUP options control whether a modem hangup should be considered as an error or not. This option is useful in scripts for dialling systems which will hang up and call your system back. The HANGUP options can be ON or OFF. When HANGUP is set OFF and the modem hangs up (e.g., after the first stage of logging in to a callback system), chat will continue running the script (e.g., waiting for the incoming call and second stage login prompt). As soon as the incoming call is connected, you should use the HANGUP ON directive to reinstall normal hang up signal behavior. Here is an (simple) example script: ABORT 'BUSY' '' ATZ OK\r\n ATD1234567 \r\n \c CONNECT \c 'Callback login:' call_back_ID HANGUP OFF ABORT "Bad Login" 'Callback Password:' Call_back_password TIMEOUT 120 CONNECT \c HANGUP ON ABORT "NO CARRIER" ogin:--BREAK--ogin: real_account etc ... TIMEOUT 45 -t ATZ OK ATDT5551212 CONNECT TIMEOUT 10 ogin:--ogin: TIMEOUT 5 assword: hello2u2 "login:" 10 5 SENDING EOT EOT chat EOT (End-of- file) EOT (return) EOT ^D GENERATING BREAK BREAK \K ESCAPE SEQUENCES '' (null string) (apostrophe) \b (backspace) \c (newline) hello h, e, l, l, o \d sleep(1) \K (newline)(linefeed) \N (null character) \p 1/10 \q SYSLOG ?????? \r \s 'HI TIM' HI\sTIM \t (tab) \T Send the phone number string as specified with the -T option (not valid in expect.) \U Send the phone number 2 string as specified with the -U option (not valid in expect.)  (backslash) \ddd (ddd) (collapse) ASCII ^C C DC1(17) ^Q ENVIRONMENT VARIABLES Environment variables are available within chat scripts, if the -E option was specified in the command line. The metacharacter $ is used to introduce the name of the environment variable to substitute. If the substition fails, because the requested environment variable is not set, nothing is replaced for the variable. TERMINATION CODES The chat program will terminate with the following completion codes. 0 The normal termination of the program. This indicates that the script was executed without error to the normal conclusion. 1 One or more of the parameters are invalid or an expect string was too large for the internal buffers. This indicates that the program as not properly executed. 2 An error occurred during the execution of the program. This may be due to a read or write operation failing for some reason or chat receiving a signal such as SIGINT. 3 A timeout event occurred when there was an expect string without having a "-subsend" string. This may mean that you did not program the script correctly for the condition or that some unexpected event has occurred and the expected string could not be found. 4 The first string marked as an ABORT condition occurred. 5 The second string marked as an ABORT condition occurred. 6 The third string marked as an ABORT condition occurred. 7 The fourth string marked as an ABORT condition occurred. ... The other termination codes are also strings marked as an ABORT condition. Using the termination code, it is possible to determine which event terminated the script. It is possible to decide if the string "BUSY" was received from the modem as opposed to "NO DIAL TONE". While the first event may be retried, the second will probably have little chance of succeeding during a retry. SEE ALSO chat UUCP chat uucico uucico(1), uucp(1) COPYRIGHT The chat program is in public domain. This is not the GNU public license. If it breaks then you get to keep both pieces. [] asdchen [] 1995/09/30 linuxman: http://cmpp.linuxforum.net man man https://github.com/man-pages-zh/manpages- zh Chat Version 1.22 22 May 1999 CHAT(8)