expectperl-discuss — Discussions about Perl modules Expect.pm, IO::Tty and IO::Stty

Re: [Expectperl-discuss] Problems with Echoing

[Austin S. <te...@of...>]

On Wed, Mar 09, 2005 at 09:55:06PM +0000, steve abrams wrote:
> 
> The issue:
> When I first make a connection, I correctly get the text that the server 
> should send, and I correctly get the "login" text I expected. After this 
> however, I can no longer expect anything that should be coming from the 
> server. Instead, expect attempts to match what I'm looking for with what is 
> contained in the 'After match string' variable concatenated with text I 
> type in. Below is output. Any suggestions would be helpful.
> 
<snip>
> match:
>  pattern #1: -ex `login'? YES!!
>    Before match string: `Trying 10.10.1.70...\r\nConnected to 
> rhino-test.lab (10.10.1.70).\r\012Escape character is \'^]\'.\r\012Welcome 
> to Microsoft Telnet Service \r\012\012\r'
>    Match string: `login'
>    After match string: `: '
>    Matchlist: ()
> Sending 'administrator\n' to spawn id(3)
                        ^^

	You probably need to send an \r, not an \n.


	Austin

[Expectperl-discuss] Problems with Echoing

[steve a. <ssa...@ho...>]

I have been using Expect successfully with a linux based telnet terminal 
server, and with ssh connections to linux based products. The problem I am 
having with the same code is where I must connect with a Windows Telnet 
Server.

The issue:
When I first make a connection, I correctly get the text that the server 
should send, and I correctly get the "login" text I expected. After this 
however, I can no longer expect anything that should be coming from the 
server. Instead, expect attempts to match what I'm looking for with what is 
contained in the 'After match string' variable concatenated with text I type 
in. Below is output. Any suggestions would be helpful.

Thanks
Steve

spawn id(3): Does `Trying 10.10.1.70...\r\nConnected to rhino-test.lab 
(10.10.1.70).\r\012Escape
character is \'^]\'.\r\012'
match:
  pattern #1: -ex `login'? No.


spawn id(3): Does `Trying 10.10.1.70...\r\nConnected to rhino-test.lab 
(10.10.1.70).\r\012Escape character is \'^]\'.\r\012Welcome to Microsoft 
Telnet Service \r\012'
match:
  pattern #1: -ex `login'? No.


spawn id(3): Does `Trying 10.10.1.70...\r\nConnected to rhino-test.lab 
(10.10.1.70).\r\012Escape character is \'^]\'.\r\012Welcome to Microsoft 
Telnet Service \r\012\012\rlogin: '
match:
  pattern #1: -ex `login'? YES!!
    Before match string: `Trying 10.10.1.70...\r\nConnected to 
rhino-test.lab (10.10.1.70).\r\012Escape character is \'^]\'.\r\012Welcome 
to Microsoft Telnet Service \r\012\012\r'
    Match string: `login'
    After match string: `: '
    Matchlist: ()
Sending 'administrator\n' to spawn id(3)
        Expect::print('Expect=GLOB(0x872044c)', 'administrator^J') called at 
SystemOperations.pm line 328
        SystemOperations::_send('administrator', 'password:') called at 
SystemOperations.pm line 680
        SystemOperations::login('SystemOperations=HASH(0x80fbb4c)') called 
at Get_All_Logs.pl line 16
Starting EXPECT pattern matching...
        Expect::expect('Expect=GLOB(0x872044c)', 10, 'password:') called at 
SystemOperations.pm line 336
        SystemOperations::_send('administrator', 'password:') called at 
SystemOperations.pm line 680
        SystemOperations::login('SystemOperations=HASH(0x80fbb4c)') called 
at Get_All_Logs.pl line 16
spawn id(3): list of patterns:
  #1: -ex `password:'


spawn id(3): Does `: '
match:
  pattern #1: -ex `password:'? No.


spawn id(3): Does `: administrator'
match:
  pattern #1: -ex `password:'? No.

Died at SystemOperations.pm line 680.
Closing spawn id(3).
        Expect::hard_close('Expect=GLOB(0x872044c)') called at 
/usr/lib/perl5/site_perl/5.6.1/Expect.pm line 1575
        Expect::DESTROY('Expect=GLOB(0x872044c)') called at Get_All_Logs.pl 
line 0
        eval {...} called at Get_All_Logs.pl line 0
spawn id(3) closed.
Pid 3537 of spawn id(3) terminated, Status: 0x01

[Expectperl-discuss] Expect.pm in AIX: pipe function is unimplemented

[Dale G. <dgr...@ho...>]

Hi all,

I'm kinda new to Perl and Expect.

I'm trying to run Expect on an AIX machine which is using ActivePerl 5.6.1.  
But I get the following error message:

"The pipe function is unimplemented at blah/blah/Expect.pm line 105."

I thought I was missing IO::Pipe in my @INC, but that doesn't seem to be the 
case.

Any ideas?
Thanks.

_________________________________________________________________
Scan and help eliminate destructive viruses from your inbound and outbound 
e-mail and attachments. 
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines 
  Start enjoying all the benefits of MSN® Premium right now and get the 
first two months FREE*.

Re: [Expectperl-discuss] Losing terminal access to remote machine after script execution

[Austin S. <te...@of...>]

On Mon, Jan 03, 2005 at 09:35:53PM +0000, steve abrams wrote:
> Hi all,
> 
>       I'm not even sure what relevant information I can include to indicate 
> why this is happening, so if someone could point me in the right direction 
> of where to begin investigating, that would be great...
> 
>      I am using some scripts that simply create a telnet connection to a 
> terminal server port, connected to the machine receiving commands.  The 
> only commands used are "send" and "expect". Occasionally, a script will 
> exit b/c it did not receive the expected output.  This appears to be 
> happening because the machine on the other end stops responding.  After the 
> script execution I find that the remote machine is unresponsive to and 
> terminal connection.
> 
>     I see this often when using Expect, but otherwise I have only seen it 
> once, months ago.  A reboot 'solves' the problem.  Would anyone know how 
> this could be happening?  Is it Expect, how I'm using Expect, or the remote 
> machine?
> 

	Sounds like the remote machine.

	Austin

[Expectperl-discuss] Losing terminal access to remote machine after script execution

[steve a. <ssa...@ho...>]

Hi all,

       I'm not even sure what relevant information I can include to indicate 
why this is happening, so if someone could point me in the right direction 
of where to begin investigating, that would be great...

      I am using some scripts that simply create a telnet connection to a 
terminal server port, connected to the machine receiving commands.  The only 
commands used are "send" and "expect". Occasionally, a script will exit b/c 
it did not receive the expected output.  This appears to be happening 
because the machine on the other end stops responding.  After the script 
execution I find that the remote machine is unresponsive to and terminal 
connection.

     I see this often when using Expect, but otherwise I have only seen it 
once, months ago.  A reboot 'solves' the problem.  Would anyone know how 
this could be happening?  Is it Expect, how I'm using Expect, or the remote 
machine?

Thanks!
Steve

Re: [Expectperl-discuss] Expect.pm not working with mod_perl

[Austin S. <te...@of...>]

On Tue, Dec 28, 2004 at 08:08:40PM +0800, Edwin Lok wrote:
> Hi All,
> 
> I'm using Expect.pm v1.15.
> 
> I've written a simple script which runs perfectly fine on command line. 
> However when I try to use this under mod_perl, it fails at the first expect 
> command. The mod_perl version is 1.29.
> 
> When I enable $Expect::Debug = 1, I can see that an EOF is found 
> prematurely. Anyone has encounter such incident before.
> 

	No, but I've never tried to use expect w/ modperl. Something to
keep in mind is that mod_perl _hates_ the use of globals. Also, in my
experience, it's somewhat buggy.
	Before you go too far down the fishing for globals route, try the
module without modperl: rename your script to script.cgi and see if it
fails when called as a normal cgi. If it does fail, you probably have
an issue with there being a difference in your environment variables.

	Austin

[Expectperl-discuss] Expect.pm not working with mod_perl

[Edwin L. <edw...@pa...>]

Hi All,

I'm using Expect.pm v1.15.

I've written a simple script which runs perfectly fine on command line. However 
when I try to use this under mod_perl, it fails at the first expect command. The 
mod_perl version is 1.29.

When I enable $Expect::Debug = 1, I can see that an EOF is found prematurely. 
Anyone has encounter such incident before.

Thanks

Rgds
Edwin

[Expectperl-discuss] Re: ActiveState Perl

[Lyle K. <ly...@ve...>]

Thanks folks, for the replies pointing me to Net::Telnet.  It looks like 
it does everything I need, including: waiting for patterns, and using 
pre-existing filehandles.  The telnet login functionality will also come 
in handy.

Regards,
Lyle Kopnicky

[Expectperl-discuss] ActiveState Perl

[Lyle K. <ly...@ve...>]

Hi, I'm trying to do something expect-like in ActivePerl and thought it 
would be nice to use a prewritten module.  I found out about Expect.pm 
but I'm told it doesn't support ActivePerl on Windows.  However, the 
reason given was that "Windows doesn't have pty's".

Well I don't care about pty's.  I'm not trying to interact with a 
program, just with an already-open network socket.  All I want to do is 
wait for certain text to appear, then send other text.  Will Expect.pm 
work fine in that case?  Or is there a simpler package that would do 
what I want?

Thanks,
Lyle Kopnicky

Re: [Expectperl-discuss] Killing all the child processes created through Expect module

[Austin S. <te...@of...>]

On Mon, Dec 13, 2004 at 10:08:17AM +0000, Madhav kelkar wrote:
> Hi all,
>            sorry to bother you once again, but I am stuck with a
> problem. This what I am doing:
> 
>                  1. I create an object by calling Expect->spawn().
>                  2. Then I use this object to fire some commands
> which are spawning another set of commands and so on.
>                  3.  I am then calling $obj->pid() to get the pid of
> the handle.
>                  4. Now I want to   kill the  commands that were
> spawned by  this handle.  So  i   am sending a kill signal to -$pid.  which 
> sends a signal to the whole group of commands that r running.
> ($pid =pid of the handle).
> 
>                      But some times the child processes created
> through the handle remain in the system. What is the reliable way to
> kill all such child processes created through the handle?  Please help
> me out of this.

	My understanding is that members of a process group are sent a HUP
when the process leader dies. You might try doing a setpgrp() within the
spawned child process. If that doesn't work then it's likely some of the
processes are catching HUP, in which case you will have to find some other
mechanism, such as finding them via ps.

	Austin

[Expectperl-discuss] Killing all the child processes created through Expect module

[Madhav k. <mad...@ho...>]

Hi all,
            sorry to bother you once again, but I am stuck with a
problem. This what I am doing:

                  1. I create an object by calling Expect->spawn().
                  2. Then I use this object to fire some commands
which are spawning another set of commands and so on.
                  3.  I am then calling $obj->pid() to get the pid of
the handle.
                  4. Now I want to   kill the  commands that were
spawned by  this handle.  So  i   am sending a kill signal to -$pid.  which 
sends a signal to the whole group of commands that r running.
($pid =pid of the handle).

                      But some times the child processes created
through the handle remain in the system. What is the reliable way to
kill all such child processes created through the handle?  Please help
me out of this.
                       I am using perl and Expect 1.15. A similler
query in the newsgroup comp.lang.perl.misc had no answers. So I
thought you could help me.



                                               Thanks,

                                                                       
Madhav.



https://lists.sourceforge.net/lists/listinfo/expectperl-discuss

_________________________________________________________________
Pep up your screen! Kickstart your day! 
http://www.msn.co.in/Cinema/screensaver/ Get these vibrant screensavers!

RE: [Expectperl-discuss] log_file append

[Hays, J. <Jon...@NC...>]

-----Original Message-----
From: Austin Schutz [mailto:te...@of...]=20
Sent: Friday, December 10, 2004 1:07 PM
To: Hays, Jonathan
Cc: exp...@li...
Subject: Re: [Expectperl-discuss] log_file append

On Fri, Dec 10, 2004 at 12:33:43PM -0500, Hays, Jonathan wrote:
> The Perl expect.pm documentation tells me how to start and stop
logging:
>=20
> Start:
> $exp->log_file("filename","w");
>=20
> Stop:
> $exp->log_file(undef);
>=20
> But this overwrites the log on every loop.=20
>=20
> How do I append to that same log? I've tried "a" and ">>", neither of
> which works.
>=20
> Any ideas?
>=20

	It works fine here with log_file("filename","a"). From here it
looks
like there is either a platform specific bug with IO::File, or perhaps
you
have something in your code which is questionable - maybe clearing the
file
ahead of time or after it is read maybe.
	IO::File has been around quite some time iirc - I suspect you
have
a bug somewhere else in your code.

	Austin


Yeah, you're right. I don't know what I was doing before but I tried "a"
and it's working fine.

Thanks!

Jonathan

Re: [Expectperl-discuss] log_file append

[Austin S. <te...@of...>]

On Fri, Dec 10, 2004 at 12:33:43PM -0500, Hays, Jonathan wrote:
> The Perl expect.pm documentation tells me how to start and stop logging:
> 
> Start:
> $exp->log_file("filename","w");
> 
> Stop:
> $exp->log_file(undef);
> 
> But this overwrites the log on every loop. 
> 
> How do I append to that same log? I've tried "a" and ">>", neither of
> which works.
> 
> Any ideas?
> 

	It works fine here with log_file("filename","a"). From here it looks
like there is either a platform specific bug with IO::File, or perhaps you
have something in your code which is questionable - maybe clearing the file
ahead of time or after it is read maybe.
	IO::File has been around quite some time iirc - I suspect you have
a bug somewhere else in your code.

	Austin

[Expectperl-discuss] log_file append

[Hays, J. <Jon...@NC...>]

The Perl expect.pm documentation tells me how to start and stop logging:

Start:
$exp->log_file("filename","w");

Stop:
$exp->log_file(undef);

But this overwrites the log on every loop.=20

How do I append to that same log? I've tried "a" and ">>", neither of
which works.

Any ideas?

Jonathan=20

Re: [Expectperl-discuss] problem with Expect::spawn() when running in background on Solaris

[Austin S. <te...@of...>]

On Tue, Nov 02, 2004 at 10:35:41AM -0800, Eric Feng wrote:
> Hi, I am having problem with the following perl program which calls
> Expect::spawn() when running in background on Solaris. It got suspended.
> 
<script snipped>
> 
> It works fine on linux (both foreground and background). Is this a perl bug
> or solaris bug? Is there a setting/workaround to get it to work in
> background on solaris? Any help is appreciated.
> 


	It fails for me in IO::Pty::make_slave_controlling_terminal() at
line 89:

  # loose controlling terminal explicitely
  if (defined TIOCNOTTY) {
    if (open (\*DEVTTY, "/dev/tty")) {
      ioctl( \*DEVTTY, TIOCNOTTY, 0 ); # Hangs here.
      close \*DEVTTY;
    }
  }

	This looks like a solaris bug, sort of. As far as I can tell calling
TIOCNOTTY on /dev/tty is pretty well obsoleted. It's not even mentioned
in any of the man pages.

	Changing the top line there to:

  if (0) { # defined TIOCNOTTY) {


	worked for me. I'm not sure what a good permanent solution is. It may
be TIOCNOTTY is required for some of the older BSD based platforms. Maybe an
if($^O ne 'solaris') might be appropriate.


	Austin

RE: [Expectperl-discuss] problem with Expect::spawn() when runnin g in background on Solaris

[Simon T. <se...@no...>]

I have had similar experience with this.
I don't have a solution but my investigations indicated it might be shell
specific - what shell are you using on Solaris?
I originally wanted to extend my app to use POE but the processes kept
hanging as soon as they were forked and run in the bg.

Simon 

-----Original Message-----
From: exp...@li...
[mailto:exp...@li...] 
Sent: 02 November 2004 18:36
To: exp...@li...
Cc: 'Eric Feng'
Subject: [Expectperl-discuss] problem with Expect::spawn() when running in
background on Solaris

Hi, I am having problem with the following perl program which calls
Expect::spawn() when running in background on Solaris. It got suspended.

% cat bg.pl

#!/usr/local/bin/perl5.6

use Expect;

my $exp = Expect->spawn("echo hello");
$exp->soft_close();

% bg.pl
hello

% bg.pl &
[1] 2191
% 
[1]  + Suspended (tty output)        bg.pl

% fg
bg.pl
Hello

It works fine on linux (both foreground and background). Is this a perl bug
or solaris bug? Is there a setting/workaround to get it to work in
background on solaris? Any help is appreciated.

I am using perl5.6, the Expect moduls is the latest I downloaded on CPAN,
the Solaris OS is both 5.6 and 5.8.

-Eric Feng



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide Read honest & candid reviews
on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Expectperl-discuss mailing list
Exp...@li...
https://lists.sourceforge.net/lists/listinfo/expectperl-discuss

[Expectperl-discuss] perl program using Expect::spawn() get suspended when running in background on Solaris

[Eric F. <ef...@ci...>]

Hi, I am having problem with the following perl program which calls
Expect::spawn()when running it in background on Solaris. It got SUSPENDED.

% cat bg.pl

#!/usr/local/bin/perl5.6

use Expect;

my $exp = Expect->spawn("echo hello");
$exp->soft_close();

% bg.pl
hello

% bg.pl &
[1] 2191
% 
[1]  + Suspended (tty output)        bg.pl

% fg
bg.pl
Hello

It works fine on linux (both foreground and background). Is this a perl bug
or solaris bug? Is there a setting/workaround to get it to work in
background on solaris? Any help is appreciated.

I am using perl5.6, the Expect/IO::Stty/IO::Tty modules are the latest I
downloaded on CPAN, the Solaris OS is both 5.6 and 5.8.

-Eric Feng

[Expectperl-discuss] problem with Expect::spawn() when running in background on Solaris

[Eric F. <ef...@ci...>]

Hi, I am having problem with the following perl program which calls
Expect::spawn() when running in background on Solaris. It got suspended.

% cat bg.pl

#!/usr/local/bin/perl5.6

use Expect;

my $exp = Expect->spawn("echo hello");
$exp->soft_close();

% bg.pl
hello

% bg.pl &
[1] 2191
% 
[1]  + Suspended (tty output)        bg.pl

% fg
bg.pl
Hello

It works fine on linux (both foreground and background). Is this a perl bug
or solaris bug? Is there a setting/workaround to get it to work in
background on solaris? Any help is appreciated.

I am using perl5.6, the Expect moduls is the latest I downloaded on CPAN,
the Solaris OS is both 5.6 and 5.8.

-Eric Feng

RE: [Expectperl-discuss] Perl Expect: On match timeout, $exp->match() holds value of previous

[steve a. <ssa...@ho...>]

Willy, thanks for your suggestion! I was originally using Net::Telnet and it 
was working great, but I'm building a module to connect to devices either 
via terminal server (telnet), or via either ssh or telnet to the device 
itself (service available depends on device type).  I was going to use 
Net::SSH::Perl to compliment the Net::Telnet work, but it wasn't not working 
for my particular application, and I'm going for as few dependecies as 
possible.

Roland, thanks for your response and your work! Perl's Expect module is 
working great for me, without the use of either above-mentioned module.  I 
will simply use the return value of expect.

P.S. The only reason I would integrate Net::Telnet with Expect for this 
module would be to make use of Net::Telnet's timeout member, which I was 
using behind the scenes, hiding it from my test scripts.



>From: Roland Giersig <RGi...@cp...>
>To: exp...@li...
>Subject: RE: [Expectperl-discuss] Perl Expect: On match timeout, 
>$exp->match() holds value of previous
>Date: Fri, 29 Oct 2004 10:06:31 +0200
>
>This indeed is inconsistent. The docs state that it should set match to
>undef, but it doesn't. It did in some ancient version, but I obviously
>broke that when I added the complex callback interface.
>
>Sorry, for now you either have to check the return value of the expect()
>call (o for timeout) or install a callback for the 'timeout' pattern if
>you use the callback-version.
>
>Oh, and you can use Net::Telnet with Expect (at least somebody told me
>it worked), just use the filehandle returned by Net::Telnet with
>exp_init()...
>
>Hope this helps,
>
>Roland
>
>
>"Roche, Willy" <wil...@hp...>:
> > Do you know of Net::Telnet? It provides lot of usefull things, like
> > Timeouts, and automate Telnet session really easily.
> >
> > Willy
> >
> > -----Original Message-----
> > From: exp...@li...
> > [mailto:exp...@li...] On Behalf Of
> > steve abrams
> > Sent: jeudi 28 octobre 2004 20:28
> > To: exp...@li...
> > Subject: [Expectperl-discuss] Perl Expect: On match timeout,
> > $exp->match() holds value of previous
> >
> > New to list, Hello all!
> >
> > So I'm automating a Telnet connection, and I'm checking for timeouts
> > by
> > seeing if $exp->match() returns undefined.  The problem I have found
> > is
> > that
> > $exp->match() doesn't get cleared from the previous $exp->expect
> > call.
> > There doesn't appear to be a method to clear out whats returned from
> > $exp->(before()|match()|after()).
> >
> > Is this expected behavior? I know there are workarounds, but I would
> > expect (no pun intended) something to be built in to either:
> >
> > A: clear out before|match|after of previous values during an expect
> > call
> >
> > B: provide a method to manually clear them.
> >
> > Thanks!
> > Steve
> >
> > _________________________________________________________________
> > Don't just search. Find. Check out the new MSN Search!
> > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> >
> >
> >
> > -------------------------------------------------------
> > This Newsletter Sponsored by: Macrovision For reliable Linux
> > application
> > installations, use the industry's leading setup authoring tool,
> > InstallShield X. Learn more and evaluate today.
> > http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
> > _______________________________________________
> > Expectperl-discuss mailing list
> > Exp...@li...
> > https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
> >
> >
> > -------------------------------------------------------
> > This Newsletter Sponsored by: Macrovision
> > For reliable Linux application installations, use the industry's
> > leading
> > setup authoring tool, InstallShield X. Learn more and evaluate
> > today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
> > _______________________________________________
> > Expectperl-discuss mailing list
> > Exp...@li...
> > https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
> >
>
>
>--
>RGi...@cp...
>
>
>-------------------------------------------------------
>This Newsletter Sponsored by: Macrovision
>For reliable Linux application installations, use the industry's leading
>setup authoring tool, InstallShield X. Learn more and evaluate
>today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
>_______________________________________________
>Expectperl-discuss mailing list
>Exp...@li...
>https://lists.sourceforge.net/lists/listinfo/expectperl-discuss

_________________________________________________________________
Get ready for school! Find articles, homework help and more in the Back to 
School Guide! http://special.msn.com/network/04backtoschool.armx

RE: [Expectperl-discuss] Perl Expect: On match timeout, $exp->match() holds value of previous

[Roland G. <RGi...@cp...>]

This indeed is inconsistent. The docs state that it should set match to
undef, but it doesn't. It did in some ancient version, but I obviously
broke that when I added the complex callback interface.

Sorry, for now you either have to check the return value of the expect()
call (o for timeout) or install a callback for the 'timeout' pattern if
you use the callback-version.

Oh, and you can use Net::Telnet with Expect (at least somebody told me
it worked), just use the filehandle returned by Net::Telnet with
exp_init()...

Hope this helps,

Roland


"Roche, Willy" <wil...@hp...>:
> Do you know of Net::Telnet? It provides lot of usefull things, like
> Timeouts, and automate Telnet session really easily.
>
> Willy
>
> -----Original Message-----
> From: exp...@li...
> [mailto:exp...@li...] On Behalf Of
> steve abrams
> Sent: jeudi 28 octobre 2004 20:28
> To: exp...@li...
> Subject: [Expectperl-discuss] Perl Expect: On match timeout,
> $exp->match() holds value of previous
>
> New to list, Hello all!
>
> So I'm automating a Telnet connection, and I'm checking for timeouts
> by
> seeing if $exp->match() returns undefined.  The problem I have found
> is
> that
> $exp->match() doesn't get cleared from the previous $exp->expect
> call.
> There doesn't appear to be a method to clear out whats returned from
> $exp->(before()|match()|after()).
>
> Is this expected behavior? I know there are workarounds, but I would
> expect (no pun intended) something to be built in to either:
>
> A: clear out before|match|after of previous values during an expect
> call
>
> B: provide a method to manually clear them.
>
> Thanks!
> Steve
>
> _________________________________________________________________
> Don't just search. Find. Check out the new MSN Search!
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
>
>
> -------------------------------------------------------
> This Newsletter Sponsored by: Macrovision For reliable Linux
> application
> installations, use the industry's leading setup authoring tool,
> InstallShield X. Learn more and evaluate today.
> http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
> _______________________________________________
> Expectperl-discuss mailing list
> Exp...@li...
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>
>
> -------------------------------------------------------
> This Newsletter Sponsored by: Macrovision
> For reliable Linux application installations, use the industry's
> leading
> setup authoring tool, InstallShield X. Learn more and evaluate
> today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
> _______________________________________________
> Expectperl-discuss mailing list
> Exp...@li...
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>


--
RGi...@cp...

RE: [Expectperl-discuss] Perl Expect: On match timeout, $exp->match() holds value of previous

[Roche, W. <wil...@hp...>]

Do you know of Net::Telnet? It provides lot of usefull things, like
Timeouts, and automate Telnet session really easily.

Willy=20

-----Original Message-----
From: exp...@li...
[mailto:exp...@li...] On Behalf Of
steve abrams
Sent: jeudi 28 octobre 2004 20:28
To: exp...@li...
Subject: [Expectperl-discuss] Perl Expect: On match timeout,
$exp->match() holds value of previous

New to list, Hello all!

So I'm automating a Telnet connection, and I'm checking for timeouts by
seeing if $exp->match() returns undefined.  The problem I have found is
that
$exp->match() doesn't get cleared from the previous $exp->expect call. =20
There doesn't appear to be a method to clear out whats returned from
$exp->(before()|match()|after()).

Is this expected behavior? I know there are workarounds, but I would
expect (no pun intended) something to be built in to either:

A: clear out before|match|after of previous values during an expect call

B: provide a method to manually clear them.

Thanks!
Steve

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!=20
http://search.msn.click-url.com/go/onm00200636ave/direct/01/



-------------------------------------------------------
This Newsletter Sponsored by: Macrovision For reliable Linux application
installations, use the industry's leading setup authoring tool,
InstallShield X. Learn more and evaluate today.
http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
Expectperl-discuss mailing list
Exp...@li...
https://lists.sourceforge.net/lists/listinfo/expectperl-discuss

[Expectperl-discuss] Perl Expect: On match timeout, $exp->match() holds value of previous

[steve a. <ssa...@ho...>]

New to list, Hello all!

So I'm automating a Telnet connection, and I'm checking for timeouts by 
seeing if $exp->match() returns undefined.  The problem I have found is that 
$exp->match() doesn't get cleared from the previous $exp->expect call.  
There doesn't appear to be a method to clear out whats returned from 
$exp->(before()|match()|after()).

Is this expected behavior? I know there are workarounds, but I would expect 
(no pun intended) something to be built in to either:

A: clear out before|match|after of previous values during an expect call

B: provide a method to manually clear them.

Thanks!
Steve

_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/

Re: [Expectperl-discuss] re: building Expect.pm on solaris 9

[Zhisong J. <jj...@dy...>]

thanks for all replied.  so now  I'm back at this setting: 

solaris 9, perl 5.8.4, gcc 3.3.2, IO-tty-1.02, and expect-1.15.

as suggested by Austin, I comment out the line 119 and 120 on Pty.pm
and now try to run a small program that use expect.pm

==========the relevent code segment of test program =======
# example taken from Perl for System administrators 
$username='test';
$tmp_pwd='test';
my $result = &InitUnixPasswd($username, $tmp_pwd);

sub InitUnixPasswd {
    my ($account,$passwd) = @_;

    # return a process object
    my $pobj = Expect->spawn($passwdex, $account);
    die "Unable to spawn $passwdex:$!\n" unless (defined $pobj);

    # do not log to stdout (i.e. be silent)
    $pobj->log_stdout(0);

    $pobj->expect(10,"New password: ");
    # Linux sometimes prompts before it is ready for input, so we pause
    sleep 1;
    print $pobj "$passwd\r";
    $pobj->expect(10, "Re-enter new password: ");
    print $pobj "$passwd\r";

    $result = (defined ($pobj->expect(10, "successfully changed")) ?
                                         "" : "password changefailed");

    # close the process object, waiting up to 15 secs for
    # the process to exit
    $pobj->soft_close(  );

    return $result;
}

================================================
the program  failed; 

Use of uninitialized value in join or string at
/usr/local/lib/perl5/site_perl/5.8.4/Expect.pm line 129.
Cannot exec( test): No such file or directory
Use of uninitialized value in concatenation (.) or string at
/usr/local/dpiusr/mkdpiusr line 137.
Unable to spawn :No such file or directory


I then commment out Expect.pm line 129 
 #warn "Error: could not connect pty as controlling terminal!\n";

and try again, still same error, the real  problem seem is
"Unable to spawn". any suggestions.

Thanks.

h
> 
> 	The other (much easier) workaround is to just comment out the
> offending warning. It doesn't really matter if the ioctl fails, because
> Solaris doesn't define TIOCSCTTY in the first place. You won't break anything
> by commenting out lines 119 and 120, which should make the warning go away.
> 
> 	Austin
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Expectperl-discuss mailing list
> Exp...@li...
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
> 

RE: [Expectperl-discuss] re: building Expect.pm on solaris 9

[Blackstone, J. D. <jda...@ci...>]

> -----Original Message-----
> From: exp...@li... 
> [mailto:exp...@li...] On 
> Behalf Of Zhisong Jin
> Sent: Monday, October 18, 2004 3:15 PM
> To: Austin Schutz
> Cc: Roland Giersig; exp...@li...
> Subject: Re: [Expectperl-discuss] re: building Expect.pm on solaris 9
> 
> 
> Austin:
> 
> thank you for the reply. since I wasn't able to figure out
> how to  make it work under perl 5.8.4. I'm now trying to
> use SUN's version of perl 5.005_03 came with solaris 9. 
> 
> solaris 9, perl 5.005_03 ,and IO-Tty-1.02 from sourceforge.
> 
> however, make on  IO-Tty-1.02  gives
> 
> [jason@flounder IO-Tty-1.02]$ make
> <snip>
> cc -c   -xO3 -xdepend    -DVERSION=\"1.02\" 
> -DXS_VERSION=\"1.02\" -KPIC
> -I/usr/perl5/5.00503/sun4-solaris/CORE -DHAVE_DEV_PTMX -DHAVE_GRANTPT
> -DHAVE_PTSNAME -DHAVE_SIGACTION -DHAVE_STRLCPY -DHAVE_SYS_STROPTS_H
> -DHAVE_TERMIOS_H -DHAVE_TERMIO_H -DHAVE_TTYNAME -DHAVE_UNLOCKPT Tty.c
> cc: unrecognized option `-KPIC'
> cc: language depend not recognized
> cc: Tty.c: linker input file unused because linking not done
> Running Mkbootstrap for IO::Tty ()
> chmod 644 Tty.bs
> LD_RUN_PATH="" cc -o blib/arch/auto/IO/Tty/Tty.so  -G Tty.o
> cc: Tty.o: No such file or directory
> cc: no input files
> make: *** [blib/arch/auto/IO/Tty/Tty.so] Error 1
> 
> I believe the sun own version of perl is compiled with sun's own c 
> compiler. does that  causing this problm, any work around? 
> 
> Thanks. 
> Jason 

  That is caused by the fact that it is compiled by Sun's compiler.  It is
possible to work around, through modifying the Config.pm that is installed
with perl.  IIRC, there are about four variables you will have to modify,
including values for the linker and the compiler (both of which need to be
gcc) and values for optimization.  (Sun's value is -KPIC or something;
you'll need to change it to either blank or -O.)

  I do not recommend messing with this workaround, though.  I doubt the
problem is caused by perl version.

> PS: I also tried to compile perl 5.005_03 from source using gcc 3.3.2
> on solaris 9.  I got an 
> [jason@flounder perl5.005_03]$ make
> make: *** No rule to make target `<built-in>', needed by
> `miniperlmain.o'.  Stop.

  Here's my recommendations for compiling perl:
http://use.perl.org/~jdavidb/journal/6477

  I recommend you retry with a fresh install of the latest version (5.8.5)
before trying older versions.

jdb

Re: [Expectperl-discuss] re: building Expect.pm on solaris 9

[Austin S. <te...@of...>]

On Mon, Oct 18, 2004 at 04:14:43PM -0400, Zhisong Jin wrote:
> Austin:
> 
> thank you for the reply. since I wasn't able to figure out
> how to  make it work under perl 5.8.4. I'm now trying to
> use SUN's version of perl 5.005_03 came with solaris 9. 
> 

	Sorry, I should have replied to the other message.

> solaris 9, perl 5.005_03 ,and IO-Tty-1.02 from sourceforge.
> 
> however, make on  IO-Tty-1.02  gives
> 
...
> <snip>
> cc -c   -xO3 -xdepend    -DVERSION=\"1.02\" -DXS_VERSION=\"1.02\" -KPIC
> -I/usr/perl5/5.00503/sun4-solaris/CORE -DHAVE_DEV_PTMX -DHAVE_GRANTPT
> -DHAVE_PTSNAME -DHAVE_SIGACTION -DHAVE_STRLCPY -DHAVE_SYS_STROPTS_H
> -DHAVE_TERMIOS_H -DHAVE_TERMIO_H -DHAVE_TTYNAME -DHAVE_UNLOCKPT Tty.c
> cc: unrecognized option `-KPIC'
> cc: language depend not recognized

	This is (as you suspected) because perl was compiled with the solaric
cc, but you are trying to compile the module with the gnu cc. You can fix this
by modifying your Config.pm (somewhere in your @INC path) to use flags
compatible with gcc, such as -fPIC and -O3.


	The other (much easier) workaround is to just comment out the
offending warning. It doesn't really matter if the ioctl fails, because
Solaris doesn't define TIOCSCTTY in the first place. You won't break anything
by commenting out lines 119 and 120, which should make the warning go away.

	Austin