Shell Accounts

From FyshyWyky
Revision as of 00:03, 9 March 2010 by Athan (talk | contribs) (Access: pond -> lake)


By default any user account on has shell login enabled. This principally means you can make use of SSH to login to the account with full access to your own files and all software installed on the machine. A few accounts are restricted to only using remote services like POP3 and IMAP for email, but this is far from the norm.


The only direct access to is via the Internet (specifically IPv4, we do not support IPv6 yet). There is no dial-up or similar access.

As mentioned, primary access to a shell account is via SSH. We do still offer telnet access, but as this is in plain-text, including when you type in your password, it is advisable to avoid this unless you simply cannot run an SSH client. It is possible to use telnet over SSL so that the connection is encrypted.

We do not offer rlogin or rsh access, please use SSH instead.


As the name 'shell account' implies once you have logged in you will be presented with a shell prompt. The default shell for a account is bash, although we do also have tcsh and zsh installed and users may run the 'chsh' command to change their default shell.

If you need any guidance on using such a shell try a Google search such as 'unix shell tutorial' to find a tutorial.


Other than those restrictions mentioned below please make sure that any and all of your shell account use complies with our AUP.

We operate very few restrictions as to what you can do with your shell account.

Most accounts do have fairly strict resource limits applied, to prevent any single user hogging all the memory or CPU on the machine. If you find these restrictions are overly strict for your purpose then ask us to loosen them up for you, giving details of what you're trying to do that seems to be failing due to the limits.

We do not currently use any disk quota scheme, but if we encounter problems with users filling available space we may have to implement such so as to protect other users.

You may leave processes running without an active login, just ensure they aren't going to hog system resources (RAM, CPU, or disk space) in your absence.