Re: [Wien] parallel ssh error

2019-09-29 Thread Gavin Abo
Checking with "which lapw1c" on each node (vlsi1, vlsi2, vlsi3, and vlsi4) is a good idea.  However, since WIENROOT is (blank) [1], it probably won't work until that is resolved. It was mentioned that the WIEN2k .bashrc block was setup on each node by running userconfig [2]. So it definitely

Re: [Wien] parallel ssh error

2019-09-29 Thread Laurence Marks
What does ssh vlsi1 which lapw1c give, what does "cat *.error" give in the case directory? _ Professor Laurence Marks "Research is to see what everybody else has seen, and to think what nobody else has thought", Albert Szent-Gyorgi www.numis.northwestern.edu On Sun, Sep 29, 2019, 01:17

Re: [Wien] parallel ssh error

2019-09-29 Thread Gavin Abo
I had noticed that ssh vlsi1 'echo $WIENROOT/lapw*' seems to pick up the local environment.  Since you are interested in the remote environment, make sure you issue them as separate commands [1] for vlsi1, vlsi2, vlsi3, and vlsi4: ssh vlsi1 echo $WIENROOT/lapw* exit ssh vlsi4 echo

Re: [Wien] parallel ssh error

2019-09-29 Thread Indranil mal
Now echo $WIENROOT is giving the $WIENROOT location. echo $WIENROOT/lapw* /home/username/WIEN2K/lapw0 /home/username/WIEN2K/lapw0_mpi /home/username/WIEN2K/lapw0para /home/username/WIEN2K/lapw0para_lapw /home/username/WIEN2K/lapw1 /home/username/WIEN2K/lapw1c /home/username/WIEN2K/lapw1c_mpi