I simplified the mechanism to just an Ant script that calls a remote script that performs a "sleep" and I tested it up to 1 hour 1 second (much longer than my script runs). I was unable to reproduce the behavior, so it must be something to do with the remote script that's being invoked. However, the script does indeed exit as demonstrated by logs, and it exits when called from the command line. What could a script be doing that would break ssh in this way?
> -----Original Message----- > From: Anderson, Rob (Global Trade) [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 02, 2006 11:47 AM > To: Ant Users List > Subject: RE: sshexec hangs after remote script exits > > Did you mean to say ...ssh never detects that the script exits... ? > > What OS are you executing the script on? Can you send the relevant > portion of your build.xml please? What version of ssh server are you > running? Also, try to see if you can get a script to return that takes > like 2 min, 3 min, etc. Write a little shell script that just sleeps and > see what happens, adjusting the sleep time to find the threshold that > breaks sshexec. > > -Rob Anderson > > > -----Original Message----- > > From: Brown, Carlton [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, May 02, 2006 8:35 AM > > To: Ant Users List > > Subject: sshexec hangs after remote script exits > > > > I've got an sshexec command that calls a remote script. The remote > > script can take something like 5-15 minutes to run. Trouble is, the > > sshexec never detects that the script exists. What have I done wrong? > > > > > > > > Carlton Brown <http://web.snt.bst.bls.com/db/emp/bwwhbhp> > > > > BellSouth Science & Technology > > > > [EMAIL PROTECTED] > > > > 404-986-0894 > > > > > > > > > > ***** > > > > The information transmitted is intended only for the person > > or entity to which it is addressed and may contain > > confidential, proprietary, and/or privileged material. Any > > review, retransmission, dissemination or other use of, or > > taking of any action in reliance upon this information by > > persons or entities other than the intended recipient is > > prohibited. If you received this in error, please contact the > > sender and delete the material from all computers. 118 > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
