Difference between revisions of "Shell Service"

From Tardis
Jump to: navigation, search
(Shell Server)
(Shell Server)
Line 10: Line 10:
  
 
== Shell Server ==
 
== Shell Server ==
We run OpenSSH version ~4.3 (or so) authenticated against [[LDAP]]. The primary shell login host is [[Vortis]] which runs Linux. To log in ssh <code>user@ssh.tardis.ed.ac.uk</code>
+
We run OpenSSH version ~4.3 (or so) authenticated against [[LDAP]]. The primary shell login host is [[Vortis]] which runs Linux. To log in ssh <code>user@ssh.tardis.ed.ac.uk</code>. Please be aware that the new SSH server [[Torchwood]] will ban you for 30 minutes after 6 successive failed login attempts and notify the sysadmins.
  
 
== Screened Irssi Timeouts ==
 
== Screened Irssi Timeouts ==

Revision as of 17:01, 12 December 2014

This page is out of date and needs rewriting.
The content is likely to be incomplete or incorrect.

Usage Guide

Vortis runs the primary shell login service for Tardis, externally accessible via ssh.tardis.ed.ac.uk. In order to log in to the Tardis systems you will need to obtain an SSH client. For those with Linux/Unix systems, you should be able to run ssh username@ssh.tardis.ed.ac.uk from a command shell. For those in Windows, you are advised to have a look at PuTTY. Use this to connect to ssh.tardis.ed.ac.uk, giving the supplied username and password.

You can change the password on your new account using passwd from the command line, and you are advised to do so on your first log in. You can read your mail off the system using pine, or whatever your preferred mail client is.

For more help in actually getting started using a shell see Tardis Beginner Tutorials.

Shell Server

We run OpenSSH version ~4.3 (or so) authenticated against LDAP. The primary shell login host is Vortis which runs Linux. To log in ssh user@ssh.tardis.ed.ac.uk. Please be aware that the new SSH server Torchwood will ban you for 30 minutes after 6 successive failed login attempts and notify the sysadmins.

Screened Irssi Timeouts

For some time we had a problem with IRC sessions running between screen(ed) irssi(s) on gallifrey and the IRC Service timing out. This was not down to a networking problem, but to a feature of screen, where it "waits until the display restarts to accept the output"[1]. This was happening when ssh timeouts occurred or when a user pressed ctrl+s and was rather annoying for other IRC users.

The solution, suggested by Patrick (not bung), was to add 'defnonblock on' to /etc/screenrc so that screen's default behaviour was to use an internal 1s timeout on the "display" (ssh in this case). Once this timeout is reached, screen will restart accepting output from its children and buffer it as it would if the screen were detached.