Here is a snippet (the tar actually executes in the middle of the sequence):
<telnet server="${server.name}" timeout="60">
<read>ogin: </read>
<write echo="false" string="${accutrack.user}"></write>
<read>assword:</read>
<write echo="false" string="${accutrack.pass}"></write>
<read string=">"></read>
<write string="cd ${accutrack.home}/${accutrack.applications}"/>
<read timeout="300" string=">"></read>
<write string="tar -xvf accutrack.war"/>
<read timeout="600" string=">"></read>
<write string="test.sh"/>
<read timeout="300" string=">"></read>
...
</telnet>
When I nohup the tar through ant and tail nohup.out, I don't see the results
of the extraction. However, if I telnet into the box and tail nohup.out, I
see the results. Why would that be?
Julia
-----Original Message-----
From: Steve Loughran [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 11, 2002 3:48 PM
To: Ant Users List
Subject: Re: Telnet and tar -xvf
----- Original Message -----
From: "Vaughn, Julia" <[EMAIL PROTECTED]>
To: "'Ant Users List'" <[EMAIL PROTECTED]>
Sent: Wednesday, September 11, 2002 11:32 AM
Subject: RE: Telnet and tar -xvf
> I have tried that as well as unzip -of. I believe it's a bug in the telnet
> task. I am responsible for automating ~20 java apps (build and deployment)
> and I see similar things with every build file. If I nohup the tar and
sleep
> 60, then it works fine. Has anyone else experienced this?
I usually remote deploy by using jar -xvf, never hit problems. But I do set
the prompt at the far end.
Are you making sure that you wait for a response after making the tar call?
the nohup hints implies you need to keep it running after the task
exits...if there isnt a <read> at the end the task exits without waiting for
tar to finish.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
