issues with expect -send: spawn id exp4 not open

From: rashmi (nsrashmi_at_gmail.com)
Date: 03/30/05

  • Next message: rashmi: "how to read remote file" 
    Date: Wed, 30 Mar 2005 01:53:50 -0500

    I have a procedure which does logout for eg:
    proc cli_logout { } {
      send "quit\r"
      expect "*#"
    }
    whenever i call this procedure in another procedure
    proc validate_ntp { } {
    cli_logout
    }
    it gives out an error mesage-----
    send: spawn id exp4 not open
        while executing
    "send "quit\r""
        (procedure "cli_logout" line 2)
        invoked from within
    Can u people plz help me out in using the procedures .
    Thanks in advance
    Rashmi

  • Next message: rashmi: "how to read remote file"

    Relevant Pages

    • Low-Level crash tracing errorInfo
      ... I'm trying to have a detailed errorStack in Tcl. ... puts "ERROR Found: " ... proc A { ... I'm running ActiveTcl 8.5.4 and executing in the wish console, ...
      (comp.lang.tcl)
    • Re: Call stored proc from ADODB.Command
      ... > The problem is that when I call for that proc using ADODB.Command object, everything that is before UPDATE statement is executed, ... > Dim cmd as new adodb.command ... > To test executing I inserted RAISERROR after UPDATE statement and it never works... ...
      (microsoft.public.vb.database)
    • Re: COND= running a step that it should not. WHY? BFOM! Options
      ... Neal Eckhardt said: ... A PROC that has an override COND.STEPX=for a step within the PROC, and the above mentioned IF/THEN/ELSE/ENDIF is also contained within the PROC. ... This step is executing. ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
      (bit.listserv.ibm-main)
    • Re: Low-Level crash tracing errorInfo
      ... I'm trying to have a detailed errorStack in Tcl. ... is still bug 1038021 or some bug related causing ... proc A { ... I'm running ActiveTcl 8.5.4 and executing in the wish console, ...
      (comp.lang.tcl)
    • Re: rdo performance with sql 2000
      ... I suspect that the SQL Server you're executing against does not have the ... There is one stored proc that is executed from the VB application and ... Private Sub Delete ...
      (microsoft.public.vb.database)