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

Re: [Expectperl-discuss] ssh works from console but not once daemonized

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

What system are you running on? You ARE using the latest version of
IO::Tty, I suppose...

The problem is: ssh is opening /dev/tty to read the password. If the
script is started in a terminal session, /dev/tty is defined and Expect
will redirect it for the spawned program to the pty, so the password
prompt is seen.

When the script is started via cron, there is no controlling terminal
and obviously Expect cannot take control of it (it would have to create
it), so ssh cannot get the password and thus fails.

Even though I've had my share at kernel hacking, I do not know how to
resolve this, especially given that this is probably highly
system-dependend...

Workaround: set up public key authentication for ssh, so ssh doesn't ask
for a password.  But then you'd probably won't need Expect at all...

Hope this helps,

Roland

Chris Muth wrote:

> Hi,
> 
> I am working on a script that daemonizes and then uses
> ssh to login/operate/logout of a remote machine.
> 
> The code works perfectly when it is not demonized, (with the demonization
> code commented out).  The script will run and partially work if the
> code (the lines indicated below) is left in,-- it will fork, detach, and
> sleep but fail to get the command prompt on the remote machine.
> I have it log to a file (LOG_FILE), because when it is daemonized I cannot
> see the output.
> 
> The only thing I can think of is that ssh must do something to the
> terminal/console that works
> when I run it manually on the console, but when the program
> is daemonized, ssh cannot do whatever it is trying to do and fails.
> 
> The segment below fails saying "never got command prompt".  This means that
> it got the password prompt from the remote machine
> and sent the password, but never got the command prompt after that.
> 
> I don't think this is an expect problem, I think that it is a problem with
> how ssh and expect work together.
> My guess is that ssh is not intentionally failing, but it is trying to do
> something that does not work with the terminal that expect uses.
> 
> I have even tried "ssh -l root" to specify the username, "ssh -T" so ssh
> won't allocate a pseudo-tty, and not setting the pty to raw; all to no
> avail.
> 
> Does anyone have any ideas?
> Below is the code segment.
> 
> Thanks,
> -Chris Muth
> 
> 
> #!/usr/bin/perl5.8 -w
> 
> #prompt user for host to login to, and password
> print"host: ";$host=<STDIN>;chomp$host;
> print"pass: ";$pass=<STDIN>;chomp$pass;
> 
> use Expect;
> use POSIX;
> 
> #  Comment out daemonizing code starting here
> #######################################
> $pid = fork();
> exit 0 if ($pid);
> 
> POSIX::setsid();
> close STDIN;
> close STDOUT;
> close STDERR;
> 
> sleep 5;
> #######################################
> # comment out daemonizing code ending here
> 
> open (LOG_FILE, "> output"); # open log file
> 
> $exp = new Expect;
> $exp->raw_pty(1);
> 
> # login to the remote host
> #$exp->spawn("/usr/local/bin/ssh",'-T',"$host");  # Even tried ssh -T
> $exp->spawn("/usr/local/bin/ssh","$host");
> 
> # wait for Password: prompt
> $retval = $exp->expect(30,'-re','word:\s$');
> if (!defined $retval){
>    print LOG_FILE "Never got password prompt\n"; flush LOG_FILE;
> } else {
>    $exp->send("$pass\n");
>    #($retval,undef,$retstr,undef,undef) = $exp->expect(30,'stdin: is not a tty'); # for ssh -T
>    ($retval,undef,$retstr,undef,undef) = $exp->expect(30,'# ');
> 
>    # do something on the remote machine, test results
>    if (!defined $retval){
>       print LOG_FILE "Never got command prompt\n"; flush LOG_FILE;
>    } else {
>       print LOG_FILE "\"$retstr\"\n"; flush LOG_FILE;
>       $exp->send("echo Hello World\n");
>       $exp->expect(5,'This will make expect sleep for 5 seconds');
>       $exp->send("logout\n");
>       print LOG_FILE "It worked\n"; flush LOG_FILE;
>    }
> }
> $exp->hard_close();
> print LOG_FILE "\n"; flush LOG_FILE;
> close LOG_FILE;
> exit 0;
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Expectperl-discuss mailing list
> Exp...@li...
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
> 

Re: [Expectperl-discuss] ssh works from console but not once daemonized

[Chris S. <cas...@pe...>]

Have you considered that the prompt is just not what you think it is?  Have you considered setting the prompt match to something very wide such as /.+/?

Just my two cents,
Chris

Re: [Expectperl-discuss] ssh works from console but not once daemonized

[Ed A. <er...@uc...>]

I gathered from your explanation that your expect-perl program
wasn't working in daemon mode because it expects to have a
controlling tty (i.e. "/dev/tty") to write to.  I'm assuming
that you're running in daemon mode such that your controlling
tty is undefined; i.e. if you did a "ps -ef" (or whatever's
appropriate for your system), the "TTY" columns for your
daemon process would contain '?'.

So maybe (and this is iffy, given the weird things ssh does
under the covers) if you move the unusable /dev/tty
out of the way and create /dev/tty as an ordinary file your
program can write to, things will work.

Unfortunately this will require root permission, since
/dev/tty is root-owned (at least on Redhat and Solaris).


> Hi.
> 
> I'm sorry.  I don't quite understand how this would help.
> It sounds interesting.  Please explain more.
> 
> Thanks,
> -Chris Muth
> 
> 
> On 9/15/03 at 1:26 PM Ed Arnold wrote:
> 
> >Have you tried an ugly hack?   Do something like "mv /dev/tty
> >/dev/tty.bak"
> >(very temporarily!), then make /dev/tty a regular file which programs that
> >require tty, can scribble into.
> >
> >Disclaimer: I've only used this hack for input.  Your mileage may vary.
> >
> >
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Expectperl-discuss mailing list
> Exp...@li...
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss

Re: [Expectperl-discuss] ssh works from console but not once daemonized

[Chris M. <mut...@mc...>]

Hi.

I'm sorry.  I don't quite understand how this would help.
It sounds interesting.  Please explain more.

Thanks,
-Chris Muth


On 9/15/03 at 1:26 PM Ed Arnold wrote:

>Have you tried an ugly hack?   Do something like "mv /dev/tty
>/dev/tty.bak"
>(very temporarily!), then make /dev/tty a regular file which programs that
>require tty, can scribble into.
>
>Disclaimer: I've only used this hack for input.  Your mileage may vary.
>
>

Re: [Expectperl-discuss] ssh works from console but not once daemonized

[Chris M. <mut...@mc...>]

Yes.  I used that extensively when debugging the program that the fragment=
 in my original
post came from.  However, in this case, the script works perfectly when=
 running on the terminal and I can
see the output of that ($Expect::Exp_Internal=3D1;), but when the script is=
 daemonized, there is no connection
to the terminal to send output to.

Note that in the fragment in my original post, I 'close STDOUT;'.
I even tried something like the following.

close STDOUT;
open (STDOUT, "> log_file");
print "Hello, World!\n";

That worked.  I was able to use standard print statements (that print to=
 STDOUT by default)
to send stuff to the file, but any output from expect did not show up in=
 the file.

I tried that again just now to be sure.  I even tried opening STDERR to a=
 file.
In both cases the program now hangs with a 0 length output file.
It does not even say that it did not get the prompt.  I know that is hung=
 as it showed up
in `ps -eaf`  for a longer time than any of its timeouts.

Thanks for the idea though :-)

-Chris Muth

On 9/15/03 at 12:24 PM John Mahoney wrote:
>
>Have you tried setting
>	$Expect::Exp_Internal=3D1;
>before creating your expect object?
>
>This will produce a lot of debugging info that may help
>you locate the cause of your trouble.
>
>--
>John
>_________________________________________________________
>John Mahoney

Re: [Expectperl-discuss] ssh works from console but not once daemonized

[John M. <ex...@h0...>]

On Sun, Sep 14, 2003 at 04:27:52PM -0500, Chris Muth wrote:
> Hi,
> 
> I am working on a script that daemonizes and then uses
> ssh to login/operate/logout of a remote machine.
> 
> The code works perfectly when it is not demonized, (with the demonization
> code commented out).  The script will run and partially work if the
> code (the lines indicated below) is left in,-- it will fork, detach, and
> sleep but fail to get the command prompt on the remote machine.
> I have it log to a file (LOG_FILE), because when it is daemonized I cannot
> see the output.
> 
> The only thing I can think of is that ssh must do something to the
> terminal/console that works
> when I run it manually on the console, but when the program
> is daemonized, ssh cannot do whatever it is trying to do and fails.
> 
> The segment below fails saying "never got command prompt".  This means that
> it got the password prompt from the remote machine
> and sent the password, but never got the command prompt after that.
> 
> I don't think this is an expect problem, I think that it is a problem with
> how ssh and expect work together.
> My guess is that ssh is not intentionally failing, but it is trying to do
> something that does not work with the terminal that expect uses.
> 
> I have even tried "ssh -l root" to specify the username, "ssh -T" so ssh
> won't allocate a pseudo-tty, and not setting the pty to raw; all to no
> avail.
> 
> Does anyone have any ideas?
> Below is the code segment.
> 
> Thanks,
> -Chris Muth
> 
> 
> #!/usr/bin/perl5.8 -w
> 
> #prompt user for host to login to, and password
> print"host: ";$host=<STDIN>;chomp$host;
> print"pass: ";$pass=<STDIN>;chomp$pass;
> 
> use Expect;
> use POSIX;
> 
> #  Comment out daemonizing code starting here
> #######################################
> $pid = fork();
> exit 0 if ($pid);
> 
> POSIX::setsid();
> close STDIN;
> close STDOUT;
> close STDERR;
> 
> sleep 5;
> #######################################
> # comment out daemonizing code ending here
> 
> open (LOG_FILE, "> output"); # open log file
> 
> $exp = new Expect;
> $exp->raw_pty(1);
> 
> # login to the remote host
> #$exp->spawn("/usr/local/bin/ssh",'-T',"$host");  # Even tried ssh -T
> $exp->spawn("/usr/local/bin/ssh","$host");
> 
> # wait for Password: prompt
> $retval = $exp->expect(30,'-re','word:\s$');
> if (!defined $retval){
>    print LOG_FILE "Never got password prompt\n"; flush LOG_FILE;
> } else {
>    $exp->send("$pass\n");
>    #($retval,undef,$retstr,undef,undef) = $exp->expect(30,'stdin: is not a tty'); # for ssh -T
>    ($retval,undef,$retstr,undef,undef) = $exp->expect(30,'# ');
> 
>    # do something on the remote machine, test results
>    if (!defined $retval){
>       print LOG_FILE "Never got command prompt\n"; flush LOG_FILE;
>    } else {
>       print LOG_FILE "\"$retstr\"\n"; flush LOG_FILE;
>       $exp->send("echo Hello World\n");
>       $exp->expect(5,'This will make expect sleep for 5 seconds');
>       $exp->send("logout\n");
>       print LOG_FILE "It worked\n"; flush LOG_FILE;
>    }
> }
> $exp->hard_close();
> print LOG_FILE "\n"; flush LOG_FILE;
> close LOG_FILE;
> exit 0;
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Expectperl-discuss mailing list
> Exp...@li...
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss

Have you tried setting
	$Expect::Exp_Internal=1;
before creating your expect object?

This will produce a lot of debugging info that may help
you locate the cause of your trouble.

--
John
_________________________________________________________
John Mahoney

RE: [Expectperl-discuss] ssh works from console but not once daem onized

[Chris M. <mut...@mc...>]

On 9/15/03 at 9:28 AM Chr...@Ve... wrote:

>Maybe you have already done this, but have you take account for the fact
>that the first time you log into a machine with ssh you will get the "RSA
>key fingerprint" message.  I ran into this problem launching script out of
>crontab.  Even though it was running as me and I have connected to that
>machine before, it still needed to do the "RSA key fingerprint" for some
>reason.
>
I just checked that out.  ssh will ask for the authorization to connect to=
 a host
before asking for the password.  My script gets past that point.

Thanks for the idea though.

>But again just something I ran into once upon a time ago.
>
>Oh yeah and Rolad will probably tell you to use Net::SSH :)
>
Oh I hope not, I have investigated that option, it is not (an option).

-Chris Muth

[Expectperl-discuss] ssh works from console but not once daemonized

[Chris M. <mut...@mc...>]

Hi,

I am working on a script that daemonizes and then uses
ssh to login/operate/logout of a remote machine.

The code works perfectly when it is not demonized, (with the demonization
code commented out).  The script will run and partially work if the
code (the lines indicated below) is left in,-- it will fork, detach, and
sleep but fail to get the command prompt on the remote machine.
I have it log to a file (LOG_FILE), because when it is daemonized I cannot
see the output.

The only thing I can think of is that ssh must do something to the
terminal/console that works
when I run it manually on the console, but when the program
is daemonized, ssh cannot do whatever it is trying to do and fails.

The segment below fails saying "never got command prompt".  This means that
it got the password prompt from the remote machine
and sent the password, but never got the command prompt after that.

I don't think this is an expect problem, I think that it is a problem with
how ssh and expect work together.
My guess is that ssh is not intentionally failing, but it is trying to do
something that does not work with the terminal that expect uses.

I have even tried "ssh -l root" to specify the username, "ssh -T" so ssh
won't allocate a pseudo-tty, and not setting the pty to raw; all to no
avail.

Does anyone have any ideas?
Below is the code segment.

Thanks,
-Chris Muth


#!/usr/bin/perl5.8 -w

#prompt user for host to login to, and password
print"host: ";$host=3D<STDIN>;chomp$host;
print"pass: ";$pass=3D<STDIN>;chomp$pass;

use Expect;
use POSIX;

#  Comment out daemonizing code starting here
#######################################
$pid =3D fork();
exit 0 if ($pid);

POSIX::setsid();
close STDIN;
close STDOUT;
close STDERR;

sleep 5;
#######################################
# comment out daemonizing code ending here

open (LOG_FILE, "> output"); # open log file

$exp =3D new Expect;
$exp->raw_pty(1);

# login to the remote host
#$exp->spawn("/usr/local/bin/ssh",'-T',"$host");  # Even tried ssh -T
$exp->spawn("/usr/local/bin/ssh","$host");

# wait for Password: prompt
$retval =3D $exp->expect(30,'-re','word:\s$');
if (!defined $retval){
   print LOG_FILE "Never got password prompt\n"; flush LOG_FILE;
} else {
   $exp->send("$pass\n");
   #($retval,undef,$retstr,undef,undef) =3D $exp->expect(30,'stdin: is not=
 a tty'); # for ssh -T
   ($retval,undef,$retstr,undef,undef) =3D $exp->expect(30,'# ');

   # do something on the remote machine, test results
   if (!defined $retval){
      print LOG_FILE "Never got command prompt\n"; flush LOG_FILE;
   } else {
      print LOG_FILE "\"$retstr\"\n"; flush LOG_FILE;
      $exp->send("echo Hello World\n");
      $exp->expect(5,'This will make expect sleep for 5 seconds');
      $exp->send("logout\n");
      print LOG_FILE "It worked\n"; flush LOG_FILE;
   }
}
$exp->hard_close();
print LOG_FILE "\n"; flush LOG_FILE;
close LOG_FILE;
exit 0;

[Expectperl-discuss] expect issues with gdb ii

[Andrew & L. W. <and...@ve...>]

I posted a question about gdb and using ctrl c. Found the problem, I was
putting the terminal and slave pty in raw mode and thus disabling the
ctrlc->sigint behavior that a non-raw terminal does. Anyway, thought I would
post the answer to the problem in case anyone else finds this problem too.

aw

Re: [Expectperl-discuss] Using Expect in ssh

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

jaws wrote:
> How will I use Expect to connect to and execute a command on a remote host.

You won't. You will use ssh to do that, either the command-line client 
or one of its Perl cousins, Net::SSH or Net::SSH::Perl. And you will set 
up authentication using private and public keys as it was meant for ssh. 
And you will not store passwords in plaintext somewhere in your scripts.

:o)

Roland
--
RGi...@cp...

Re: [Expectperl-discuss] Using Expect in ssh

[expect <ex...@ih...>]

On Wed, 3 Sep 2003 14:02:18 +0800
"jaws" <ja...@sk...> wrote:

> Hi all,
> 
> How will I use Expect to connect to and execute a command on a remote host.

Is this where we are to guess how you will do it?  I'd hate to spoil it for
everyone else. ;^)  Seriously, there are examples of that recently in this list.
Search the archives.

> 
> thanks
> 
> jaws

[Expectperl-discuss] Using Expect in ssh

[jaws <ja...@sk...>]

Hi all,

How will I use Expect to connect to and execute a command on a remote host.

thanks

jaws

---------------
Computer system security is a journey, not a destination.

Re: [Expectperl-discuss] Can't reference $exp->slave after $exp->spawn

[Steve T. <ste...@su...>]

> If I switch the order of lines 4 and 5, the error goes away.

Sorry, this should be:

If I switch the order of lines 6 and 7, the error goes away.

Thanks,

Steve

Steve Talley wrote:

> Hello,
> 
> I'm running perl 5.8.0, Expect 1.15, Tty and Pty 1.02.  When I run
> this code:
> 
>     1. #!/usr/bin/perl
>     2.
>     3. use Epect;
>     4.
>     5. my $exp = new Expect;
>     6. $exp->spawn('bash') or die "Cannot spawn $sshcmd: $!\n";
>     7. $exp->slave->clone_winsize_from(\*STDIN);
> 
> I get:
> 
>     Cannot open slave : No such file or directory at /tmp/example.pm line 7
> 
> If I switch the order of lines 4 and 5, the error goes away.  The
> problem is that the script just halts immediately with this error if I
> ever reference $exp->slave after I've called $exp->spawn().
> Unfortunately I need this to work so that I can use the WINCH signal
> handler detailed in the man page.
> 
> I ran a truss (strace) on the process, and found these lines:
> 
>     ioctl(137425816, SNDCTL_TMR_TIMEBASE, 0xbfffeca0) = -1 EBADF (Bad file descriptor)
>     open("", O_RDWR|O_NOCTTY|O_LARGEFILE)   = -1 ENOENT (No such file or directory)
> 
> Any ideas why this is failing?
> 
> Thanks,
> 
> Steve
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Expectperl-discuss mailing list
> Exp...@li...
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss

[Expectperl-discuss] Can't reference $exp->slave after $exp->spawn

[Steve T. <ste...@su...>]

Hello,

I'm running perl 5.8.0, Expect 1.15, Tty and Pty 1.02.  When I run
this code:

    1. #!/usr/bin/perl
    2.
    3. use Epect;
    4.
    5. my $exp = new Expect;
    6. $exp->spawn('bash') or die "Cannot spawn $sshcmd: $!\n";
    7. $exp->slave->clone_winsize_from(\*STDIN);

I get:

    Cannot open slave : No such file or directory at /tmp/example.pm line 7

If I switch the order of lines 4 and 5, the error goes away.  The
problem is that the script just halts immediately with this error if I
ever reference $exp->slave after I've called $exp->spawn().
Unfortunately I need this to work so that I can use the WINCH signal
handler detailed in the man page.

I ran a truss (strace) on the process, and found these lines:

    ioctl(137425816, SNDCTL_TMR_TIMEBASE, 0xbfffeca0) = -1 EBADF (Bad file descriptor)
    open("", O_RDWR|O_NOCTTY|O_LARGEFILE)   = -1 ENOENT (No such file or directory)

Any ideas why this is failing?

Thanks,

Steve

Re: [Expectperl-discuss] expect closing port handle

[Sayre S. <sa...@qu...>]

I eventually fixed the problem by tediously debugging with the perl 
debugger.

I was using a serial port both for ascii communication (cooked stty) and 
binary protocol xfers (raw stty), switching back and forth between the 
modes. Sometimes when the binary xfer was over and I set the port stty 
back to cooked, the other side had not yet finished the xfer. If it sent 
a ^D the Expect.pm module would close the port.

I tried to set stty eof to undef after setting stty to cooked, but it 
the Stty.pm would not take a non-numeric argument on the eof parm. I set 
eof to 0 and it works fine now, even if there is a communication error. 
I removed my patch from Expect.pm and am getting good results even under 
error conditions.

Thank you,
Sayre Swarztrauber


Roland Giersig wrote:

> sorry for the belated reply...
>
> expect wrote:
>
>> On Mon, 04 Aug 2003 17:19:18 -0400
>> Sayre Swarztrauber <sa...@qu...> wrote:
>>
>>
>>> I am new to Expect. I am using it to control some serial devices 
>>> that our company manufactures. They are connected on /dev/tty ports 
>>> directly as RS232 devices. I open the port using IO::File and then 
>>> connect that handle to Expect.
>>>
>>> I have a problem where Expect.pm occasionally closes the filehandle 
>>> on the port giving the following message from the debug output:
>>>
>>> Waiting for new data (6 seconds)...
>>> handle id(3): new data.
>>> handle id(3): EOF
>>> handle id(3): closing...
>>> Returning from expect with TIMEOUT or EOF
>>>
>>>
>>> I have patched my problem by commenting out the      
>>> $exp->hard_close();
>>>
>>> on line 853 of Expect.pm - which I realize is a drastic step.
>>>
>>> What am I doing wrong? Why would expect decide to close my 
>>> filehandle? What can I do about it so that I do not have to modify 
>>> the Expect.pm program.
>>
>
> this works as intended, the other side (spwaned program) has closed 
> its stdout, which normally is an indication that the program exits. if 
> you need a more fine-grained control over the input and output 
> streams, take a look at IPC::Run.
>
>
>>>
>>> Any help would be greatly appreciated.
>>
>>
>>
>>
>> This sounds familiar to me...something about been there and done that.
>> Of course this may not be your problem.
>>
>> I simply didn't understand that to cause Expect to wait forever on
>> a pattern match the perl 'undef' function has to be used in place of
>> a $timeout value.  What I did was just not define it and it didn't do
>> what I Expect'd.
>>
>> my $proghandle = new Expect;
>> $proghandle = Expect->spawn($myprog);
>> $proghandle->expect(undef, $whatiamexpecting);
>>
>>
>> It may make sense to modify the docs slightly to point out that the
>> perl function undef should be specified.
>>
>>
>> perldoc Expect
>>
>> "Simple interface:
>>
>>  Given $timeout in seconds Expect will wait for $object's handle to
>>  produce one of the match_patterns. Due to o/s limitations $timeout
>>  should be a round number. If $timeout is 0 Expect will check one
>>  time to see if $object's handle contains any of the match_patterns.
>>  If $timeout is undef Expect will wait forever for a pattern to
>>  match."
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
>> Data Reports, E-commerce, Portals, and Forums are available now.
>> Download today and enter to win an XBOX or Visual Studio .NET.
>> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 
>>
>> _______________________________________________
>> Expectperl-discuss mailing list
>> Exp...@li...
>> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Expectperl-discuss mailing list
> Exp...@li...
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss

Re: [Expectperl-discuss] expect closing port handle

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

On Wed, Aug 27, 2003 at 09:22:45AM +0200, Roland Giersig wrote:
> >>I have patched my problem by commenting out the       
> >>
> >> $exp->hard_close();
> >>
> >>on line 853 of Expect.pm - which I realize is a drastic step.
> >>
> >>What am I doing wrong? Why would expect decide to close my filehandle? 
> >>What can I do about it so that I do not have to modify the Expect.pm 
> >>program.
> 
> this works as intended, the other side (spwaned program) has closed its 
> stdout, which normally is an indication that the program exits. if you 
> need a more fine-grained control over the input and output streams, take 
> a look at IPC::Run.

	Yes, this is true, _normally_, and maybe it would be worthwhile to
try a non-blocking waitpid, or even block a couple seconds and do that.
hard_close() will explicitly _kill_ the process, however. That doesn't seem
like intuitive behavior during an expect() call, imo.
	soft_close might be a good choice, except that it also will kill
the process if it doesn't go away after the handle is closed. What it should
do (and should have done, my fault) is merely close the handle and wait for
a bit, returning an error if the process doesn't go away by itself. Again
that's all just imo.

	Austin

Re: [Expectperl-discuss] expect closing port handle

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

sorry for the belated reply...

expect wrote:
> On Mon, 04 Aug 2003 17:19:18 -0400
> Sayre Swarztrauber <sa...@qu...> wrote:
> 
> 
>>I am new to Expect. I am using it to control some serial devices that 
>>our company manufactures. They are connected on /dev/tty ports directly 
>>as RS232 devices. I open the port using IO::File and then connect that 
>>handle to Expect.
>>
>>I have a problem where Expect.pm occasionally closes the filehandle on 
>>the port giving the following message from the debug output:
>>
>>Waiting for new data (6 seconds)...
>>handle id(3): new data.
>>handle id(3): EOF
>>handle id(3): closing...
>>Returning from expect with TIMEOUT or EOF
>>
>>
>>I have patched my problem by commenting out the       
>>
>> $exp->hard_close();
>>
>>on line 853 of Expect.pm - which I realize is a drastic step.
>>
>>What am I doing wrong? Why would expect decide to close my filehandle? 
>>What can I do about it so that I do not have to modify the Expect.pm 
>>program.

this works as intended, the other side (spwaned program) has closed its 
stdout, which normally is an indication that the program exits. if you 
need a more fine-grained control over the input and output streams, take 
a look at IPC::Run.


>>
>>Any help would be greatly appreciated.
> 
> 
> 
> This sounds familiar to me...something about been there and done that.
> Of course this may not be your problem.
> 
> I simply didn't understand that to cause Expect to wait forever on
> a pattern match the perl 'undef' function has to be used in place of
> a $timeout value.  What I did was just not define it and it didn't do
> what I Expect'd.
> 
> my $proghandle = new Expect;
> $proghandle = Expect->spawn($myprog);
> $proghandle->expect(undef, $whatiamexpecting);
> 
> 
> It may make sense to modify the docs slightly to point out that the
> perl function undef should be specified.
> 
> 
> perldoc Expect
> 
> "Simple interface:
> 
>  Given $timeout in seconds Expect will wait for $object's handle to
>  produce one of the match_patterns. Due to o/s limitations $timeout
>  should be a round number. If $timeout is 0 Expect will check one
>  time to see if $object's handle contains any of the match_patterns.
>  If $timeout is undef Expect will wait forever for a pattern to
>  match."
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Expectperl-discuss mailing list
> Exp...@li...
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
> 

Re: [Expectperl-discuss] Problem with GLOB Reference in Expect.pm

[Sayre S. <sa...@qu...>]

Thank you for all of your replies.

By reading all of your comments and looking at my code I discovered my 
problem. I had created an object. The filehandle to the Expect object 
lived only as an attribute my object. My object lived inside of a loop 
as a local variable, and I had put the closure of the Expect file object 
of the outside of the loop in which my object lived. However, my object 
was destroyed when the loop ended because its scope had terminated, so 
perl closed my file when my loop ended.

I fixed the problem by putting a DESTROY method in my object package 
into which I moved my file closing code which had been outside of the 
loop where my object lived.

Sayre Swarztrauber


Austin Schutz wrote:

>On Mon, Aug 25, 2003 at 07:26:27AM -0500, Rogaski, Mark, ALABS wrote:
>  
>
>>I suspect that you are closing the file handles elsewhere in your
>>program, and Expect is simply carping because the handles it wants to
>>clean up and close are missing.
>>    
>>
>
>	I had thought that might be the case too, but now I'm thinking that
>probably isn't the case. It doesn't make sense that closing the associated
>handle would somehow make a reference no longer point to a glob.
>	I'm thinking it's probably something like a bug in perl's reference
>counter, or something like that. If you modify the code to test if each
>reference isa() GLOB before the problematic parts, that might be a bandaid.
>Ugly, but I'm not sure what else could be done.
>	If you go down that road please let us know what worked.
>
>
>	Austin
>	
>
>  
>
>>I've attached a "cosmetic" patch to get
>>rid of the error message (as always, use at your own risk).  But, you
>>may want to figure out whether the file handles are being closed nicely.
>> 
>>Mark 
>>
>>-- 
>>Mark Rogaski                     "Computers save time like kudzu
>>prevents 
>>Multi-service Data Field Support          soil erosion." -- Al Castanoli
>>
>>email: ro...@at... voice: +1-732-885-7534 
>>pager: +1-888-858-7243 p: 200853 or 20...@pa... 
>>
>>-----Original Message-----
>>From: Sayre Swarztrauber [mailto:sa...@qu...]
>>Sent: Friday, August 22, 2003 3:53 PM
>>To: Rogaski, Mark, ALABS
>>Cc: Expectperl-Discuss (E-mail)
>>Subject: Re: [Expectperl-discuss] Problem with GLOB Reference in
>>Expect.pm
>>
>>
>>I am creating it with exp_init().
>>
>>Rogaski, Mark, ALABS wrote:
>>
>>
>>It looks like the filehandle is disappearing before the Expect
>>
>>destructor is called.  Are you creating the Expect object with spawn()
>>
>>or exp_init()?
>>
>>
>>
>>Mark
>>
>>
>>
>>--
>>
>>Mark Rogaski                     "Computers save time like kudzu
>>
>>prevents
>>
>>Multi-service Data Field Support          soil erosion." -- Al Castanoli
>>
>>email:  ro...@at... voice: +1-732-885-7534
>>
>>pager: +1-888-858-7243 p: 200853 or  20...@pa...
>>
>>
>>
>>
>>
>>-----Original Message-----
>>
>>From: Sayre Swarztrauber [ mailto:sa...@qu...]
>>
>>Sent: Friday, August 22, 2003 2:07 PM
>>
>>To: Expectperl-Discuss (E-mail)
>>
>>Subject: Re: [Expectperl-discuss] Problem with GLOB Reference in
>>
>>Expect.pm
>>
>>
>>
>>
>>
>>I have a similar problem **whenever** my program exits:
>>
>>
>>
>>(in cleanup) Not a GLOB reference at 
>>
>>/usr/lib/perl5/site_perl/5.8.0/Expect.pm line 1572.
>>
>>
>>
>>I am also interested in a way to stop that from happening.
>>
>>
>>
>>Thank you.
>>
>>
>>
>>
>>
>>Sayre Swarztrauber
>>
>>Quadlogic
>>
>>New York
>>
>>
>>
>>
>>
>>Kemp, Donald wrote:
>>
>>
>>
>>  
>>
>>Hi,
>>
>>I am intermittently getting the following message  ....
>>
>>	Not a GLOB reference at
>>
>>/usr/local/lib/perl5/site_perl/5.6.1/Expect.pm line 256.
>>
>>This happens on a Solaris 8 system running Perl 5.6.1 and Expect 1.15.
>>
>>    
>>
>>The
>>
>>  
>>
>>problem is occurring on a production system that has multiple fast
>>
>>processors and a very large amount of memory. It seems to be occurring
>>
>>    
>>
>>more
>>
>>  
>>
>>often as the number of users on the system that are using my code
>>
>>    
>>
>>increases.
>>
>>  
>>
>>I do not see the problem on my "slower" test system running the same
>>
>>    
>>
>>level
>>
>>  
>>
>>of software. Does anyone have any idea what may be triggering this
>>
>>    
>>
>>error?
>>
>>  
>>
>>What can I do to try an isolate what the cause of the problem may be??
>>
>>
>>
>>Best Regards,
>>
>>Donald.E.S.Kemp
>>
>>AT&T
>>
>>Network Management Solutions,
>>
>>Building 6000, Langstone Technology Park,
>>
>>Langstone Road,  Havant, Hampshire,
>>
>>United Kingdom,
>>
>>PO9 1SA
>>
>>Phone:  +44(0)23 9222 8424
>>
>>email:   dk...@em...
>>
>>
>>
>>This message and any attachments to it contain confidential business
>>
>>information exclusively intended for the recipients. Please do not
>>
>>    
>>
>>forward
>>
>>  
>>
>>or distribute it to anyone else. If you have received this e-mail in
>>
>>    
>>
>>error,
>>
>>  
>>
>>please call [+44 (0)23 92228424] to report the error and then delete
>>
>>    
>>
>>this
>>
>>  
>>
>>message from your system.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>
>>This SF.net email is sponsored by: VM Ware
>>
>>With VMware you can run multiple operating systems on a single machine.
>>
>>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
>>
>>at the same time. Free trial click
>>
>>    
>>
>>here: http://www.vmware.com/wl/offer/358/0
>>
>>  
>>
>>_______________________________________________
>>
>>Expectperl-discuss mailing list
>>
>>Exp...@li...
>>
>>https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>>
>> 
>>
>>
>>
>>    
>>
>>
>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>
>>This SF.net email is sponsored by: VM Ware
>>
>>With VMware you can run multiple operating systems on a single machine.
>>
>>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
>>
>>at the same time. Free trial click
>>
>>here: http://www.vmware.com/wl/offer/358/0
>>
>>_______________________________________________
>>
>>Expectperl-discuss mailing list
>>
>>Exp...@li...
>>
>>https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>
>>This SF.net email is sponsored by: VM Ware
>>
>>With VMware you can run multiple operating systems on a single machine.
>>
>>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
>>
>>at the same time. Free trial click here:
>>http://www.vmware.com/wl/offer/358/0
>>
>>_______________________________________________
>>
>>Expectperl-discuss mailing list
>>
>>Exp...@li...
>>
>>https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>>
>>  
>>
>>    
>>
>
>Content-Description: Expect_pm_globref_patch.txt
>  
>
>>*** /usr/local/lib/perl5/site_perl/5.6.1/Expect.pm	Tue Mar 19 06:59:29 2002
>>--- Expect.pm	Fri Aug 22 15:12:39 2003
>>***************
>>*** 1569,1578 ****
>>  # clean up child processes
>>  sub DESTROY {
>>    my $self = shift;
>>!   if (${*$self}{exp_Do_Soft_Close}) {
>>!     $self->soft_close();
>>    }
>>-   $self->hard_close();
>>  }
>>  
>>  1;
>>--- 1569,1580 ----
>>  # clean up child processes
>>  sub DESTROY {
>>    my $self = shift;
>>!   if (defined $self->fileno()) {
>>!     if (${*$self}{exp_Do_Soft_Close}) {
>>!       $self->soft_close();
>>!     }
>>!     $self->hard_close();
>>    }
>>  }
>>  
>>  1;
>>    
>>

Re: [Expectperl-discuss] Problem with GLOB Reference in Expect.pm

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

On Tue, Aug 26, 2003 at 10:09:29AM +0100, Kemp, Donald wrote:
> Hi,
> In my case I am using spawn(). The only time I use exp_init is for the
> filehandles used when I am setting up for a "Expect::interconnect".
> 
> The "Expect" sub-routine that I am seeing the failure is AUTOLOAD and the
> line that the failure is indicated on is  ....
> $tmp = ${*$self}{varname} if exists ${*self}{$varname};
> 

	Which again doesn't seem like an Expect bug, per se. However,
if it's not defined here it's likely not going to work later either, so
it might as well toss up some sort of error code, or at least return undef.
	I would suggest ways to debug this, but I'm not really that familiar
with the autoloading mechanism, and I've never had the pleasure of having
references disappear from under me.

	Austin

RE: [Expectperl-discuss] Problem with GLOB Reference in Expect.pm

[Kemp, D. <dk...@em...>]

Hi,
In my case I am using spawn(). The only time I use exp_init is for the
filehandles used when I am setting up for a "Expect::interconnect".

The "Expect" sub-routine that I am seeing the failure is AUTOLOAD and the
line that the failure is indicated on is  ....
$tmp = ${*$self}{varname} if exists ${*self}{$varname};

Best Regards,
Donald.E.S.Kemp
AT&T
Network Management Solutions,
Building 6000, Langstone Technology Park,
Langstone Road,  Havant, Hampshire,
United Kingdom,
PO9 1SA
Phone:  +44(0)23 9222 8424
email:  dk...@em...

This message and any attachments to it contain confidential business
information exclusively intended for the recipients. Please do not forward
or distribute it to anyone else. If you have received this e-mail in error,
please call [+44 (0)23 92228424] to report the error and then delete this
message from your system.






-----Original Message-----
From: Rogaski, Mark, ALABS [mailto:ro...@at...]
Sent: 22 August 2003 20:18
To: Sayre Swarztrauber; Expectperl-Discuss (E-mail)
Subject: RE: [Expectperl-discuss] Problem with GLOB Reference in
Expect.pm


It looks like the filehandle is disappearing before the Expect
destructor is called.  Are you creating the Expect object with spawn()
or exp_init()?

Mark

--
Mark Rogaski                     "Computers save time like kudzu
prevents
Multi-service Data Field Support          soil erosion." -- Al Castanoli
email: ro...@at... voice: +1-732-885-7534
pager: +1-888-858-7243 p: 200853 or 20...@pa...


-----Original Message-----
From: Sayre Swarztrauber [mailto:sa...@qu...]
Sent: Friday, August 22, 2003 2:07 PM
To: Expectperl-Discuss (E-mail)
Subject: Re: [Expectperl-discuss] Problem with GLOB Reference in
Expect.pm


I have a similar problem **whenever** my program exits:

(in cleanup) Not a GLOB reference at 
/usr/lib/perl5/site_perl/5.8.0/Expect.pm line 1572.

I am also interested in a way to stop that from happening.

Thank you.


Sayre Swarztrauber
Quadlogic
New York


Kemp, Donald wrote:

>Hi,
>I am intermittently getting the following message  ....
>	Not a GLOB reference at
>/usr/local/lib/perl5/site_perl/5.6.1/Expect.pm line 256.
>This happens on a Solaris 8 system running Perl 5.6.1 and Expect 1.15.
The
>problem is occurring on a production system that has multiple fast
>processors and a very large amount of memory. It seems to be occurring
more
>often as the number of users on the system that are using my code
increases.
>I do not see the problem on my "slower" test system running the same
level
>of software. Does anyone have any idea what may be triggering this
error?
>What can I do to try an isolate what the cause of the problem may be??
>
>Best Regards,
>Donald.E.S.Kemp
>AT&T
>Network Management Solutions,
>Building 6000, Langstone Technology Park,
>Langstone Road,  Havant, Hampshire,
>United Kingdom,
>PO9 1SA
>Phone:  +44(0)23 9222 8424
>email:  dk...@em...
>
>This message and any attachments to it contain confidential business
>information exclusively intended for the recipients. Please do not
forward
>or distribute it to anyone else. If you have received this e-mail in
error,
>please call [+44 (0)23 92228424] to report the error and then delete
this
>message from your system.
>
>
>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: VM Ware
>With VMware you can run multiple operating systems on a single machine.
>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
>at the same time. Free trial click
here:http://www.vmware.com/wl/offer/358/0
>_______________________________________________
>Expectperl-discuss mailing list
>Exp...@li...
>https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>  
>



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click
here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
Expectperl-discuss mailing list
Exp...@li...
https://lists.sourceforge.net/lists/listinfo/expectperl-discuss


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
Expectperl-discuss mailing list
Exp...@li...
https://lists.sourceforge.net/lists/listinfo/expectperl-discuss

Re: [Expectperl-discuss] Problem with GLOB Reference in Expect.pm

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

On Mon, Aug 25, 2003 at 07:26:27AM -0500, Rogaski, Mark, ALABS wrote:
> I suspect that you are closing the file handles elsewhere in your
> program, and Expect is simply carping because the handles it wants to
> clean up and close are missing.

	I had thought that might be the case too, but now I'm thinking that
probably isn't the case. It doesn't make sense that closing the associated
handle would somehow make a reference no longer point to a glob.
	I'm thinking it's probably something like a bug in perl's reference
counter, or something like that. If you modify the code to test if each
reference isa() GLOB before the problematic parts, that might be a bandaid.
Ugly, but I'm not sure what else could be done.
	If you go down that road please let us know what worked.


	Austin
	

> I've attached a "cosmetic" patch to get
> rid of the error message (as always, use at your own risk).  But, you
> may want to figure out whether the file handles are being closed nicely.
>  
> Mark 
> 
> -- 
> Mark Rogaski                     "Computers save time like kudzu
> prevents 
> Multi-service Data Field Support          soil erosion." -- Al Castanoli
> 
> email: ro...@at... voice: +1-732-885-7534 
> pager: +1-888-858-7243 p: 200853 or 20...@pa... 
> 
> -----Original Message-----
> From: Sayre Swarztrauber [mailto:sa...@qu...]
> Sent: Friday, August 22, 2003 3:53 PM
> To: Rogaski, Mark, ALABS
> Cc: Expectperl-Discuss (E-mail)
> Subject: Re: [Expectperl-discuss] Problem with GLOB Reference in
> Expect.pm
> 
> 
> I am creating it with exp_init().
> 
> Rogaski, Mark, ALABS wrote:
> 
> 
> It looks like the filehandle is disappearing before the Expect
> 
> destructor is called.  Are you creating the Expect object with spawn()
> 
> or exp_init()?
> 
> 
> 
> Mark
> 
> 
> 
> --
> 
> Mark Rogaski                     "Computers save time like kudzu
> 
> prevents
> 
> Multi-service Data Field Support          soil erosion." -- Al Castanoli
> 
> email:  ro...@at... voice: +1-732-885-7534
> 
> pager: +1-888-858-7243 p: 200853 or  20...@pa...
> 
> 
> 
> 
> 
> -----Original Message-----
> 
> From: Sayre Swarztrauber [ mailto:sa...@qu...]
> 
> Sent: Friday, August 22, 2003 2:07 PM
> 
> To: Expectperl-Discuss (E-mail)
> 
> Subject: Re: [Expectperl-discuss] Problem with GLOB Reference in
> 
> Expect.pm
> 
> 
> 
> 
> 
> I have a similar problem **whenever** my program exits:
> 
> 
> 
> (in cleanup) Not a GLOB reference at 
> 
> /usr/lib/perl5/site_perl/5.8.0/Expect.pm line 1572.
> 
> 
> 
> I am also interested in a way to stop that from happening.
> 
> 
> 
> Thank you.
> 
> 
> 
> 
> 
> Sayre Swarztrauber
> 
> Quadlogic
> 
> New York
> 
> 
> 
> 
> 
> Kemp, Donald wrote:
> 
> 
> 
>   
> 
> Hi,
> 
> I am intermittently getting the following message  ....
> 
> 	Not a GLOB reference at
> 
> /usr/local/lib/perl5/site_perl/5.6.1/Expect.pm line 256.
> 
> This happens on a Solaris 8 system running Perl 5.6.1 and Expect 1.15.
> 
>     
> 
> The
> 
>   
> 
> problem is occurring on a production system that has multiple fast
> 
> processors and a very large amount of memory. It seems to be occurring
> 
>     
> 
> more
> 
>   
> 
> often as the number of users on the system that are using my code
> 
>     
> 
> increases.
> 
>   
> 
> I do not see the problem on my "slower" test system running the same
> 
>     
> 
> level
> 
>   
> 
> of software. Does anyone have any idea what may be triggering this
> 
>     
> 
> error?
> 
>   
> 
> What can I do to try an isolate what the cause of the problem may be??
> 
> 
> 
> Best Regards,
> 
> Donald.E.S.Kemp
> 
> AT&T
> 
> Network Management Solutions,
> 
> Building 6000, Langstone Technology Park,
> 
> Langstone Road,  Havant, Hampshire,
> 
> United Kingdom,
> 
> PO9 1SA
> 
> Phone:  +44(0)23 9222 8424
> 
> email:   dk...@em...
> 
> 
> 
> This message and any attachments to it contain confidential business
> 
> information exclusively intended for the recipients. Please do not
> 
>     
> 
> forward
> 
>   
> 
> or distribute it to anyone else. If you have received this e-mail in
> 
>     
> 
> error,
> 
>   
> 
> please call [+44 (0)23 92228424] to report the error and then delete
> 
>     
> 
> this
> 
>   
> 
> message from your system.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> 
> This SF.net email is sponsored by: VM Ware
> 
> With VMware you can run multiple operating systems on a single machine.
> 
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
> 
> at the same time. Free trial click
> 
>     
> 
> here: http://www.vmware.com/wl/offer/358/0
> 
>   
> 
> _______________________________________________
> 
> Expectperl-discuss mailing list
> 
> Exp...@li...
> 
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
> 
>  
> 
> 
> 
>     
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> 
> This SF.net email is sponsored by: VM Ware
> 
> With VMware you can run multiple operating systems on a single machine.
> 
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
> 
> at the same time. Free trial click
> 
> here: http://www.vmware.com/wl/offer/358/0
> 
> _______________________________________________
> 
> Expectperl-discuss mailing list
> 
> Exp...@li...
> 
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
> 
> 
> 
> 
> 
> -------------------------------------------------------
> 
> This SF.net email is sponsored by: VM Ware
> 
> With VMware you can run multiple operating systems on a single machine.
> 
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
> 
> at the same time. Free trial click here:
> http://www.vmware.com/wl/offer/358/0
> 
> _______________________________________________
> 
> Expectperl-discuss mailing list
> 
> Exp...@li...
> 
> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
> 
>   
> 

Content-Description: Expect_pm_globref_patch.txt
> *** /usr/local/lib/perl5/site_perl/5.6.1/Expect.pm	Tue Mar 19 06:59:29 2002
> --- Expect.pm	Fri Aug 22 15:12:39 2003
> ***************
> *** 1569,1578 ****
>   # clean up child processes
>   sub DESTROY {
>     my $self = shift;
> !   if (${*$self}{exp_Do_Soft_Close}) {
> !     $self->soft_close();
>     }
> -   $self->hard_close();
>   }
>   
>   1;
> --- 1569,1580 ----
>   # clean up child processes
>   sub DESTROY {
>     my $self = shift;
> !   if (defined $self->fileno()) {
> !     if (${*$self}{exp_Do_Soft_Close}) {
> !       $self->soft_close();
> !     }
> !     $self->hard_close();
>     }
>   }
>   
>   1;

RE: [Expectperl-discuss] Problem with GLOB Reference in Expect.pm

[Rogaski, M. A. <ro...@at...>]

KioqIC91c3IvbG9jYWwvbGliL3Blcmw1L3NpdGVfcGVybC81LjYuMS9FeHBlY3QucG0JVHVlIE1h
ciAxOSAwNjo1OToyOSAyMDAyDQotLS0gRXhwZWN0LnBtCUZyaSBBdWcgMjIgMTU6MTI6MzkgMjAw
Mw0KKioqKioqKioqKioqKioqDQoqKiogMTU2OSwxNTc4ICoqKioNCiAgIyBjbGVhbiB1cCBjaGls
ZCBwcm9jZXNzZXMNCiAgc3ViIERFU1RST1kgew0KICAgIG15ICRzZWxmID0gc2hpZnQ7DQohICAg
aWYgKCR7KiRzZWxmfXtleHBfRG9fU29mdF9DbG9zZX0pIHsNCiEgICAgICRzZWxmLT5zb2Z0X2Ns
b3NlKCk7DQogICAgfQ0KLSAgICRzZWxmLT5oYXJkX2Nsb3NlKCk7DQogIH0NCiAgDQogIDE7DQot
LS0gMTU2OSwxNTgwIC0tLS0NCiAgIyBjbGVhbiB1cCBjaGlsZCBwcm9jZXNzZXMNCiAgc3ViIERF
U1RST1kgew0KICAgIG15ICRzZWxmID0gc2hpZnQ7DQohICAgaWYgKGRlZmluZWQgJHNlbGYtPmZp
bGVubygpKSB7DQohICAgICBpZiAoJHsqJHNlbGZ9e2V4cF9Eb19Tb2Z0X0Nsb3NlfSkgew0KISAg
ICAgICAkc2VsZi0+c29mdF9jbG9zZSgpOw0KISAgICAgfQ0KISAgICAgJHNlbGYtPmhhcmRfY2xv
c2UoKTsNCiAgICB9DQogIH0NCiAgDQogIDE7DQo=

Re: [Expectperl-discuss] Problem with GLOB Reference in Expect.pm

[Sayre S. <sa...@qu...>]

I am creating it with exp_init().

Rogaski, Mark, ALABS wrote:

>It looks like the filehandle is disappearing before the Expect
>destructor is called.  Are you creating the Expect object with spawn()
>or exp_init()?
>
>Mark
>
>--
>Mark Rogaski                     "Computers save time like kudzu
>prevents
>Multi-service Data Field Support          soil erosion." -- Al Castanoli
>email: ro...@at... voice: +1-732-885-7534
>pager: +1-888-858-7243 p: 200853 or 20...@pa...
>
>
>-----Original Message-----
>From: Sayre Swarztrauber [mailto:sa...@qu...]
>Sent: Friday, August 22, 2003 2:07 PM
>To: Expectperl-Discuss (E-mail)
>Subject: Re: [Expectperl-discuss] Problem with GLOB Reference in
>Expect.pm
>
>
>I have a similar problem **whenever** my program exits:
>
>(in cleanup) Not a GLOB reference at 
>/usr/lib/perl5/site_perl/5.8.0/Expect.pm line 1572.
>
>I am also interested in a way to stop that from happening.
>
>Thank you.
>
>
>Sayre Swarztrauber
>Quadlogic
>New York
>
>
>Kemp, Donald wrote:
>
>  
>
>>Hi,
>>I am intermittently getting the following message  ....
>>	Not a GLOB reference at
>>/usr/local/lib/perl5/site_perl/5.6.1/Expect.pm line 256.
>>This happens on a Solaris 8 system running Perl 5.6.1 and Expect 1.15.
>>    
>>
>The
>  
>
>>problem is occurring on a production system that has multiple fast
>>processors and a very large amount of memory. It seems to be occurring
>>    
>>
>more
>  
>
>>often as the number of users on the system that are using my code
>>    
>>
>increases.
>  
>
>>I do not see the problem on my "slower" test system running the same
>>    
>>
>level
>  
>
>>of software. Does anyone have any idea what may be triggering this
>>    
>>
>error?
>  
>
>>What can I do to try an isolate what the cause of the problem may be??
>>
>>Best Regards,
>>Donald.E.S.Kemp
>>AT&T
>>Network Management Solutions,
>>Building 6000, Langstone Technology Park,
>>Langstone Road,  Havant, Hampshire,
>>United Kingdom,
>>PO9 1SA
>>Phone:  +44(0)23 9222 8424
>>email:  dk...@em...
>>
>>This message and any attachments to it contain confidential business
>>information exclusively intended for the recipients. Please do not
>>    
>>
>forward
>  
>
>>or distribute it to anyone else. If you have received this e-mail in
>>    
>>
>error,
>  
>
>>please call [+44 (0)23 92228424] to report the error and then delete
>>    
>>
>this
>  
>
>>message from your system.
>>
>>
>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: VM Ware
>>With VMware you can run multiple operating systems on a single machine.
>>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
>>at the same time. Free trial click
>>    
>>
>here:http://www.vmware.com/wl/offer/358/0
>  
>
>>_______________________________________________
>>Expectperl-discuss mailing list
>>Exp...@li...
>>https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>> 
>>
>>    
>>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: VM Ware
>With VMware you can run multiple operating systems on a single machine.
>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
>at the same time. Free trial click
>here:http://www.vmware.com/wl/offer/358/0
>_______________________________________________
>Expectperl-discuss mailing list
>Exp...@li...
>https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: VM Ware
>With VMware you can run multiple operating systems on a single machine.
>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
>at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
>_______________________________________________
>Expectperl-discuss mailing list
>Exp...@li...
>https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>  
>

RE: [Expectperl-discuss] Problem with GLOB Reference in Expect.pm

[Rogaski, M. A. <ro...@at...>]

It looks like the filehandle is disappearing before the Expect
destructor is called.  Are you creating the Expect object with spawn()
or exp_init()?

Mark

--
Mark Rogaski                     "Computers save time like kudzu
prevents
Multi-service Data Field Support          soil erosion." -- Al Castanoli
email: ro...@at... voice: +1-732-885-7534
pager: +1-888-858-7243 p: 200853 or 20...@pa...


-----Original Message-----
From: Sayre Swarztrauber [mailto:sa...@qu...]
Sent: Friday, August 22, 2003 2:07 PM
To: Expectperl-Discuss (E-mail)
Subject: Re: [Expectperl-discuss] Problem with GLOB Reference in
Expect.pm


I have a similar problem **whenever** my program exits:

(in cleanup) Not a GLOB reference at=20
/usr/lib/perl5/site_perl/5.8.0/Expect.pm line 1572.

I am also interested in a way to stop that from happening.

Thank you.


Sayre Swarztrauber
Quadlogic
New York


Kemp, Donald wrote:

>Hi,
>I am intermittently getting the following message  ....
>	Not a GLOB reference at
>/usr/local/lib/perl5/site_perl/5.6.1/Expect.pm line 256.
>This happens on a Solaris 8 system running Perl 5.6.1 and Expect 1.15.
The
>problem is occurring on a production system that has multiple fast
>processors and a very large amount of memory. It seems to be occurring
more
>often as the number of users on the system that are using my code
increases.
>I do not see the problem on my "slower" test system running the same
level
>of software. Does anyone have any idea what may be triggering this
error?
>What can I do to try an isolate what the cause of the problem may be??
>
>Best Regards,
>Donald.E.S.Kemp
>AT&T
>Network Management Solutions,
>Building 6000, Langstone Technology Park,
>Langstone Road,  Havant, Hampshire,
>United Kingdom,
>PO9 1SA
>Phone:  +44(0)23 9222 8424
>email:  dk...@em...
>
>This message and any attachments to it contain confidential business
>information exclusively intended for the recipients. Please do not
forward
>or distribute it to anyone else. If you have received this e-mail in
error,
>please call [+44 (0)23 92228424] to report the error and then delete
this
>message from your system.
>
>
>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: VM Ware
>With VMware you can run multiple operating systems on a single machine.
>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
>at the same time. Free trial click
here:http://www.vmware.com/wl/offer/358/0
>_______________________________________________
>Expectperl-discuss mailing list
>Exp...@li...
>https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
> =20
>



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click
here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
Expectperl-discuss mailing list
Exp...@li...
https://lists.sourceforge.net/lists/listinfo/expectperl-discuss

Re: [Expectperl-discuss] Problem with GLOB Reference in Expect.pm

[Sayre S. <sa...@qu...>]

I have a similar problem **whenever** my program exits:

(in cleanup) Not a GLOB reference at 
/usr/lib/perl5/site_perl/5.8.0/Expect.pm line 1572.

I am also interested in a way to stop that from happening.

Thank you.


Sayre Swarztrauber
Quadlogic
New York


Kemp, Donald wrote:

>Hi,
>I am intermittently getting the following message  ....
>	Not a GLOB reference at
>/usr/local/lib/perl5/site_perl/5.6.1/Expect.pm line 256.
>This happens on a Solaris 8 system running Perl 5.6.1 and Expect 1.15. The
>problem is occurring on a production system that has multiple fast
>processors and a very large amount of memory. It seems to be occurring more
>often as the number of users on the system that are using my code increases.
>I do not see the problem on my "slower" test system running the same level
>of software. Does anyone have any idea what may be triggering this error?
>What can I do to try an isolate what the cause of the problem may be??
>
>Best Regards,
>Donald.E.S.Kemp
>AT&T
>Network Management Solutions,
>Building 6000, Langstone Technology Park,
>Langstone Road,  Havant, Hampshire,
>United Kingdom,
>PO9 1SA
>Phone:  +44(0)23 9222 8424
>email:  dk...@em...
>
>This message and any attachments to it contain confidential business
>information exclusively intended for the recipients. Please do not forward
>or distribute it to anyone else. If you have received this e-mail in error,
>please call [+44 (0)23 92228424] to report the error and then delete this
>message from your system.
>
>
>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: VM Ware
>With VMware you can run multiple operating systems on a single machine.
>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
>at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
>_______________________________________________
>Expectperl-discuss mailing list
>Exp...@li...
>https://lists.sourceforge.net/lists/listinfo/expectperl-discuss
>  
>