On Wed, Jun 9, 2010 at 6:14 AM, Gavin Brock <gavin.br
...@gmail.com> wrote:
> Stew,
> Great idea!!
> Took slightly longer to implement than I expected - mostly due to getting
> distracted :-)
> A first cut at it is in svn: http://csshx.googlecode.com/svn/trunk/csshX
> This adds the "--hosts" and prerequisite "--remote_command" arguments (and
> equivalent csshrc options).
> The file format is similar to your suggestion, but I opted to drop the
> double-quotes on the commands:
> root@server1 /bin/sh script.sh 20091001
> I assume everything after the hostname string is a command to run (and
> avoid having to do complicated checking for quotes in the command).
> The hostname can, as you showed, contain user names or port numbers. It
> will also support the hostname ranges (like "server[1-9]").
> Let me know how it works for you, if you have time.
> Regards,
> Gavin
> On 2 Jun 2010, at 05:59, Stew wrote:
> i would like the ability to add an optional command to specify to the
> remote host.
> This would be useful in the case where you want to connect to
> potentially just one host multiple times and run a slightly different
> command.
> The format of this file might look like (mockup):
> # csshX --hosts servers.txt
> # cat servers.txt
> root@server1 "/bin/sh script.sh 20091001"
> root@server1 "/bin/sh script.sh 20091101"
> root@server1 "/bin/sh script.sh 20091201"
> root@server1 "/bin/sh script.sh 20100201"
> root@server1 "/bin/sh script.sh 20100101"
> This would almost necessitate the ability to take an input file of
> hosts (one per line) with an optional quoted string -- which will be
> the command run on the remote side.
> user@host[:port] [command with args]
> I could accomplish this today use GNU screen but it doesn't allow me
> to see all the windows simultaneously of course like csshX.
> What do you think? Thanks!
> On May 31, 7:01 pm, brockgr <gavin.br...@gmail.com> wrote:
> Seems like the requests for features have died down - is there
> anything left to add?
