inconsistent exitStatus codes for JschSshClient

[Michael Neale]

Anyone else seeing exit codes of -1 from time to time even when a script was run successfully? Its driving me up the wall. 

I have looked through a reasonably current version of the code, I can't see anything obvious, other than the Jsch recommendation that the channel is closed before the exit code is read (?). FYI runnign the script by hand (command line) doesn't return -1 in these particular cases, but it all ends up working just the same. 

--
Michael D Neale
home: www.michaelneale.net
blog: michaelneale.blogspot.com

[Adrian Cole]

Hmm.. not quite sure, but we can fix the channel close issue and see what happens.

On a side-note, I think we should do some slight refactoring on the way scripts are invoked to take advantage of clouds.  For example, on EC2 images that support userData scripts, using those would be advantageous.  Also, Rackspace file injection is another win.  Switching "off" using ssh where possible allows us to leverage the native features of the API and also not unnecessarily require SSH access to hosts.  Moreover, once this is abstracted out, we can plug in other means to bootstrap and such, allowing hooks to let the user do things like retrying.

-Adrian

--
You received this message because you are subscribed to the Google Groups "jclouds-dev" group.
To post to this group, send email to jclou...@googlegroups.com.
To unsubscribe from this group, send email to jclouds-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jclouds-dev?hl=en.

[Michael Neale]

I think there are limits to the size of those (at least in rackspace) which may make it a bit of a challenge... without having some agent "pull" something which is a whole other area... 

yeah - nevertheless, I am still curios about jsch - I quite enjoy the jclouds nice api on top (I have to say that jclouds api has "taste" !).