I'm sure I've used autoexpect on SCO systems in the past, but maybe not..

I tried both versions from Skunkware. "autoexpect" by itself should,
for example, just show a shell prompt and continue from there. Instead,
everything seems to be buffered - which I expect autexpect to take care
of by itself.

I've tried this on two systems now, same results. If I start autoexpect
somewhere else, I can ssh on into the SCO and everything is fine, but
not if I ssh in and start it there..

I'm baffled..


--
Tony Lawrence
Unix/Linux/Mac OS X resources: http://aplawrence.com

Tony Lawrence typed (on Mon, Apr 18, 2005 at 11:17:18AM -0400):
| I'm sure I've used autoexpect on SCO systems in the past, but maybe not..
|
| I tried both versions from Skunkware. "autoexpect" by itself should,
| for example, just show a shell prompt and continue from there. Instead,
| everything seems to be buffered - which I expect autexpect to take care
| of by itself.
|
| I've tried this on two systems now, same results. If I start autoexpect
| somewhere else, I can ssh on into the SCO and everything is fine, but
| not if I ssh in and start it there..
|
| I'm baffled..


I'm not sure what you mean by "everything is buffered". I'd not run
autoexpect in years, but I just tried it on 5.0.6 and on 5.0.7, and saw no
difference in what happened, or in the resultant capture scripts.


--
JP

Jean-Pierre Radley wrote:
> Tony Lawrence typed (on Mon, Apr 18, 2005 at 11:17:18AM -0400):
> | I'm sure I've used autoexpect on SCO systems in the past, but maybe not..
> |
> | I tried both versions from Skunkware. "autoexpect" by itself should,
> | for example, just show a shell prompt and continue from there. Instead,
> | everything seems to be buffered - which I expect autexpect to take care
> | of by itself.
> |
> | I've tried this on two systems now, same results. If I start autoexpect
> | somewhere else, I can ssh on into the SCO and everything is fine, but
> | not if I ssh in and start it there..
> |
> | I'm baffled..
>
>
> I'm not sure what you mean by "everything is buffered". I'd not run
> autoexpect in years, but I just tried it on 5.0.6 and on 5.0.7, and saw no
> difference in what happened, or in the resultant capture scripts.
>
>

Boy, that is weird. I tried this on two systems, with two versions from
Skunkware - and neither work. What I mean by buffered is that nothing
is appearing on the screen - no shell prompt, no anything. If I type
commands, etc. they work, but don't appear on the screen until I type
exit, and then the script.exp (after the usual preamble) is just

set timeout -1
spawn $env(SHELL)
match_max 100000
expect eof

If I run that, I get the somewhat similar behavior - one shell prompt,
then no prompts, no apparent response to commands:

$ ./script.exp
spawn /bin/sh
$ ls


ls > /tmp/that

(ctrl-c no response - yes intr is set to ctrl-c not del)

(CTRL-\ here)


$ cat /tmp/that
cat: cannot open /tmp/that: No such file or directory (error 2)

$

Obviously some unexpected buffering going on but I do not know why..


--
Tony Lawrence
Unix/Linux/Mac OS X resources: http://aplawrence.com

Tony Lawrence wrote:

> I've tried this on two systems now, same results. If I start autoexpect
> somewhere else, I can ssh on into the SCO and everything is fine, but
> not if I ssh in and start it there..

Complete and utter shot in the dark, but could it have something to do
with SSH's tty allocation? I know it's bitten me in the past, but can't
remember the details. What happens if you (*shudder*) telnet or modem
into the machine in question rather than than ssh?

JS

John Schmidt wrote:
> Tony Lawrence wrote:
>
>> I've tried this on two systems now, same results. If I start
>> autoexpect somewhere else, I can ssh on into the SCO and everything is
>> fine, but not if I ssh in and start it there..
>
>
> Complete and utter shot in the dark, but could it have something to do
> with SSH's tty allocation? I know it's bitten me in the past, but can't
> remember the details. What happens if you (*shudder*) telnet or modem
> into the machine in question rather than than ssh?
>
> JS

Hmm.. I can't do that, but I could get someone there to try autoexpect
on the console.. not sure what I'd do if that does work though..

--
Tony Lawrence
Unix/Linux/Mac OS X resources: http://aplawrence.com

Tony Lawrence enscribed:
| I'm sure I've used autoexpect on SCO systems in the past, but maybe not..
|
| I tried both versions from Skunkware. "autoexpect" by itself should,
| for example, just show a shell prompt and continue from there. Instead,
| everything seems to be buffered - which I expect autexpect to take care
| of by itself.
|
| I've tried this on two systems now, same results. If I start autoexpect
| somewhere else, I can ssh on into the SCO and everything is fine, but
| not if I ssh in and start it there..

I've some unexplained problems with expect and the lame 5.0.7 ssh but
not like this.

Could you be running afoul of the tcl/expect in /usr/gnu/bin?
--
================================================== ========================
Tom Parsons tom@tegan.com
================================================== ========================

Tom Parsons wrote:
> Tony Lawrence enscribed:
> | I'm sure I've used autoexpect on SCO systems in the past, but maybe not..
> |
> | I tried both versions from Skunkware. "autoexpect" by itself should,
> | for example, just show a shell prompt and continue from there. Instead,
> | everything seems to be buffered - which I expect autexpect to take care
> | of by itself.
> |
> | I've tried this on two systems now, same results. If I start autoexpect
> | somewhere else, I can ssh on into the SCO and everything is fine, but
> | not if I ssh in and start it there..
>
> I've some unexplained problems with expect and the lame 5.0.7 ssh but
> not like this.
>
> Could you be running afoul of the tcl/expect in /usr/gnu/bin?

Hmm.. no, that's not installed.. maybe that's the problem.. I just
installed expect, nothing else. Tcl is /bin/tcl.. so does it want the
Gnu tcl?





--
Tony Lawrence
Unix/Linux/Mac OS X resources: http://aplawrence.com

Tony Lawrence enscribed:
| Tom Parsons wrote:
| > Tony Lawrence enscribed:
| > | I'm sure I've used autoexpect on SCO systems in the past, but maybe not..
| > |
| > | I tried both versions from Skunkware. "autoexpect" by itself should,
| > | for example, just show a shell prompt and continue from there. Instead,
| > | everything seems to be buffered - which I expect autexpect to take care
| > | of by itself.
| > |
| > | I've tried this on two systems now, same results. If I start autoexpect
| > | somewhere else, I can ssh on into the SCO and everything is fine, but
| > | not if I ssh in and start it there..
| >
| > I've some unexplained problems with expect and the lame 5.0.7 ssh but
| > not like this.
| >
| > Could you be running afoul of the tcl/expect in /usr/gnu/bin?
|
| Hmm.. no, that's not installed.. maybe that's the problem.. I just
| installed expect, nothing else. Tcl is /bin/tcl.. so does it want the
| Gnu tcl?

I've usually had Expect complain if it couldn't find tcl. I'm currently
using expect-5.30, tcl-8.1.1 and tclX-8.1.1 on 5.0.7

On a FreeBSD box (where it is easier to find), expect-5.38.0_3 lists
tcl-8.4.6,1 and tk-8.4.6,1 as dependencies

--
================================================== ========================
Tom Parsons tom@tegan.com
================================================== ========================

Tom Parsons wrote:
> Tony Lawrence enscribed:
> | Tom Parsons wrote:
> | > Tony Lawrence enscribed:
> | > | I'm sure I've used autoexpect on SCO systems in the past, but maybe not..
> | > |
> | > | I tried both versions from Skunkware. "autoexpect" by itself should,
> | > | for example, just show a shell prompt and continue from there. Instead,
> | > | everything seems to be buffered - which I expect autexpect to take care
> | > | of by itself.
> | > |
> | > | I've tried this on two systems now, same results. If I start autoexpect
> | > | somewhere else, I can ssh on into the SCO and everything is fine, but
> | > | not if I ssh in and start it there..
> | >
> | > I've some unexplained problems with expect and the lame 5.0.7 ssh but
> | > not like this.
> | >
> | > Could you be running afoul of the tcl/expect in /usr/gnu/bin?
> |
> | Hmm.. no, that's not installed.. maybe that's the problem.. I just
> | installed expect, nothing else. Tcl is /bin/tcl.. so does it want the
> | Gnu tcl?
>
> I've usually had Expect complain if it couldn't find tcl. I'm currently
> using expect-5.30, tcl-8.1.1 and tclX-8.1.1 on 5.0.7
>
> On a FreeBSD box (where it is easier to find), expect-5.38.0_3 lists
> tcl-8.4.6,1 and tk-8.4.6,1 as dependencies
>

Well, now I'm totally confused. I found tcl-8.1.1-VOLS.tar on
skunkware, but that doesn't include tcl - just tclsh..

Alligators, draining the swamp.. I don't want to have to care about Tcl :-)

--
Tony Lawrence
Unix/Linux/Mac OS X resources: http://aplawrence.com

Tony Lawrence enscribed:
| Tom Parsons wrote:
| > Tony Lawrence enscribed:
| > | Tom Parsons wrote:
| > | > Tony Lawrence enscribed:
| > | > | I'm sure I've used autoexpect on SCO systems in the past, but maybe not..
| > | > |
| > | > | I tried both versions from Skunkware. "autoexpect" by itself should,
| > | > | for example, just show a shell prompt and continue from there. Instead,
| > | > | everything seems to be buffered - which I expect autexpect to take care
| > | > | of by itself.
| > | > |
| > | > | I've tried this on two systems now, same results. If I start autoexpect
| > | > | somewhere else, I can ssh on into the SCO and everything is fine, but
| > | > | not if I ssh in and start it there..
| > | >
| > | > I've some unexplained problems with expect and the lame 5.0.7 ssh but
| > | > not like this.
| > | >
| > | > Could you be running afoul of the tcl/expect in /usr/gnu/bin?
| > |
| > | Hmm.. no, that's not installed.. maybe that's the problem.. I just
| > | installed expect, nothing else. Tcl is /bin/tcl.. so does it want the
| > | Gnu tcl?
| >
| > I've usually had Expect complain if it couldn't find tcl. I'm currently
| > using expect-5.30, tcl-8.1.1 and tclX-8.1.1 on 5.0.7
| >
| > On a FreeBSD box (where it is easier to find), expect-5.38.0_3 lists
| > tcl-8.4.6,1 and tk-8.4.6,1 as dependencies
| >
|
| Well, now I'm totally confused. I found tcl-8.1.1-VOLS.tar on
| skunkware, but that doesn't include tcl - just tclsh..
|
| Alligators, draining the swamp.. I don't want to have to care about Tcl :-)

For reasons unexplained, tcl is in tclX-8.1.1 on Skunkware
--
================================================== ========================
Tom Parsons tom@tegan.com
================================================== ========================