Thursday, March 21, 2019

new version 2.5.1 released

Changelog
  • Bug fix: selecting a KiTTY binary containing the version string now possible
  • Bug fix: no error message was shown when opening a session and the PuTTY/KiTTY binary was not found

7 comments:

  1. Hi, Great product. However when you use the Login Cmd option it appends ;bash --login to it so that you end up with a shell. However that wont work on some systems like AIX where there is no bash installed. Is there an option (or could there be one in a future release) that allows us to set the shell command to run?
    Thanks

    ReplyDelete
    Replies
    1. Hi, thanks for your feedback. I'll add an option so that it can be customized.

      Delete
    2. You could set a hash "#" at the end of your login command for your AIX systems to comment out the bash command, so it won't be executed. This way you can also run a different shell (e.g. ";/usr/bin/ksh --login #"). Does this work for you?

      Delete
  2. Yes that works thanks. By the way with AIX you have to use the enhanced ksh (ksh93) to get it to run the login (ksh93 --login).
    I was hoping to be able to automatically run some post login commands in the same shell - do you have an option for that?

    ReplyDelete
    Replies
    1. Thanks, why do you need to run commands in the same shell? Can you give me an example of what you are trying to do?

      Delete
  3. Hi, yes I'm trying to customize things in the shell that I use for all connections like setting aliases or other shell settings. For example alias ll='ls -al' ; set -o emacs , that type of thing. Is that something your script functions could do? i.e. run a script that resides on the local PC after login?

    ReplyDelete
    Replies
    1. Hi, yes, you could create a script with your aliases and so on, add a newline at the end, assign the script to a button and click on the button after you log in. I think there is no other way to do this without changing the remote system

      Delete