External applications optional client path options

Advertisement

alerosmile
Donor
Joined:
Posts:
5

External applications optional client path options

For some sessions, I need to pass a private key file via command line to the external application (... -k !K). If the session does not have a private key configured, the application starts with the -k option alone. That application fails to start because the expected key file is not present on the command line. Is there a way to configure the terminal client path depending on whether the session has a key or not?

Thanks.

Reply with quote

Advertisement

Advertisement

You can post new topics in this forum