On Wed, 02 Apr 2008 19:57:31 -0600, Paul Lemelle <[EMAIL PROTECTED]> wrote:
> Jorgen,
>
> Thanks for your reply.
>
> The ssh function is just a small part of what I would like to
> accomplish. And yes, chk is undefined, I was trying to figure out why
> control was not being returned from the sshc
Jorgen,
Thanks for your reply.
The ssh function is just a small part of what I would like to
accomplish. And yes, chk is undefined, I was trying to figure out why
control was not being returned from the sshcon funciton.
I looked for pexpect doucment on http://www.noah.org/wiki/Pexpect, but
th
On Fri, 28 Mar 2008 08:12:36 -0700 (PDT), Paul Lemelle <[EMAIL PROTECTED]>
wrote:
> I am trying separate a script that users pexpect into
> various functions within the same expect session. The
> problem is that the function does not return control
> back Main.
I do not understand what that sent
Hi,
While I continue to look at the problem, I thought I would post more
details. In a sense, this is more of a UNIX issue.
I have a python script that uses pexpect to spawn a child process (p1).
The python script then goes ahead and does a "tail --pid=p1". Assuming
that I do close(wait=0), P1 c
[EMAIL PROTECTED] wrote:
> Currently, I am spawning a new thread
> that just does pexpect_spawned_child.close(wait=1). It seems to work in
> some cases but the child process is occassionally getting deadlocked.
I think your only cross-platform option will be to fix the child
process to die nicely
Hi,
I actually replied saying that the process dies when close(wait=0) is
done (the reply doesn't show up yet). It is not correct. The process
actually runs but ends up in zombie status (defunct).
Raghu.
--
http://mail.python.org/mailman/listinfo/python-list
> "[EMAIL PROTECTED]" == [EMAIL PROTECTED] com <[EMAIL PROTECTED]> writes:
> Hi,
> I am using pexpect to spawn an interactive program and wait for
> particular string in its output. It works fine but once I get this
> required information, I really don't care about the child process
> anymore.
