cancel shouldn't mean cancel the session for a log question

Hello,

The log feature on the entry was originally envisioned as being part of an administrator's auditing tools. Meaning, if an administrator configured an entry to require logging, a user using this entry should have the logging enabled to start with. I'm not sure if this makes sense anymore as we have better tools for this like session recording which is much more reliable, especially when going through our Gateway. Additionally, it's possible to configure the entry to not prompt for a choice, meaning the log will always be written.

That said, I will open a ticket so we can improve this.

Regards,

Understand, I manage over 400 switches logging has allways been a part my work to record when need, to overright at times and sometimes I just don't care. I understand your point above, but hopefully this tool can be flexible to meet this need from a user focusing on ssh connections. Recording all the time isn't the solution. I have used tool for 20 years and RDM meets 2/3 of the request. The Cancel IS not the important part, but i personally would think that if one connects to a system and the question is for logging, the session should drop.

Just to confirm your sentence here:

The Cancel IS not the important part, but i personally would think that if one connects to a system and the question is for logging, the session should drop.

Do you mean that the session should not drop? That's what I understood from your original message. You want to be able to proceed without logging as sometimes making this choice is not relevant to you. I want to make sure the changes we make will actually improve things for you.

Regards,

The session SHOULD CONTINUE with no logging.

Here is the other change, when I enter one line i still get this screen. As a single command it should be entered in the session since there is not return line at the end, multiple line have a return at the end to enter the command which is the purpose of this windown.