Brown, Carlton wrote:
I've got an sshexec task that never exits, and I need to solicit some
opinions on the problem. The reasons behind it are well-known; if an
ssh command starts a long-running in the background, then ssh doesn't
know when it should exit.
From the purist standpoint, this is expected behavior. In practice, I
need a workaround. If I'm starting an application server, for example,
I have succeeded if my ssh command completes and returns a successful
error code, regardless of whatever may be backgrounded.
The Ant manual entry on sshexec does not hint at any solutions to this
behavior. Does anyone have any suggestions as to workarounds or
resolutions?
In order of complexity
1. nohup jboss &
2. use Cargo for starting your app server
3. use smartfrog for managing your entire deployment.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
