Machines at uni-duesseldorf

Hi all, Here's an update on the computers that we have for PyPy at the HHU. Snake is back, but nothing wrong was found with its hardware, which means that it'll probably continue to hang randomly from time to time... Maybe we'll reinstall the machine from scratch. For all I know it could be corrupted system files. However, there are now two other machines. Just like snake they are machines whose performances can be a bit strange - hyperthreaded Xeon cores. Each core has roughly snake-like performance, but each machine has got 4 cores. The software setup is: SuSE Linux base, which I'm hiding as much as possible behind a Gentoo Linux installation in the /gentoo directory. When you log in, you reach a chrooted environment, so you should not see that at all unless you dig in special files. I've copied some accounts from codespeak, so you must use the same public key to log in (no password logins). Just ask me if you want to use the machines but I forgot to copy your account over. To login, you must use port 922 instead of 22. The latter would reach the SSH daemon of the outer SuSE installation (where you don't have an account). I recommend adding the following lines to your file ~/.ssh/config: Host wyvern HostName wyvern.cs.uni-duesseldorf.de Port 922 Host cobra HostName cobra.cs.uni-duesseldorf.de Port 922 Then you can log in with 'ssh wyvern' or 'ssh cobra'. Note that 'wyvern' is the fastest machine so feel free to prefer it. A great way to use them is for distributed testing. Put in your file ~/conftest.py: disthosts = ['wyvern'] * 4 + ['cobra'] * 4 Then you can do 'py.test --session=R'. Try also the --runbrowser option. A bientot, Armin

On Wed, 27 Dec 2006 11:44:34 +0100, Armin Rigo <arigo@tunes.org> wrote:
Unless these machines have the same ssh host keys, you'll experience a nasty message when you attempt to log in, unless you only ever use port 922 or port 22. Add this under the host config of each host that connects on an alternate port to make that go away: UserKnownHostsFile ~/.ssh/known_hosts.922 It will make the hosts file a different file on disk, so you won't have port 922 and 22 having different rsa fingerprints causing you grief, while retaining the ability to check that the host/port combinations rsa key. Stephen.

Hi Stephen, On Wed, Jan 24, 2007 at 01:50:11PM +1000, Stephen Thorne wrote:
I seems to depend on the version of ssh. In my known_hosts file I see two entries: one for 'wyvern.cs.uni-duesseldorf.de,134.99.112.213' and one for '[wyvern.cs.uni-duesseldorf.de]:922,[134.99.112.213]:922'. So at least OpenSSH_4.5p1 distinguishes by port automatically. I don't think many people other than me have an account on the port 22, too. Thanks for the note nevertheless! A bientot, Armin.

On Wed, 27 Dec 2006 11:44:34 +0100, Armin Rigo <arigo@tunes.org> wrote:
Unless these machines have the same ssh host keys, you'll experience a nasty message when you attempt to log in, unless you only ever use port 922 or port 22. Add this under the host config of each host that connects on an alternate port to make that go away: UserKnownHostsFile ~/.ssh/known_hosts.922 It will make the hosts file a different file on disk, so you won't have port 922 and 22 having different rsa fingerprints causing you grief, while retaining the ability to check that the host/port combinations rsa key. Stephen.

Hi Stephen, On Wed, Jan 24, 2007 at 01:50:11PM +1000, Stephen Thorne wrote:
I seems to depend on the version of ssh. In my known_hosts file I see two entries: one for 'wyvern.cs.uni-duesseldorf.de,134.99.112.213' and one for '[wyvern.cs.uni-duesseldorf.de]:922,[134.99.112.213]:922'. So at least OpenSSH_4.5p1 distinguishes by port automatically. I don't think many people other than me have an account on the port 22, too. Thanks for the note nevertheless! A bientot, Armin.
participants (2)
-
Armin Rigo
-
Stephen Thorne