Apache web server for windows - uucico also allows for some sort of conditional
uucico also allows for some sort of conditional execution. Let’s say the remote machine’s getty needs to be reset before sending a prompt. For this, you can attach a subchat to an expect string, set off by a dash. The sub- chat is executed only if the main expect fails, i.e., a timeout occurs. One way to use this feature is to send a BREAK if the remote site doesn’t display a login prompt. The following example gives a general-purpose chat script that should also work in case you have to press Enter before the login appears. The empty first argument, “”, tells UUCP to not wait for anything, but to continue with the next send string: “” \n\r\d\r\n\c ogin:-BREAK-ogin: vstout ssword: catch22 A couple of special strings and escape characters can occur in the chat script. The following is a partial list of characters legal in expect strings: “” The empty string. It tells uucico to not wait for anything, but to proceed with the next send string immediately. \t Tab character. \r Carriage return character. \s Space character. You need this to embed spaces in a chat string. \n Newline character. \\ Backslash character. On send strings, the following escape characters and strings are legal in addition to the above: EOT End of transmission character (^D). BREAK Break character. \c Suppress sending of carriage return at end of string. \d Delay sending for 1 second. \E Enable echo checking. This requires uucico to wait for the echo of everything it writes to be read back from the device before it can continue with the chat. It is primarily useful when used in modem chats (which we will encounter later). Echo checking is off by default. \e Disable echo checking. \K Same as BREAK. \p Pause for fraction of a second. Alternates Sometimes you want to have multiple entries for a single system, for instance if the system can be reached on different modem lines. With Taylor UUCP, you can do this by defining a so-called alternate.