SSH macros on unsiccessful connections?

Hi,
I will verify if we can detect that the connection fails and cancel the macro. The slowness, I'm not sure why but I will verify at the same time.

I would like to bump this..

The slowness is because we have to wait to process the message. For the cancel issue, we have a bug entered. The problem is to detect that the connection fails. It's not trivial unfortunately.

ok,

re the slowness, could you have a look at putty, there the macro (entered here: http://screencast.com/t/se2dneFpK) ist sent and executed immediately.

re the detection of failed connections, you already detect this: http://screencast.com/t/gtX3AoET1H

The problem is that there is no link between the macro execution and the login. It handled at two different location and the terminal can't send a notification to the macro engine.

with the new version 10.0 the problem still exists. and seriously, it's not just annoying, it's dangerous. when you execute a macro blindly after an unsuccessful connection it just types it in the next window that is on top - this is plainly irresponsible for such a powerful tool as RDM!

Hi,
we have implemented a batch execution macro that does all the work without sending the actual keystroke. However it seems that we haven't back ported that to your scenario. I will assign this to one of our dev and we will take care of this.

thanks, how will I see, that it works now?

You will see a change history entry talking about SSH scripting macro

..while you're at it, with SSH connections, the macro seems to swallow the first letters.

screen -xR {ENTER}

for instance, doesn't work. I had similar problems in older versions, it helped sometimes to put a {ENTER} in front of it, but even this isn't working now.

Hi,
André has made the change and this will be in the next beta release.

Regards

is there an ETA?

I think it's already in the latest beta

ah, ok, I don't like working with betas in a production environment, so, when will this feature get stable?

We expect to release the version 10.1 by the end of the month.

Regards

any news here?

The final version is expected in the middle of next week. This is my fault since I'm currently on vacation and I will be back Monday.

vacations are never a fault..