Hi Edi,
thanks for the feedback. The key sequences are too generic (as they work with all kinds of connections) and they also (by default) simulate keyboard input. For rebex based connections we could implement something like "triggers". The idea is that you configure some sort of pattern you look out for and when the pattern appears, a key sequence is triggered immediately. Would that be helpful?
Regards,
Stefan
Hi Stefan
Yes, it will be very helpful rather than change the timeout value. Hopefully, this feature can be implemented soon.
Edi
I was also looking for this feature, you put the timers for worst case scenario and it causes a delay in most of the times.
Fatih
Edi
Hi,
On the Key Sequence feature, I don't see any option to waiting for some char/pattern available yet. Actually when the network connection to the host server was poor then the time to wait was need a little bit longer than usual and the key sequence not working as expected. If I increase the timeout then when the network in the good condition then it makes me waiting too long for the Key Sequence running. So the idea is waiting based on some char/pattern before it runs the Key Sequence. Here are the illustrations.
[username@localhost ~]$ su -
Password:
[root@localhost ~]# su - username
[username@labs ~]$
WAITFOR=$
su -
WAITFOR=assword
SOME WORD
WAITFOR=#
su - username
Thanks