.
ctys-CLI - Command Line Interface
ctys -t CLI -a action[=<suboptions>] ... ctys -T CLI -a action[=<suboptions>] ... ctys -T ALL -a action[=<suboptions>] ...
The CLI-plugin starts a remote shell from within a local shell. No specific default desktop functionality such as XTerm is supported, just a pure CLI access is performed. The handling of desktop windows such as XTerm or GTerm is supported by the X11-Plugin. The default and standard usage of the X11 displayforwarding by activation of the '-X' option of the underlying OpenSSH provides the usage of the CLI-plugin as a scripting and automation starter for any X11 application. This provides particularly any application with a proven on-demand encryption for the network interconnection by seamless integration into the ctys user interface. An Xterm, gnome-terminal or any arbitray X11 tool could be started from within a CLI sub-option "CMD". Chained logins by gateways with Overall-Display-Forwarding is supported by OpenSSH, thus by ctys too.
When executing CLI almost the same functionality as for an ordinary SSH session is supported. The main advance of using ctys instead of an ordinary ssh-call is the seamless integration into the ctys environment. Resulting from this feature instead of an IP address the <machine-address> could be used. Thus the administration of address-to-target-mapping could be completely delegated to ctys and will be utilized by internal usage of the full scope of ctys-vhost. E.g. the LABELS defined within ctys could be used to open a remote shell to any "labeled" instance such as a VM or PM. Therefore internal CLI type CONSOLES only use the CLI plugin.
Another quite important aspect is the persistancy of any symbolic address entity. The complete set of addresses defined by symbolic elements such as labels is mapped to actual runtime addresses when required. Thus the automation of post-attachement of an X11 application could be easily stored into a script without additional effort for determination of the dynamic runtime identifier such as arbitrary display identifiers.
Another option might be the usage of UUIDs or MAC-Addresses for persistent definition of the handling of commands on frequently changing and reinstalled systems with reassigned IP-Addresses and DNS names. This is provided for any system by dynamic mapping.
The second important feature of CLI is the facility to start native remote commands as shell calls within any managed PM or VM instance. Therefore CLI is the working horse for native execution of GUI-less ctys-tasks. Similar to the call of a system command, any internal ctys library and plugins function could be called remotely by CLI sub-option "CMD".
The default shell used on the target instance is bash, which could be altered interactive by the sub-option "SHELL|S", or persistently by the variable CLI_SHELL_CMD_DEFAULT.
It should be mentioned and explained here that there are two quite similar suboptions, which on the first view seems to be redundant, which is actually not the case. The main difference betweend the CMD and SHELL suboptions is the behaviour. Whereas the SHELL just overlays the standard shell within a Session, the CMD suboption executes a command from within the executed shell - either the standard shell, or a pre-set custom shell.
Additional information containing use-cases with application examples is available from
ctys-uc-CLI .
CREATE=[<machine-address>]
[REUSE|CONNECT|RECONNECT|RESUME]
[CONSOLE:<>]
[(CALLOPTS|C):<callopts>]
[CD:<working-directory>][,]
[(XOPTS|X):<xopts>]
[(SHELL|S):<shell>]
[(STUBMODE|STUB)[:on]][,]
[(CMD):<cmd>]
| Arno-Can Uestuensoez | <https://arnocan.wordpress.com/> |
| <https://unifiedsessionsmanager.sourceforge.io/> | |
| <https://github.com/unifiedsessionsmanager> | |
|
Copyright (C) 2008, 2009, 2010, 2011, 2020 Ingenieurbuero Arno-Can Uestuensoez
This is software and documentation from BASE package,
For additional information refer to enclosed Releasenotes and License files.
