From: Jim Phillips (jim_at_ks.uiuc.edu)
Date: Tue Dec 20 2016 - 23:29:12 CST
It looks like this all started here:
Not the most flexible solution, but OpenSSH is ubiquitous these days.
Your options for using rsh are:
1) Use "++remote-shell /path/to/myrsh" where myrsh is a script that calls
rsh correctly, e.g.: exec rsh $1 /bin/bash -f
2) If you have a working mpiexec on your system, use ++mpiexec.
On Tue, 20 Dec 2016, Scott Brozell wrote:
> This problem that charmrun now passes openssh options still exists in
> 2.12b1 according to a quick check with the download:
> On Wed, Jan 13, 2016 at 01:04:54PM -0500, Scott Brozell wrote:
>> A batch script that works correctly with previous versions of NAMD,
>> 2.10, etc., is failing with 2.11.
>> The initial error is due to a charmrun change to ssh for the default remote shell:
>> Host key verification failed.
>> Charmrun> Error 255 returned from remote shell (n72:0)
>> Using ++remote-shell rsh or export CONV_RSH=rsh yields the same new failure:
>> n75: invalid option -- 'o'
>> usage: rsh [-nd] [-l login] host [command]
>> Charmrun> Error 1 returned from remote shell (n75:0)
>> Digging deeper the problem is that charmrun now passes openssh options:
>> Charmrun> Starting rsh n75 -l me -o KbdInteractiveAuthentication=no -o PasswordAuthentication=no -o NoHostAuthenticationForLocalhost=yes /bin/bash -f
>> For reference in 2.10:
>> Charmrun> Starting rsh n19 -l me /bin/bash -f
>> How can these invalid options be eliminated ?
>> This page doesn't contain a version or a change log that would show
>> changes to defaults or show the need to tinker with the remote shell stuff:
>> This page is clearly stale:
>> This page is not as clearly stale; how about a date stamp or some other
>> obvious clue that it is being maintained?
>> I recommend that your quality assurance and quality control processes
>> be reviewed.
This archive was generated by hypermail 2.1.6 : Sun Dec 31 2017 - 23:20:54 CST