CRSH(1)

CRSH(1) πŸ’…

okay bestie, this is the manual for crsh, from the User Contributed Perl Documentation corner of the universe. sit down, grab a strawberry πŸ“, we're doing cluster admin today and it's gonna be iconic.


✨ NAME ✨

crsh β€” the cluster administration tool. yes, THE cluster administration tool. πŸ‘‘


🌸 VERSION 🌸

This documentation is for version: 4.19 πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

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

like. look at all those flags. she's serving. 🫢


there's a whole friend group, ok. each of these has its own man page, go read them too:

  • ccon β€” use console as the communication method
  • csftp β€” use sftp as the communication method
  • cssh β€” use ssh as the communication method
  • ctel β€” use telnet as the communication method

πŸ’œ DESCRIPTION πŸ’œ

so basically, this command opens an administration console and an xterm to all the hosts you specify. anything you type into the administration console gets replicated to every single window. and you can also type directly into any window if you're feeling spicy. πŸ’…

this tool is intended for (but not limited to) cluster administration β€” the vibe where the same config or the same commands have to be run on every node in the cluster. doing all of it at once through this tool is how you keep every node in sync. no cap. ✨

Connections are opened using rsh, which must be correctly installed and configured. that part is not optional, bestie.

⚠️ 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 modifying that is dangerous. it's better to search for the specific line you want to change and double-check all terminals are as expected before changes are committed. fr fr, do not skip the double-check. 😭

πŸŽ€ Further Notes πŸŽ€

please also see "KNOWN BUGS" (iykyk).

  • the dotted line on any sub-menu is a tear-off β€” click on it and the sub-menu turns into its own window. it's giving main character energy.
  • unchecking a hostname on the Hosts sub-menu will unplug the host from the cluster control window, so any text typed into the console is not sent to that host. re-selecting it plugs it back in. πŸ¦‹
  • if your window manager menu bars are obscured by terminal windows, go look at the screen_reserve_XXXXX options in the $HOME/.clusterssh/config file (see "FILES").
  • if the terminals overlap too much, go look at 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, 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 going to authenticate with a password), the sshd daemon at that location may refuse connections after 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:
crsh -e {single host name}

this will test the mechanisms used to open windows to hosts. the culprit could be 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 it could be the configuration of rsh. πŸ™ˆ


⭐ OPTIONS ⭐

some of these options may also be defined within the configuration file. default options are shown as appropriate. πŸ’–

  • --action '<command>', -a '<command>' β€” run the command in each session, e.g. -a 'vi /etc/hosts' to drop straight into a vi session. straight in. no detours. πŸ”₯
  • --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 s@, -C s@ β€” use the supplied file as an additional configuration file (see also "FILES"). this option may be repeated, and files are loaded in the order given.
  • --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. full screen, full drama. ✨
  • --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 the hosts for that tag are listed. NOTE: the format of the output changes when using the --quiet or -Q option.
  • --main-window-font '<font>', -M '<font>' β€” specify the font to use in the main console window. use Tk font notation such as sans 14 bold.
  • --man, -H β€” show full help text (the man page) and exit.
  • --no-autoclose β€” do not close terminal windows automatically (same as auto_close = 0).
  • --options '<STRING>', -o '<STRING>' β€” specify arguments to be passed to ssh when making the connection. NOTE: options for ssh should normally be put into the ssh configuration file; see ssh_config and $HOME/.ssh/config for more details. default: -x -o ConnectTimeout=10
  • --port <port>, -p <port> β€” specify an alternate port for connections.
  • --preserve-host-order, -P β€” display and tile hosts in the order given on the command line instead of alphabetically. order matters, bestie. 🫢
  • --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 the config file entry).
  • --username '<username>', -l '<username>' β€” specify the default username to use for connections (if different from the currently logged in user). NOTE: will be overridden by <user>@<host>.
  • --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 is not 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 πŸ‘‘

these are the key shortcuts available within the console window, and all of them may be changed via the configuration files. slay.

  • 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

$ crsh 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

$ crsh -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.

$ crsh user1@server1 admin@server2

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

$ crsh -c $HOME/cssh.extra_clusters db_cluster

override the configured/default port to use 2022 instead

$ crsh -p 2022 server1 server2

load multiple extra configuration files; later files override earlier ones

$ crsh -C ssh -C right 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 is checked to see if it is 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 as 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"

You can also yeet in extra cluster files, either as a command-line option (peep cluster-file) or tucked into your $HOME/.clusterssh/config file (that's the extra_cluster_file config option, more on that below).

NOTE: the last tag read wins β€” it straight-up overwrites any pre-existing tag with that same name. no merging, no negotiating πŸ’€
NOTE: there's a special cluster tag called default β€” anything (tags or hosts) you shove inside that one gets opened automatically if you don't specify anything on the command line. it's the "just do the thing, bestie" tag 🫢

/etc/tags, $HOME/.clusterssh/tags

Basically the same vibe as clusters files but reversed, the definition is flipped. The format is:

<host> <tag> [...]

The way this slaps is it lets one single host be listed as a member of a whole bunch of tags. ngl this format can be way clearer than wrestling with clusters files. ✨

Extra tag files can come in either as an option (see tag-file) or from your $HOME/.clusterssh/config file (see the extra_tag_file configuration option).

NOTE: All tags are added together. every single one. they stack. πŸ’…

/etc/csshrc & $HOME/.clusterssh/config

This file is where you drop configuration overrides β€” the defaults are marked below so you know what you're changing. Default options get overwritten first by the global file, and then by the user file. so user wins, always. πŸ‘‘

NOTE: values for entries don't need quotes unless you actually need them for passing arguments, like:
"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 you set it to 0 it will instead wait on input from you in each window before closing. See also --autoclose and --no-autoclose.
  • auto_quit = 1 β€” Automatically quit once the last client window closes. Set to 0 to disable. See also --autoquit.
  • auto_wm_decoration_offsets = no β€” Turn on/off the alternative algorithm for calculating terminal positioning.
  • command_pre = / command_post = β€” Add extra commands around the communication method. Like, for example:
command_pre= . $HOME/virtualenvs/default/bin/active ;
command_post= | ct

would let you use Python virtual environments and then pipe all shell output through chromaterm for syntax highlighting. Note: you must use appropriate command separators/terminators to keep the meaning of the command pipeline intact (stuff like ; and | between commands). These do not get put through macro parsing.

  • comms = rsh β€” Sets the default communication method (initially taken from the name of the program, but you can override it 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 the top left hand corner of the screen, '+0-70' is the bottom left hand side of the 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 you can write to for controlling some aspects of ClusterSSH, like opening sessions to more clusters.

Commands:

  • "open <tag|hostname>" β€” open new sessions to the 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 into host names. This command can be written in any language, go off. 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 can't be resolved should be returned unchanged.

A non-0 exit code counts as an error β€” a warning gets printed and the output is ignored.

If the external command is given a -L option it should output a list of tags (space separated on a single line) that 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 your 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 your 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 info.
  • 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 the client. See "KEY SHORTCUTS" for more info.
  • key_localname = Alt-l β€” Default key sequence to send the hostname of the local server to the client. See "KEY SHORTCUTS" for more info.
  • key_paste = Control-v β€” Default key sequence to paste text into the console window. See "KEY SHORTCUTS" for more info.
  • key_quit = Control-q β€” Default key sequence to quit the program (heads up: this terminates all open windows). See "KEY SHORTCUTS" for more info.
  • key_retilehosts = Alt-r β€” Default key sequence to retile the host windows. See "KEY SHORTCUTS" for more info.
  • key_username = Alt-u β€” Default key sequence to send the username to the client. See "KEY SHORTCUTS" for more info.
  • 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 the client. If the matching macro_user_1 macro is undefined, the sequence just gets passed straight through to the terminal. See "KEY SHORTCUTS" for more info.
  • 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 you're 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 gets 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 get 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 it 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 info.
  • 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, otherwise it 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 it takes defaults from your $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 the working directory for each terminal when terminal_chdir is enabled. The path you give gets 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.
  • main_window_font = "" β€” Font to use in the main console window. Use Tk font notation (e.g. "sans 14 bold"). When empty, the default is used (on 4K+ displays, Nimbus 14). πŸŽ€
  • terminal_reserve_top = 5 β€” number of pixels to reserve at the top of the terminal when calculating screen geometry for tiling.
  • terminal_reserve_bottom = 0 β€” number of pixels to reserve at the bottom.
  • terminal_reserve_left = 5 β€” number of pixels to reserve on the left.
  • terminal_reserve_right = 0 β€” number of pixels to reserve on the right.
bestie, setting these helps 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 β€” tell Tk to use the UnmapWindow request before redrawing terminal windows. This defaults to "no" as it causes some problems with the FVWM window manager. If you are experiencing problems with redraws, you can set it to "yes" to allow the window to be unmapped before it is repositioned.
  • use_all_a_records = 0 β€” if a hostname resolves to multiple IP addresses, set to 1 to connect to all of them, not just the first one found. See also "--use-all-a-records"}. 😭 (yes, that stray } is in the original, no cap)
  • use_hotkeys = 1 β€” setting to 0 will disable all hotkeys.
  • use_natural_sort = 0 β€” windows will normally sort in alphabetical order, i.e.: host1, host11, host2. Setting to this 1 will change the sort order, i.e.: host1, host2, host11. NOTE: You must have the perl module Sort::Naturally installed. 🌸
  • host_sort_command = <null> β€” define an external command that reads hosts from STDIN and writes the desired host order to STDOUT (whitespace-separated). This command is used for host sorting and takes precedence over "use_natural_sort". If the command cannot be started, exits non-zero, or outputs no hosts, cssh falls back to default lexical sorting.
  • preserve_host_order = 0 β€” when set to 1, display and tile hosts in the order given on the command line instead of sorting them alphabetically. See also "-P/--preserve-host-order".
  • user = $LOGNAME β€” sets the default user for running commands on clients.
  • window_tiling = 1 β€” perform window tiling (set to 0 to disable).
  • window_tiling_direction = right β€” direction to tile windows, where "right" means starting top left and moving right and then down, and anything else means starting bottom right and moving left and then up.
NOTE: The key shortcut modifiers must be in the form "Control", "Alt" or "Shift", e.g. with the first letter capitalised and the rest lower case. Keys may also be disabled individually by setting to the word "null". ✨

$HOME/.clusterssh/send_menu πŸŽ€

This (optional) file contains items to 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 as follows:

<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).

πŸ› οΈ TROUBLESHOOTING πŸ› οΈ

If you have issues running crsh, first try:

"crsh -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 internal defaults).

  1. Test the terminal window works with the options provided.
  2. Test rsh 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>" due to the amount of output produced (in both main and child windows). 😭


πŸ‘€ SEE ALSO πŸ‘€


πŸ‘‘ 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.


and that's a wrap, bestie! πŸ’– this iconic page was brought to you by perl v5.42.2 on 2026-05-05 β€” go forth and cluster your ssh like the main character you are. πŸ’…βœ¨

πŸ“¦ where this page comes from