Re: output error messages
- From: Uwe Klein <uwe_klein_habertwedt@xxxxxxxxxxx>
- Date: Tue, 08 Jun 2010 18:30:07 +0200
He needs to at least expect EOF to have the
shell command or any other at that ) its course.
as nothing is [expect]ed the spawned process is blocked.
spawn itself will only report errors in creating the
spawned process, i.e.
spawn telnex $host $port
expect1.3> spawn telnex ben smtp
spawn telnex ben smtp
couldn't execute "telnex": no such file or directory
while executing
"spawn telnex ben smtp"
expect1.4>
will produce a usefull error ( prob. telnex not found or similar )
OK:
expect1.1> spawn sh "mv a b"
spawn sh mv a b
28289
expect1.2> expect EOF
mv a b: mv a b: No such file or directory
expect1.3> wait
28289 exp4 0 127
expect1.5>
uwe
.
- Follow-Ups:
- Re: output error messages
- From: Dave
- Re: output error messages
- From: Dave
- Re: output error messages
- References:
- output error messages
- From: Dave
- Re: output error messages
- From: Alexandre Ferrieux
- Re: output error messages
- From: Dave
- Re: output error messages
- From: Dave
- Re: output error messages
- From: Alexandre Ferrieux
- output error messages
- Prev by Date: Re: output error messages
- Next by Date: Re: BLT
- Previous by thread: Re: output error messages
- Next by thread: Re: output error messages
- Index(es):