CHAT 8

中文man手册

CHAT

NAME
æ»è§ SYNOPSIS
æè¿° DESCRIPTION
é项 OPTIONS
CHAT èæ¬ SCRIPT
COMMENTS
SENDING DATA FROM A FILE
æ¾å¼å符串 ABORT STRINGS
CLR_ABORT STRINGS
SAY STRINGS
REPORT STRINGS
CLR_REPORT STRINGS
ECHO
HANGUP
è¶æ¶ TIMEOUT
SENDING åé EOT
产ç䏿 GENERATING BREAK
转ä¹åºå ESCAPE SEQUENCES
ENVIRONMENT VARIABLES
TERMINATION CODES
åè§ SEE ALSO
COPYRIGHT
[䏿çç»´æ¤äºº]
[ä¸æçææ°æ´æ°]
ãä¸å½linux论åmanæåç¿»è¯è®¡åã:
è·

NAME

chat - 䏿°æ®æºèªå¨æ²éçæä»¤ç¨¿

æ»è§ SYNOPSIS

chat [ options ] script

æè¿° DESCRIPTION

chat ç¨å¼å¨çµè䏿°æ®æºä¹é´å®ä¹æ²é交æ¢äºå®ã 宿䏻è¦ç ç®çæ¯ç¨æ¥å¨ç¹å¯¹ç¹åå®çéå½¢ç¨å¼ (pppd) 以åè¿ç«¯ç pppd ç¨åº ä¹é´å»ºç«è¿çº¿ã

é项 OPTIONS

-f <chat file>

ä» chat æ¡£æ¡è¯»å chat æä»¤ç¨¿ãè¿ä¸ªé项ç使ç¨ä¸ chat ç ä»¤ç¨¿åæ°äºæ¥(mutually exclusive)ã使ç¨èå¿é¡»å·æåå该 æ¡£æ¡ç读åæã卿¡£æ¡ä¸å许å¤çº¿(multiple lines)设å®ãåº è¯¥è¦ä»¥ç©ºç½ææ¯æ¨ªåå®ä½(horizontal tab)å忥åéå串ã

-t <timeout>

å¯¹äºæè¦æ¥æ¶çæå¾å串(expected string)设å®é¾æ¶éå¶ã 妿å¨è¯¥æ¶é´éå¶åæ²¡ææ¥æ¶å°è¯¥å串çè¯é£ä¹å°±ä¸éåºåå¤ å串(reply string)ã å¯ä»¥éåºä¸ä¸ªåé(alternate)çåå¤ æèå¦ææ²¡æåéçåå¤å- 串å该æä»¤ç¨¿å°ä¼å¤±è´¥ãä¸ä¸ªå¤±è´¥ çæä»¤ç¨¿å°ä¼ä½¿å¾ chat ç¨å¼ä»¥ä¸ä¸ªéé¶çé误ç ç»æã

-r <report file>

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 <phone number>

Pass in an arbitary string, usually a phone number, that will be substituted for the \T substitution metacharacter in a send string.

-U <phone number 2>

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

\d

å»¶è¿ä¸ç§éã该ç¨å¼ä½¿ç¨æé¿å»¶è¿ä¸ºä¸ç§ç sleep(1) ãï¼å¨ æå¾å- 䏲䏿 æãï¼

\K

æå¥ä¸ä¸ªä¸æï¼å¨æå¾å䏲䏿 æãï¼

\n

éåºä¸ä¸ªæ°å(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 <asdchen@pc2.hinet.net>

[ä¸æçææ°æ´æ°]

1995/09/30

ãä¸å½linux论åmanæåç¿»è¯è®¡åã:

http://cmpp.linuxforum.net

è·

æ¬é¡µé¢ä¸æçç±ä¸æ man æå页计åæä¾ã
䏿 man æå页计åï¼https://github.com/man-pages-zh/manpages-zh