CTEL(1p)

πŸ“¦
version 4.18 Β· 4 versions
, in ubuntu resolute, ubuntu stonking

okay bestie, buckle up πŸŽ€ this is ctel(1p), living in the User Contributed Perl Documentation section, and it's lowkey a whole personality. let's get into it. ✨

🌸 NAME 🌸

ctel β€” Cluster administration tool. that's it, that's the name, iconic. πŸ’…


πŸ‘‘ VERSION πŸ‘‘

This documentation is for version: 4.18.


✨ SYNOPSIS ✨

ctel [-K <seconds>] [-q] [-c '<filename>'] [-x <cols>] [-C '<filename>']
[--debug [[...] || <INTEGER>]] [-d] [-e '<[user@]<host>[:port]>']
[--fillscreen] [-f '<font>'] [-h] [-L '[tag]'] [-H] [-p <port>] [-Q] [-y
<rows>] [-s] [-r '<filename>'] [-t '<STRING>'] [-g] [-T '<title>'] [-u]
[-?] [-A] [-v]

Also see the individual man pages for each of these utilities, bestie, they each do their own thing:

  • ccon β€” use 'console' as the communication method
  • crsh β€” use 'rsh' as the communication method
  • csftp β€” use 'sftp' as the communication method
  • cssh β€” use 'ssh' as the communication method

🌈 DESCRIPTION 🌈

So like, this command opens an administration console and an xterm to all the hosts you specify. Any text you type into the administration console gets replicated to all the windows. and yes, you can also type directly into any of the windows, multi-tasking queen. πŸ’…

It's made for (but not limited to!!) cluster administration, where the same config or commands have to run on every single node in the cluster. Running them all at once with this tool keeps every node in sync. periodt.

Connections get opened using telnet, which has to be correctly installed and configured. no telnet, no party. πŸ™ˆ

Extra caution should be taken when editing files, because lines may not necessarily be in the same order. assuming line 5 is the same across all servers and just editing that?? dangerous. it's way better to search for the specific line you wanna change and double-check that every terminal is exactly as expected before committing anything. fr fr.

πŸ¦‹ Further Notes πŸ¦‹

Please also see "KNOWN BUGS".

  • The dotted line on any sub-menu is a tear-off, i.e. click on it and the sub-menu gets turned into its own window. cute, right?
  • Unchecking a hostname on the Hosts sub-menu will unplug that host from the cluster control window, so any text typed into the console is not sent to that host. Re-selecting it plugs it right back in. 🫢
  • If your window manager menu bars are obscured by terminal windows, go see the "screen_reserve_XXXXX" options in the $HOME/.clusterssh/config file (see "FILES").
  • If the terminals overlap too much, go see the "terminal_reserve_XXXXX" options in the $HOME/.clusterssh/config file (see "FILES").
  • When using ClusterSSH on a large number of systems to connect to a single system using an SSH utility (like when you issue a command to copy a file using scp from the remote computers to a single host), and when those connections require authentication (i.e. you're gonna authenticate with a password), the sshd daemon at that location may refuse connections once the number "MaxStartups" limit in sshd_config is exceeded. (If this value is not set, it defaults to 10.) This is expected behavior; sshd uses this mechanism to prevent DoS attacks from unauthenticated sources. Please tune sshd_config and reload the SSH daemon, or consider using the ~/.ssh/authorized_keys mechanism for authentication if you hit this problem. not a bug, just sshd being sshd. πŸ’€
  • If client windows fail to open, try running:
"ctel -e {single host name}"

This will test the mechanisms used to open windows to hosts. This could be due to either the -xrm terminal option which enables AllowSendEvents (some terminals do not require this option, other terminals have another method for enabling it β€” see your terminal documentation) or the configuration of telnet.


πŸ’… OPTIONS πŸ’…

Some of these options may also be defined within the configuration file. Default options are shown as appropriate.

  • --autoclose <seconds>, -K <seconds> β€” number of seconds to wait before closing finished terminal windows.
  • --autoquit, -q β€” toggle automatically quitting after the last client window has closed (overriding the config file).
  • --cluster-file '<filename>', -c '<filename>' β€” use the supplied file as an additional cluster file (see also "FILES").
  • --cols <cols>, -x <cols> β€” number of columns
  • --config-file '<filename>', -C '<filename>' β€” use the supplied file as an additional configuration file (see also "FILES").
  • --debug [[...] || <INTEGER>] β€” enable debugging. either a level can be provided, or the option can be repeated multiple times. maximum level is 9.
  • --dump-config, -d β€” dump the current configuration in the same format used by the $HOME/.clusterssh/config file.
  • --evaluate '<[user@]<host>[:port]>', -e '<[user@]<host>[:port]>' β€” display and evaluate the terminal and connection arguments to display any potential errors. the <hostname> is required to aid the evaluation.
  • --fillscreen β€” resize terminal windows to fill the whole available screen
  • --font '<font>', -f '<font>' β€” specify the font to use in the terminal windows. use standard X font notation such as "5x8".
  • --help, -h β€” show basic help text and exit
  • --list '[tag]', -L '[tag]' β€” list available cluster tags. tag is optional. if a tag is provided, then hosts for that tag are listed. NOTE: the format of output changes when using "--quiet" or "-Q".
  • --man, -H β€” show full help text (the man page) and exit
  • --port <port>, -p <port> β€” specify an alternate port for connections.
  • --quiet, -Q β€” do not output extra text when using some options
  • --rows <rows>, -y <rows> β€” number of rows
  • --show-history, -s β€” show history within the console window.
  • --tag-file '<filename>', -r '<filename>' β€” use the supplied file as an additional tag file (see also "FILES")
  • --term-args '<STRING>', -t '<STRING>' β€” specify arguments to be passed to the terminals being used.
  • --tile, -g β€” toggle window tiling (overriding the config file).
  • --title '<title>', -T '<title>' β€” specify the initial part of the title used in the console and client windows.
  • --unique-servers, -u β€” toggle connecting to each host only once when a hostname has been specified multiple times.
  • --usage, -? β€” show synopsis and exit
  • --use-all-a-records, -A β€” if a hostname resolves to multiple IP addresses, toggle whether or not to connect to all of them, or just the first one (see also config file entry).
  • --version, -v β€” show version information and exit

πŸ“ ARGUMENTS πŸ“

The following arguments are supported:

  • [user@]<hostname>[:port] ... β€” open an xterm to the given hostname and connect to the administration console. the optional port number can be used if the server isn't listening on the standard port.
  • <tag> ... β€” open a series of xterms defined by <tag> in one of the supplementary configuration files (see "FILES").
Note: specifying a username on a cluster tag will override any usernames defined in the cluster.

πŸŽ€ KEY SHORTCUTS πŸŽ€

The following key shortcuts are available within the console window, and all of them may be changed via the configuration files. (yes, customizable, we love options πŸ’–)

  • Control-Shift-plus β€” open the 'Add Host(s) or Cluster(s)' dialogue box. multiple host or cluster names can be entered, separated by spaces.
  • Alt-n β€” paste in the hostname part of the specific connection string to each client, minus any username or port, e.g.
"scp /etc/hosts server:files/<Alt-n>.hosts"

would replace the <Alt-n> with the client's name in each window.

  • Alt-l β€” paste in the hostname of the server cssh is being run on
  • Alt-q β€” quit the program and close all connections and windows.
  • Alt-r β€” retile all the client windows.
  • Alt-u β€” paste in the username for the connection
  • Alt-1
  • Alt-2
  • Alt-3
  • Alt-4 β€” run the matching user defined macro on the server and send the output to the client

🌟 EXAMPLES 🌟

Open up a session to 3 servers

$ ctel server1 server2 server3

Open up a session to a cluster of servers identified by the tag 'farm1' and give the controlling window a specific title, where the tag is defined in one of the default configuration files

$ ctel -T 'Web Farm Cluster 1' farm1

Connect to different servers using different login names. NOTE: this can also be achieved by setting up appropriate options in the configuration files. do not close the console when the last terminal exits.

$ ctel user1@server1 admin@server2

Open up a cluster defined in a non-default configuration file

$ ctel -c $HOME/cssh.extra_clusters db_cluster

Override the configured/default port to use 2022 instead

$ ctel -p 2022 server1 server2

πŸ—‚οΈ FILES πŸ—‚οΈ

  • /etc/clusters, $HOME/.clusterssh/clusters β€” these files contain a list of tags to server names mappings. when any name is used on the command line it gets checked to see if it's a tag. if it is a tag, then the tag is replaced with the list of servers. The format is as follows:
<tag> [user@]<server>[:port] [user@]<server>[:port] [...]

e.g.

# List of servers in live
live admin1@server1 admin2@server2:2022 server3 server4

All comments (marked by a #) and blank lines are ignored. Tags may be nested, but be aware of using recursive tags, because they are not checked for. πŸ™ˆ

Servers can be defined using expansion macros:

"webservers websvr{a,b,c}"

would be expanded to

"webservers websvra websvrb websvrc"

and

"webservers websvr{6..9}"

would be expanded to

"webservers websvr6 websvr7 websvr8 websvr9"

Extra cluster files may also be specified either as an option on the command line (see "cluster-file") or in the user's $HOME/.clusterssh/config file (see "extra_cluster_file" configuration option).

NOTE: the last tag read overwrites any pre-existing tag of that name.
NOTE: there's a special cluster tag called "default" β€” any tags or hosts included within this tag will be automatically opened if nothing is specified on the command line.
  • /etc/tags, $HOME/.clusterssh/tags β€” very similar to clusters files but the definition is reversed. The format is:
<host> <tag> [...]

This allows one host to be specified as a member of a number of tags. This format can be clearer than using clusters files.

Extra tag files may be specified either as an option (see "tag-file") or within the user's $HOME/.clusterssh/config file (see "extra_tag_file" configuration option).

NOTE: All tags are added together
  • /etc/csshrc & $HOME/.clusterssh/config β€” this file contains configuration overrides β€” the defaults are as marked. Default options are overwritten first by the global file, and then by the user file.
✨ NOTE: okay so real quick bestie β€” values for entries do not need to be quoted unless it is required for passing arguments, e.g. πŸ’…
terminal_allow_send_events="-xrm '*.VT100.allowSendEvents:true'"

should be written as

terminal_allow_send_events=-xrm '*.VT100.allowSendEvents:true'

  • auto_close = 5 β€” close the terminal window after this many seconds. If set to 0 it will instead wait on input from the user in each window before closing. See also --autoclose and --no-autoclose. πŸ•
  • auto_quit = 1 β€” automatically quit after the last client window closes. Set to 0 to disable. See also --autoquit. πŸ‘‹
  • auto_wm_decoration_offsets = no β€” enable or disable the alternative algorithm for calculating terminal positioning. πŸͺŸ
  • command_pre =, command_post = β€” add extra commands around the communication method. For example:
command_pre= . $HOME/virtualenvs/default/bin/active ;
command_post= | ct

would allow for using Python virtual environments and then piping all shell output through "chromaterm" for syntax highlighting. πŸ’… Note: you must use appropriate command separators/terminators to keep the meaning of the command pipeline (such as ; and | between commands).

these are not put through macro parsing, bestie. no macros in here, periodt.
  • comms = telnet β€” sets the default communication method (initially taken from the name of the program, but can be overridden here). πŸ“‘
  • console_position = <null> β€” set the initial position of the console β€” if empty then let the window manager decide. Format is '+<x>+<y>', i.e. '+0+0' is top left hand corner of the screen, '+0-70' is bottom left hand side of screen (more or less). πŸ“
  • external_command_mode = 0600 β€” file mode bits for the external_command_pipe. πŸ”
  • external_command_pipe = <null> β€” define the full path to an external command pipe that can be written to for controlling some aspects of ClusterSSH, such as opening sessions to more clusters. πŸŽ›οΈ

Commands:

  • "open <tag|hostname>" - open new sessions to provided tag or hostname
  • "retile" - force window retiling

e.g.:

echo 'open localhost' > /path/to/external_command_pipe
  • external_cluster_command = <null> β€” define the full path to an external command that can be used to resolve tags to host names. This command can be written in any language. πŸ¦‹ The script must accept a list of tags to resolve and output a list of hosts (space separated on a single line). Any tags that cannot be resolved should be returned unchanged.

A non-0 exit code will be counted as an error, a warning will be printed and output ignored. ⚠️

If the external command is given a -L option it should output a list of tags (space separated on a single line) it can resolve.

  • extra_cluster_file = <null> β€” define an extra cluster file in the format of /etc/clusters. Multiple files can be specified, separated by commas. Both ~ and $HOME are acceptable as a reference to the user's home directory, e.g. 🏠
"extra_cluster_file = ~/clusters, $HOME/clus"
  • extra_tag_file = <null> β€” define an extra tag file in the format of /etc/tags. Multiple files can be specified, separated by commas. Both ~ and $HOME are acceptable as a reference to the user's home directory, e.g. 🏷️
"extra_tag_file = ~/tags, $HOME/tags"
  • key_addhost = Control-Shift-plus β€” default key sequence to open the AddHost menu. See "KEY SHORTCUTS" for more information. ⌨️
  • hide_menu = 0 β€” if set to 1, hide the menu bar (File, Hosts, Send, Help) in the console. πŸ™ˆ
  • key_clientname = Alt-n β€” default key sequence to send cssh client names to client. See "KEY SHORTCUTS" for more information. πŸ’Œ
  • key_localname = Alt-l β€” default key sequence to send hostname of local server to client. See "KEY SHORTCUTS" for more information. πŸ’Œ
  • key_paste = Control-v β€” default key sequence to paste text into the console window. See "KEY SHORTCUTS" for more information. πŸ“‹
  • key_quit = Control-q β€” default key sequence to quit the program (will terminate all open windows). See "KEY SHORTCUTS" for more information. πŸ’€
  • key_retilehosts = Alt-r β€” default key sequence to retile host windows. See "KEY SHORTCUTS" for more information. πŸ”„
  • key_username = Alt-u β€” default key sequence to send username to client. See "KEY SHORTCUTS" for more information. πŸ’Œ
  • key_user_1 = Alt-1, key_user_2 = Alt-2, key_user_3 = Alt-3, key_user_4 = Alt-4 β€” default key sequence to send user defined macros to client. If the matching macro_user_1 macro is undefined, the sequence is passed straight to the terminal. See "KEY SHORTCUTS" for more information. πŸŽ€
  • macro_servername = %s, macro_hostname = %h, macro_username = %u, macro_newline = %n, macro_version = %v, macro_user_1 = %1, macro_user_2 = %2, macro_user_3 = %3, macro_user_4 = %4 β€” change the replacement macro used when either using a 'Send' menu item, or when pasting text into the main console. πŸ”€
  • macro_user_1_command =, macro_user_2_command =, macro_user_3_command =, macro_user_4_command = β€” user defined macros β€” the macro is run through the shell on the server and the output is sent to the client. 🐚 For example,
"macro_user_1_command=echo echo macro_user_1"

would send the text echo macro_user_1 into the terminal session.

"macro_user_1_command=env | grep CSSH"

would send the CSSH environment variables to the client.

The following environment variables are set in the shell of the macro process:

"CSSH_SERVERNAME"
"CSSH_HOSTNAME"
"CSSH_USERNAME"
"CSSH_CONNECTION_STRING"
"CSSH_CONNECTION_PORT"
"CSSH_VERSION"
  • macros_enabled = yes β€” enable or disable macro replacement. Note: this affects all the macro_* variables above. 🌈
  • max_addhost_menu_cluster_items = 6 β€” maximum number of entries in the 'Add Host' menu cluster list before scrollbars are used. πŸ“œ
  • max_host_menu_items = 30 β€” maximum number of hosts to put into the host menu before starting a new column. πŸ—‚οΈ
  • menu_host_autotearoff = 0, menu_send_autotearoff = 0 β€” when set to non-0 will automatically tear-off the host or send menu at program start. βœ‚οΈ
  • mouse_paste = Button-2 (middle mouse button) β€” default key sequence to paste text into the console window using the mouse. See "KEY SHORTCUTS" for more information. πŸ–±οΈ
  • rsh = /path/to/rsh, ssh = /path/to/ssh, telnet = /path/to/telnet β€” set the path to the specific binary to use for the communication method, else uses the first match found in $PATH. πŸ”
  • rsh_args = <blank>, ssh_args = "-x -o ConnectTimeout=10", telnet_args = <blank> β€” sets any arguments to be used with the communication method (defaults to ssh arguments). πŸ› οΈ
NOTE: the given defaults are based on OpenSSH, not commercial ssh software. 😀
NOTE: any "generic" change to the method (e.g., specifying the ssh port to use) should be done in the medium's own config file (see ssh_config and $HOME/.ssh/config). πŸ“
  • screen_reserve_top = 0, screen_reserve_bottom = 60, screen_reserve_left = 0, screen_reserve_right = 0 β€” number of pixels from the screen's side to reserve when calculating screen geometry for tiling. Setting this to something like 50 will help keep cssh from positioning windows over your window manager's menu bar if it draws one at that side of the screen. πŸ“
  • terminal = /path/to/xterm β€” path to the X-Windows terminal used for the client. πŸ–₯️
  • terminal_args = <blank> β€” arguments to use when opening terminal windows. Otherwise takes defaults from $HOME/.Xdefaults or $HOME/.Xresources file. πŸ“
  • terminal_chdir = 0 β€” when non-0, set the working directory for each terminal as per terminal_chdir_path. πŸšͺ
  • terminal_chdir_path = $HOME/.clusterssh/work/%s β€” path to use as working directory for each terminal when terminal_chdir is enabled. The path provided is passed through the macro parser (see the section above on macros_enabled). πŸ”€
  • terminal_font = 6x13 β€” font to use in the terminal windows. Use standard X font notation. πŸ”‘
  • terminal_reserve_top = 5, terminal_reserve_bottom = 0, terminal_reserve_left = 5, terminal_reserve_right = 0 β€” number of pixels from the terminal's side to reserve when calculating screen geometry for tiling. Setting these will help keep cssh from positioning windows over your scroll and title bars or otherwise overlapping the windows too much. πŸ“
  • terminal_colorize = 1 β€” if set to 1 (the default), then -bg and -fg arguments will be added to the terminal invocation command-line. The terminal will be colored in a pseudo-random way based on the host name; while the color of a terminal is not easily predicted, it will always be the same color for a given host name. After a while, you will recognize hosts by their characteristic terminal color. 🌈✨
  • terminal_bg_style = dark β€” if set to "dark", the terminal background will be set to black and the foreground to the pseudo-random color. If set to "light", then the foreground will be black and the background the pseudo-random color. If terminal_colorize is "zero", then this option has no effect. 🎨
  • terminal_size = 80x24 β€” initial size of terminals to use. NOTE: the number of lines (24) will be decreased when resizing terminals for tiling, not the number of characters (80). πŸ“
  • terminal_title_opt = -T β€” option used with terminal to set the title of the window. 🏷️
  • terminal_allow_send_events = -xrm '*.VT100.allowSendEvents:true' β€” option required by the terminal to allow XSendEvents to be received. πŸ“¨
  • title = cssh β€” title of windows to use for both the console and terminals. πŸ‘‘

  • unmap_on_redraw = no β€” this tells Tk to hit the UnmapWindow request before it redraws terminal windows. It defaults to "no" because turning it on causes drama with the FVWM window manager πŸ’€. If your redraws are acting up, set it to "yes" so the window gets unmapped before it's repositioned.
  • use_all_a_records = 0 β€” if a hostname resolves to multiple IP addresses, set this to 1 and you'll connect to alllll of them, not just the first one it finds 🌈. See also --use-all-a-records.
  • use_hotkeys = 1 β€” set it to 0 and every single hotkey goes bye-bye πŸ™ˆ.
  • use_natural_sort = 0 β€” windows normally sort alphabetically, so like: host1, host11, host2. Set this to 1 and the sort order switches up to host1, host2, host11 ✨. NOTE: you need the perl module Sort::Naturally installed for this, no cap.
  • user = $LOGNAME β€” sets the default user for running commands on clients.
  • window_tiling = 1 β€” performs window tiling (set to 0 to disable it).
  • window_tiling_direction = right β€” the direction to tile windows in. "right" means start top left, move right, then down. Anything else means start bottom right, move left, then up πŸ¦‹.
NOTE: the key shortcut modifiers have to be in the form "Control", "Alt" or "Shift" β€” like, first letter capitalised, rest lowercase. Keys can also be disabled individually by setting them to the word "null" πŸ‘‘

$HOME/.clusterssh/send_menu

This (optional) file contains the items that populate the send menu πŸ’–. The default entry could be written as:

<send_menu>
  <menu title="Use Macros">
      <toggle/>
      <accelerator>ALT-p</accelerator>
  </menu>
  <menu title="Remote Hostname">
      <command>%s</command>
      <accelerator>ALT-n</accelerator>
  </menu>
  <menu title="Local Hostname">
      <command>%s</command>
      <accelerator>ALT-l</accelerator>
  </menu>
  <menu title="Username">
      <command>%u</command>
      <accelerator>ALT-u</accelerator>
  </menu>
  <menu title="Test Text">
      <command>echo "ClusterSSH Version: %v%n</command>
  </menu>
</send_menu>

Submenus can also be specified, like this:

<send_menu>
  <menu title="Default Entries">
    <detach>yes</detach>
    <menu title="Hostname">
        <command>%s</command>
        <accelerator>ALT-n</accelerator>
    </menu>
  </menu>
</send_menu>

Caveats:

  • There is currently no strict format checking of this file 😭
  • The format of the file may change in the future
  • If the file exists, the default entry (Hostname) is not added

The following replacement macros are available (note: these can be changed in the configuration file):

  • %s β€” Hostname part of the specific connection string to each client, minus any username or port
  • %u β€” Username part of the connection string to each client
  • %h β€” Hostname of server where cssh is being run from
  • %n β€” "RETURN" code
NOTE: requires XML::Simple to be installed 🫢

πŸ’€ KNOWN BUGS πŸ’€

If you have any ideas about how to fix the below bugs, please get in touch and/or provide a patch πŸ₯Ί.

  • Swapping virtual desktops can cause a redraw of all the terminal windows. This is due to a lack of distinction within Tk between switching desktops and minimising/maximising windows. Until Tk can tell the difference between the two events, there is no fix (apart from rewriting everything directly in X). Fr fr, that's the whole situation.

πŸ”§ TROUBLESHOOTING πŸ”§

If you have issues running ctel, first try:

"ctel -e [user@]<hostname>[:port]"

This performs two tests to confirm cssh is able to work properly with the settings provided within the $HOME/.clusterssh/config file (or the internal defaults).

  1. Test the terminal window works with the options provided
  2. Test telnet works to a host with the configured arguments

Configuration options to watch for in ssh are:

  • SSH doesn't understand "-o ConnectTimeout=10" β€” remove the option from the $HOME/.clusterssh/config file
  • OpenSSH-3.8 using untrusted ssh tunnels β€” use "-Y" instead of "-X", or use "ForwardX11Trusted yes" in $HOME/.ssh/ssh_config (if you change the default ssh options from "-x" to "-X")

🫢 SUPPORT AND REPORTING BUGS 🫢

A web site for comments, requests, bug reports and bug fixes/patches is available at: https://github.com/duncs/clusterssh

If you require support, please run the following commands and create an issue via: https://github.com/duncs/clusterssh/issues

"perl -V"
"perl -MTk -e 'print $Tk::VERSION,$/'"
"perl -MX11::Protocol -e 'print $X11::Protocol::VERSION,$/'"
"cat /etc/csshrc $HOME/.clusterssh/config"

Using the debug option (--debug) will turn on debugging output ✨. Repeat the option to increase the amount of debug. However, if possible please only use this option with one host at a time, e.g. "cssh --debug <host>", because of the amount of output produced (in both main and child windows). It's giving so much text, bestie 😭


πŸ‘€ SEE ALSO πŸ‘€

https://github.com/duncs/clusterssh/wiki/, "ssh", Tk::overview, X11::Protocol, "perl"


πŸ‘‘ AUTHOR πŸ‘‘

Duncan Ferguson, "<duncan_j_ferguson at yahoo.co.uk>"


Copyright 1999-2018 Duncan Ferguson.

This program is free software; you can redistribute it and/or modify it under the terms of either: the GNU General Public License as published by the Free Software Foundation; or the Artistic License.

See http://dev.perl.org/licenses/ for more information.


okay that's the whole page bestie, you're officially a ctel scholar now πŸŽ€ This edition is perl v5.40.1, dated 2026-01-14, and it's the CTEL(1p) manual β€” go forth and cluster, icon, periodt βœ¨πŸ’…

πŸ“¦ where this page comes from