Error processing request

Parameters

CONTENT_LENGTH0
REQUEST_METHODGET
REQUEST_URI/revision/Expect?V=176
QUERY_STRINGV=176
CONTENT_TYPE
DOCUMENT_URI/revision/Expect
DOCUMENT_ROOT/var/www/nikit/nikit/nginx/../docroot
SCGI1
SERVER_PROTOCOLHTTP/1.1
HTTPSon
REMOTE_ADDR172.70.42.126
REMOTE_PORT28892
SERVER_PORT4443
SERVER_NAMEwiki.tcl-lang.org
HTTP_HOSTwiki.tcl-lang.org
HTTP_CONNECTIONKeep-Alive
HTTP_ACCEPT_ENCODINGgzip, br
HTTP_X_FORWARDED_FOR3.88.60.5
HTTP_CF_RAY86b9a9a1bf653b2c-IAD
HTTP_X_FORWARDED_PROTOhttps
HTTP_CF_VISITOR{"scheme":"https"}
HTTP_ACCEPT*/*
HTTP_USER_AGENTclaudebot
HTTP_CF_CONNECTING_IP3.88.60.5
HTTP_CDN_LOOPcloudflare
HTTP_CF_IPCOUNTRYUS

Body


Error

Unknow state transition: LINE -> END

-code

1

-level

0

-errorstack

INNER {returnImm {Unknow state transition: LINE -> END} {}} CALL {my render_wikit Expect {** Summary **

'''Expect''', by [Don Libes], is known primarily as an indispensable application for
system administrators.  Amazingly enough, it is, at its heart, Just Another
[Tcl] Extension (JATE).


** Use Cases **

[LV]:  Our local public library used to have a telnet interface to its patron
account system.  I wrote an Expect script which logged onto the system, queried
for the holdings status of each account in my family, then logged off.  I would
run this from [cron] and get a report as to which books were coming up for
return, what items were held for pick up, and so on.  I then placed the text
version of that report into a directory where a daily sync to my Palm Pilot
would result in a PalmOS memo containing this info.

** Description **

People use Expect to automate interaction with non-[GUI] (and typically
non-cursor-controlled, even though a persevering Expect programmer can tackle
them, too) applications that prompt the user for input.

Examples of commands that often appear in Expect scripts are the [Unix] passwd,
[ftp], [telnet], [ssh], [sudo], and command-line shells.  Expect is the natural
answer for those who want to automate password changes, periodically update FTP
sites, manage Cisco routers, or check the statuses of a collection of remote
systems by logging in.

======none
What: Expect
Where: http://expect.sf.net/
       http://expect.nist.gov/
       http://expect.nist.gov/FAQ.html
       http://expect.nist.gov/scripts/
       ftp://ftp.nist.gov/mel/div826/subject/expect/
       http://prdownloads.sf.net/expect/slavedrv1.1.zip
       http://phaseit.net/claird/comp.lang.tcl/expect.html
Description: Expect is a scripting language to interace with programs
        such as FTP, telnet, fsck, and others that normally cannot be
        automated from a shell script. Think of it as providing the means
        to 'remote control' other programs. It is thus also good for
        automating program exection on remote systems, and providing the
        means to creating Tk interfaces on top of other, non-GUI, programs
        V5.x is Tcl 7.x compatible. 
        The version on liv, while not from the author, is a set of source 
        modified to be used with tclX, BLT, and [TkSteal] (unmaintained). 
        V5.28 (the tar.gz version) is Tcl 8.0 compatible. 
        This package will also build expectk, which allows one 
        to write Tk interfaces to the above types of programs.
        The version at berkeley is a release of Expect for Windows NT,
        which includes patches to Tcl to allow fileevent to work 
        for pipes and serial ports. It does not work for Windows 95. 
        Check its web page for info on the latest development snapshots.
        The url for a version of Expect 5.25/Tcl 7.6 for Japanese Tcl 
        is mentioned above.
        The slavedrv code mentioned above is an attempt to port 
        a recent version of expect to recent version of Windows. 
        It may not have all the expect functionality.
        Version 5.44.1 of Expect, compatible with Tcl 8.5, 
        is also available from the SF.net CVS repository.
Updated: 8/2009
Contact: See the web sites 
===

The current Expect code was written to pre-7.5 standards, so until someone
steps forward to modernize the code base, should be treated gently.  It is not
multi-interp-safe, to say nothing about threads.

** Obtaining **

The current maintenance of the package can be found at
[http://expect.sf.net/%|%expect.sf.net] , with access to the CVS available via
sf.net's cvs repository.

Expect is part of the [ActiveTcl] Batteries Included distribution on Unix
and as of 2005, the Windows version is available via ActiveTcl as well
[http://blogs.activestate.com/activestate/2005/09/expect_for_wind.html].


** Documentation **

   [http://www.tcl.tk/man/expect5.31/index.html%|%man pages]:   
   [http://expect.sourceforge.net/FAQ.html%|%FAQ]:   
   [BOOK Exploring Expect]:   the bible of the Expect world
   [http://expect.nist.gov/%|%official website]:   supplies sources and considerable history, background, and instruction.  It does fail to mention, though, recognition of Expect as one of [http://nvl.nist.gov/pub/nistpubs/sp958-lide/cntsp958.htm%|%the 100 most important publications] of [NIST]'s first century.  Note that the warning regarding expect 5.44 on that page is seriously out of date.  The CVS 5.44 version linked to below is fine (and needed to build against Tcl 8.5).


** External Resources **

   [Expect External Resources]:   gives pointers to some wiki-external Expect material
   [http://phaseit.net/claird/comp.lang.tcl/expect.html%|%Expect references of interest to Cameron Laird]:   some notes by [CL]


** Tools **
   
   [http://expect-lite.sourceforge.net/%|%expect-lite]:   Written in expect, it is designed to directly map an interactive terminal session into an automation script

** Examples **

See [Expect Examples]


** See Also **

   [Expect FAQ]:   
   [Expect Hints and Tips]:   
   [Expect Tutorials]:   
   [Debugging Expect programs]:   
   [Remote input-output with Expect]:   
   [Secure expect]:   
   [Expect for languages other than Tcl]:   
   [Most programmers don't know what Expect can do for them]:   
   [I am new to Expect]:   
   [Event-oriented Expect]:   
   [Expect vs. Tcl]:   
   [Network programming with Expect]:   
   [Expect and Tclkit]:   
   [Expect and choice]:   
   [It seems like Expect is not actively developed]:   
   [overlay]:   
   [handling of ANSI terminals using Expect]:   
   [send special characters]:   
   [Stubsification of Expect]:   
   [An example wherein Expect controls a pager]:   
   ["expect_out(buffer) has the content of the previous send"]:   
   [Calc_Object]:   
   [How Expect can capture the exit code from a remote command]:   
   [Expect for Windows]:   
   [Expect for languages other than Tcl]:   
   [Checking your IMAP mail with Expect]:   
   [How to access the result of a remote command in Expect]:   
   [Many people who think they need Expect do not need Expect]:   
   [Expect's frequently-made mistakes]:   
   [How Expect sees function keys]:   
   [How to send escape characters through Expect]:   
   [Pipes vs Expect]:   
   [expectk]:   
   [expect in pure tcl]:   
   [expect4j]:   provides a certain level of expect's functionality to the [Jacl] / [Java] programmer.  Package author Justin Ryan reports on the [TclJava] [http://sourceforge.net/mailarchive/forum.php?thread_name=67e5f3da0711080735k4820242ascc219f87c52ac45d%40mail.gmail.com&forum_name=tcljava-user%|%mailing list]: ''I've successfully ported a 100K tcl script based on expect to tcljava, without any changes, by just using expect4j.''
   [How do I get the result of a remote command when I have to pass through a third host?]:   
   [Don't Expect to sleep]:   
   [How do I execute 'grep' on a remote machine and receive the result?]:   


** Articles **

   [http://www.nist.gov/customcf/get_pdf.cfm?pub_id=821282%|%Writing a Tcl Extension in Only Three, no Four, no Five, no 7 Years]:   Don Libes' memoir on the joys of writing "simple" tools to get stuff done.

   [http://www.drdobbs.com/expect-success/199101659%|%Expect Success], [CL%|%Cameron Laird] 2003:   is, for [Kim Richert], "the best Expect article I've read". [http://web.archive.org/web/20080804121417/http://www.samag.com/documents/s=7824/sam0310web1/sam0310web1.html%|%alternate]

   [http://www.ibm.com/developerworks/library/l-sc1/?n-l-4112%|%Expect Exceeds Expectations], [CL%|%Cameron Laird], 2002:   a short introduction with minimal examples [http://web.archive.org/web/20101201015029/http://www.ibm.com/developerworks/library/l-sc1/?n-l-4112%|%alternate]

   [http://www.drdobbs.com/expect-the-firefighters-friend/199101420%|%Expect: The Firefighter's Friend], [CL%|%Cameron Laird], 2002:   [http://web.archive.org/liveweb/http://www.drdobbs.com/expect-the-firefighters-friend/199101420%|%alternate]

   [http://web.archive.org/web/20070224042215/http://www.samag.com/documents/s=9035/sam0402web1/%|%Unknown Expect], [CL%|%Cameron Laird] ,2004-02:   seven little-known facts about expect that may help you use it more efficiently

   [http://www.drdobbs.com/test-driven-development-expect-and-syste/199101682%|%Test-driven Development, Expect, and Systems Administration], [CL%|%Cameron Laird] ,2003-12-15:   

   [http://web.archive.org/web/20071031081809/http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/expect/tutorial.html%|%Expect Tutorial]:   

   [http://web.archive.org/web/20061021184854/http://www.samag.com/documents/s=1180/sam9903c/9903c.htm%|%Using Expect to Configure Cisco Routers], Clay Lin ,1999:   "... the entire task would take about a month for two people ...  What used to take us a month now takes about an hour to finish completely and accurately."

   [http://www.ibm.com/developerworks/aix/library/au-expect/%|%Expect plays a crucial role in network management], Cameron Laird, 2007-07-31:   

   [http://www2.lib.uchicago.edu/keith/tcl-course/topics/expect.html%|%Expect], Keith Waclena ,1994:   a 5-minute tutorial

   [http://www.linuxjournal.com/article/3065%|%Automating Tasks with EXPECT] ,Vinnie Saladino ,1998:   


** Misc **

[LV]:  Note that '''expect''' is also a command that is a part of the expect
extension; see the expect source distribution for the doc.

[Lars H]:  Also note that in the latter sense, [expect] is a powerful control
structure (pretty much an [automaton], is it not?).

----

[srinadh] 2009-10-08 10:41:28: I have an expect program. Sometimes it produces
a core dump. How do I see core dump backtrace? Thanks

[AMG]: Use [gdb].

----

[susja] 2010-11-12 14:05:18: I have a simple task:  run autoexpect program to
automate telnet. I was able to do it on my Solaris box but I am stuck on my
Windows XP box.  Here's what I did:

   1. downloaded expect-5.43.tar to my local drive, untar it and have Expect located at C:\.... . I tried to execute 'autoexpect' but it says: "'autoexpect' is not recognized as an internal or external command"
   1. I installed ActiveTcl 8.5.9. Successfully ran 'teacup install Expect'.
   1. Here I'm blocked: how now I could execute autoexpect program?

thanks in advance
----

[bodangly] 2011-12-13 18:47:18: The above question is old and the user likely
found the answer however for reference, the PATH environment variable needs to
have the location of the autoexpect program appended to it.


<<categories>> Package | Expect | Command | System Administration | Control Structure | Unix} regexp2} CALL {my render Expect {** Summary **

'''Expect''', by [Don Libes], is known primarily as an indispensable application for
system administrators.  Amazingly enough, it is, at its heart, Just Another
[Tcl] Extension (JATE).


** Use Cases **

[LV]:  Our local public library used to have a telnet interface to its patron
account system.  I wrote an Expect script which logged onto the system, queried
for the holdings status of each account in my family, then logged off.  I would
run this from [cron] and get a report as to which books were coming up for
return, what items were held for pick up, and so on.  I then placed the text
version of that report into a directory where a daily sync to my Palm Pilot
would result in a PalmOS memo containing this info.

** Description **

People use Expect to automate interaction with non-[GUI] (and typically
non-cursor-controlled, even though a persevering Expect programmer can tackle
them, too) applications that prompt the user for input.

Examples of commands that often appear in Expect scripts are the [Unix] passwd,
[ftp], [telnet], [ssh], [sudo], and command-line shells.  Expect is the natural
answer for those who want to automate password changes, periodically update FTP
sites, manage Cisco routers, or check the statuses of a collection of remote
systems by logging in.

======none
What: Expect
Where: http://expect.sf.net/
       http://expect.nist.gov/
       http://expect.nist.gov/FAQ.html
       http://expect.nist.gov/scripts/
       ftp://ftp.nist.gov/mel/div826/subject/expect/
       http://prdownloads.sf.net/expect/slavedrv1.1.zip
       http://phaseit.net/claird/comp.lang.tcl/expect.html
Description: Expect is a scripting language to interace with programs
        such as FTP, telnet, fsck, and others that normally cannot be
        automated from a shell script. Think of it as providing the means
        to 'remote control' other programs. It is thus also good for
        automating program exection on remote systems, and providing the
        means to creating Tk interfaces on top of other, non-GUI, programs
        V5.x is Tcl 7.x compatible. 
        The version on liv, while not from the author, is a set of source 
        modified to be used with tclX, BLT, and [TkSteal] (unmaintained). 
        V5.28 (the tar.gz version) is Tcl 8.0 compatible. 
        This package will also build expectk, which allows one 
        to write Tk interfaces to the above types of programs.
        The version at berkeley is a release of Expect for Windows NT,
        which includes patches to Tcl to allow fileevent to work 
        for pipes and serial ports. It does not work for Windows 95. 
        Check its web page for info on the latest development snapshots.
        The url for a version of Expect 5.25/Tcl 7.6 for Japanese Tcl 
        is mentioned above.
        The slavedrv code mentioned above is an attempt to port 
        a recent version of expect to recent version of Windows. 
        It may not have all the expect functionality.
        Version 5.44.1 of Expect, compatible with Tcl 8.5, 
        is also available from the SF.net CVS repository.
Updated: 8/2009
Contact: See the web sites 
===

The current Expect code was written to pre-7.5 standards, so until someone
steps forward to modernize the code base, should be treated gently.  It is not
multi-interp-safe, to say nothing about threads.

** Obtaining **

The current maintenance of the package can be found at
[http://expect.sf.net/%|%expect.sf.net] , with access to the CVS available via
sf.net's cvs repository.

Expect is part of the [ActiveTcl] Batteries Included distribution on Unix
and as of 2005, the Windows version is available via ActiveTcl as well
[http://blogs.activestate.com/activestate/2005/09/expect_for_wind.html].


** Documentation **

   [http://www.tcl.tk/man/expect5.31/index.html%|%man pages]:   
   [http://expect.sourceforge.net/FAQ.html%|%FAQ]:   
   [BOOK Exploring Expect]:   the bible of the Expect world
   [http://expect.nist.gov/%|%official website]:   supplies sources and considerable history, background, and instruction.  It does fail to mention, though, recognition of Expect as one of [http://nvl.nist.gov/pub/nistpubs/sp958-lide/cntsp958.htm%|%the 100 most important publications] of [NIST]'s first century.  Note that the warning regarding expect 5.44 on that page is seriously out of date.  The CVS 5.44 version linked to below is fine (and needed to build against Tcl 8.5).


** External Resources **

   [Expect External Resources]:   gives pointers to some wiki-external Expect material
   [http://phaseit.net/claird/comp.lang.tcl/expect.html%|%Expect references of interest to Cameron Laird]:   some notes by [CL]


** Tools **
   
   [http://expect-lite.sourceforge.net/%|%expect-lite]:   Written in expect, it is designed to directly map an interactive terminal session into an automation script

** Examples **

See [Expect Examples]


** See Also **

   [Expect FAQ]:   
   [Expect Hints and Tips]:   
   [Expect Tutorials]:   
   [Debugging Expect programs]:   
   [Remote input-output with Expect]:   
   [Secure expect]:   
   [Expect for languages other than Tcl]:   
   [Most programmers don't know what Expect can do for them]:   
   [I am new to Expect]:   
   [Event-oriented Expect]:   
   [Expect vs. Tcl]:   
   [Network programming with Expect]:   
   [Expect and Tclkit]:   
   [Expect and choice]:   
   [It seems like Expect is not actively developed]:   
   [overlay]:   
   [handling of ANSI terminals using Expect]:   
   [send special characters]:   
   [Stubsification of Expect]:   
   [An example wherein Expect controls a pager]:   
   ["expect_out(buffer) has the content of the previous send"]:   
   [Calc_Object]:   
   [How Expect can capture the exit code from a remote command]:   
   [Expect for Windows]:   
   [Expect for languages other than Tcl]:   
   [Checking your IMAP mail with Expect]:   
   [How to access the result of a remote command in Expect]:   
   [Many people who think they need Expect do not need Expect]:   
   [Expect's frequently-made mistakes]:   
   [How Expect sees function keys]:   
   [How to send escape characters through Expect]:   
   [Pipes vs Expect]:   
   [expectk]:   
   [expect in pure tcl]:   
   [expect4j]:   provides a certain level of expect's functionality to the [Jacl] / [Java] programmer.  Package author Justin Ryan reports on the [TclJava] [http://sourceforge.net/mailarchive/forum.php?thread_name=67e5f3da0711080735k4820242ascc219f87c52ac45d%40mail.gmail.com&forum_name=tcljava-user%|%mailing list]: ''I've successfully ported a 100K tcl script based on expect to tcljava, without any changes, by just using expect4j.''
   [How do I get the result of a remote command when I have to pass through a third host?]:   
   [Don't Expect to sleep]:   
   [How do I execute 'grep' on a remote machine and receive the result?]:   


** Articles **

   [http://www.nist.gov/customcf/get_pdf.cfm?pub_id=821282%|%Writing a Tcl Extension in Only Three, no Four, no Five, no 7 Years]:   Don Libes' memoir on the joys of writing "simple" tools to get stuff done.

   [http://www.drdobbs.com/expect-success/199101659%|%Expect Success], [CL%|%Cameron Laird] 2003:   is, for [Kim Richert], "the best Expect article I've read". [http://web.archive.org/web/20080804121417/http://www.samag.com/documents/s=7824/sam0310web1/sam0310web1.html%|%alternate]

   [http://www.ibm.com/developerworks/library/l-sc1/?n-l-4112%|%Expect Exceeds Expectations], [CL%|%Cameron Laird], 2002:   a short introduction with minimal examples [http://web.archive.org/web/20101201015029/http://www.ibm.com/developerworks/library/l-sc1/?n-l-4112%|%alternate]

   [http://www.drdobbs.com/expect-the-firefighters-friend/199101420%|%Expect: The Firefighter's Friend], [CL%|%Cameron Laird], 2002:   [http://web.archive.org/liveweb/http://www.drdobbs.com/expect-the-firefighters-friend/199101420%|%alternate]

   [http://web.archive.org/web/20070224042215/http://www.samag.com/documents/s=9035/sam0402web1/%|%Unknown Expect], [CL%|%Cameron Laird] ,2004-02:   seven little-known facts about expect that may help you use it more efficiently

   [http://www.drdobbs.com/test-driven-development-expect-and-syste/199101682%|%Test-driven Development, Expect, and Systems Administration], [CL%|%Cameron Laird] ,2003-12-15:   

   [http://web.archive.org/web/20071031081809/http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/expect/tutorial.html%|%Expect Tutorial]:   

   [http://web.archive.org/web/20061021184854/http://www.samag.com/documents/s=1180/sam9903c/9903c.htm%|%Using Expect to Configure Cisco Routers], Clay Lin ,1999:   "... the entire task would take about a month for two people ...  What used to take us a month now takes about an hour to finish completely and accurately."

   [http://www.ibm.com/developerworks/aix/library/au-expect/%|%Expect plays a crucial role in network management], Cameron Laird, 2007-07-31:   

   [http://www2.lib.uchicago.edu/keith/tcl-course/topics/expect.html%|%Expect], Keith Waclena ,1994:   a 5-minute tutorial

   [http://www.linuxjournal.com/article/3065%|%Automating Tasks with EXPECT] ,Vinnie Saladino ,1998:   


** Misc **

[LV]:  Note that '''expect''' is also a command that is a part of the expect
extension; see the expect source distribution for the doc.

[Lars H]:  Also note that in the latter sense, [expect] is a powerful control
structure (pretty much an [automaton], is it not?).

----

[srinadh] 2009-10-08 10:41:28: I have an expect program. Sometimes it produces
a core dump. How do I see core dump backtrace? Thanks

[AMG]: Use [gdb].

----

[susja] 2010-11-12 14:05:18: I have a simple task:  run autoexpect program to
automate telnet. I was able to do it on my Solaris box but I am stuck on my
Windows XP box.  Here's what I did:

   1. downloaded expect-5.43.tar to my local drive, untar it and have Expect located at C:\.... . I tried to execute 'autoexpect' but it says: "'autoexpect' is not recognized as an internal or external command"
   1. I installed ActiveTcl 8.5.9. Successfully ran 'teacup install Expect'.
   1. Here I'm blocked: how now I could execute autoexpect program?

thanks in advance
----

[bodangly] 2011-12-13 18:47:18: The above question is old and the user likely
found the answer however for reference, the PATH environment variable needs to
have the location of the autoexpect program appended to it.


<<categories>> Package | Expect | Command | System Administration | Control Structure | Unix}} CALL {my revision Expect} CALL {::oo::Obj1051631 process revision/Expect} CALL {::oo::Obj1051629 process}

-errorcode

NONE

-errorinfo

Unknow state transition: LINE -> END
    while executing
"error $msg"
    (class "::Wiki" method "render_wikit" line 6)
    invoked from within
"my render_$default_markup $N $C $mkup_rendering_engine"
    (class "::Wiki" method "render" line 8)
    invoked from within
"my render $name $C"
    (class "::Wiki" method "revision" line 31)
    invoked from within
"my revision $page"
    (class "::Wiki" method "process" line 56)
    invoked from within
"$server process [string trim $uri /]"

-errorline

4