Closed GoogleCodeExporter closed 9 years ago
Unfortunately, we've had about three recent suggestions for changes to the
hosts file format, and it simply won't be possible to accommodate them all.
Currently you can specify the username and port separately for each host, as
each line is of the form user@host:port. Likewise, individual settings can be
managed by ssh itself (man ssh_config for more details). Are there any
critical settings that can't be added using these two mechanisms for
customization?
Thanks for your interest in using pssh and making it better.
Original comment by amcna...@gmail.com
on 17 Mar 2011 at 9:20
Honestly,I didn't know about this ssh future.
All the options I nedd (user, key, port, compression) can be set in the
ssh_config file so, for pssh, we could even leave the simple host file list.
Correct me If I'm wrong, but by ssh_config file, we can pass all the options of
command line.
On consideration. Watch this ssh_config example:
Host pippo
User root
Port 22
Hostname 192.168.2.153
"pippo" is not a valid dns name. "ssh pippo" works fine because it uses
"Hostname" option.
So, the pssh host file, should list the host 'pippo' and not '192.168.2.153'.
Or we use a convention: hostname/ip of the pssh host.txt file are the same ho
"Host" declaration of ssh_config.
Last: in any case, we need a bit of documentation :-)
Original comment by siri...@gmail.com
on 18 Mar 2011 at 7:34
Indeed, giving pssh the same host as in the "Host" declaration of ssh_config
works well, and it might be helpful to add this to the examples section of the
man page. And again, if it's just user and port that need to be specified,
pssh already allows these in the hosts file, so ssh_config would normally be
for extra options like compression.
Original comment by amcna...@gmail.com
on 18 Mar 2011 at 3:22
I just added a TIPS section to the man page with a brief description of
ssh_config. I'll close this issue for now, but please feel free to reopen it
if you have any additional thoughts. Thanks.
Original comment by amcna...@gmail.com
on 23 May 2011 at 6:49
Original issue reported on code.google.com by
siri...@gmail.com
on 17 Mar 2011 at 9:13