Difference between revisions of "Shell Service"

From Tardis
Jump to navigation Jump to search
m (Link to new Tutorials)
Tag: Replaced
(15 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Usage Guide ==
No shell service is currently available due to [[2022 Move|the move]].
[[Vortis]] runs the primary shell login service for Tardis, externally accessible via <code>ssh.tardis.ed.ac.uk</code>. 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 <code>ssh <var>username</var>@ssh.tardis.ed.ac.uk</code>
from a command shell. For those in Windows, you are advised to have a look at [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]. Use this to connect to <tt>ssh.tardis.ed.ac.uk</tt>, giving the supplied username and password.
You can change the password on your new account using <code>passwd</code> 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, but there also exists a Solaris shell host on [[Argolin]] which can be accessed at <code>sssh.tardis.ed.ac.uk</code>.
== 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"[http://www.linuxmanpages.com/man1/screen.1.php#lbAH].  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.

Latest revision as of 00:17, 26 February 2022

No shell service is currently available due to the move.