Stefan, I see your point, and I agree. Can there be some flag that specifies
interactivity? Or non-interactivity? Perhaps the default behavior should be
to assume interactivity unless the "interactive" flag is set to false. I'm
thinking of something like:
<!-- Non-interactive -->
<ssh host="myhost" username="myname" password="mypass"
interactive="false"
command="cd /usr/local/bin ; rm -rf product ; tar zxf
product.tar.gz"
/>
<!-- Interactive -->
<ssh host="myhost" username="myname" password="mypass">
<read>bash-2.03$ </read>
<write>cd /usr/local/bin</write>
<read>bash-2.03$ </read>
<write>rm -rf product</write>
<read>bash-2.03$ </read>
<write>tar zxf product.tar.gz</write>
</ssh>
I think this is a fair compromise.
-Rob Anderson
-----Original Message-----
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 20, 2003 11:25 PM
To: [EMAIL PROTECTED]
Subject: Re: SSH Tasks
On Thu, 20 Feb 2003, Rob H. Anderson <[EMAIL PROTECTED]>
wrote:
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
>
> On Thu, 20 Feb 2003, Rob H. Anderson <[EMAIL PROTECTED]>
> wrote:
>
>> The ssh task is different from the telnet task in that is not meant
>> to handle an interactive shell session, beyond the password
>> authentication.
>
> Why not?
>
> RA> Because there is no need to interact with the shell.
No need for you, but I have to disagree with this as a general
assumption.
People may prefer scripting an interactive session ovber writing a
shell script on the remote server. You may even be able to run an
interactive program on the remote site and script the answers into
your build file.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
