Open main menu

CDOT Wiki β

Changes

SPO600 Servers

856 bytes added, 15:31, 10 September 2017
no edit summary
{{Admon/important|Backup Your Data|These computers are NEVER backed up. Please save all important files on other storage. '''These machines may fail, be removed or be reinstalled at any time.'''}}
In [[SPO600]], remote access to servers is provided for learning and project work. It is recommended that you also set up [[SPO600 Host Setup|a personal Linux system]].
 
== Preparatory Steps ==
{{Admon/tip|Check Your Key!|Your professor uses an automated script to create accounts, so the key must be valid, in the OpenSSH format, and correctly named in order to work successfully.}}
 
== Available Servers ==
ssh ''username''@xerxes.cdot.systems
 
== Simplified SSH Access ==
ssh xerxes
{{Admon/important|Common SSH Problems|Your ssh private key must be You can similarly configure simplified access in your <code>~/.ssh</code> directory and have correct permissions (0600). If your SSH public key is not named <code>~/.ssh/id_rsa</code>, your most other SSH client may not automatically find it. You can specify the identity (private key) file using the <code>-i</code> argument to the SSH commandprograms.}}
 == SSH Access from Other Clients Client Systems ==
If you wish to access the servers from additional computers, you can append the SSH public keys from those computers to the <code>~/.ssh/authorized_keys</code> file.
In order to use <code>sudo</code>, you will need to know your password. An initial random password is provided in the file <code>~/password.txt</code> (note that your password will be different on each server). Feel free to change this with the <code>passwd</code> command -- not by editing the file, which is provided only for your information!
 
== Multiuser Access ==
Remember that these machines are multi-user systems. Use the <code>w</code> or <code>who</code> commands to see who else is using them; you can also try using the <code>write</code> command to communicate with another user if required.
 
 
== Backup Your Accounts ==
 
These accounts are ''never'' backed up, and the machines may fail, lose data, or be reinstalled without warning at any time. Please back up your work frequently by copying it to another system or storage device.
 
 
== Common SSH Problems ==
 
With the OpenSSH client:
# Your ssh private key must be in your <code>~/.ssh</code> directory (which must have 0700 permission) and the private key file must have 0600 permissions -- no more and no less.
# If your SSH public key is not named <code>~/.ssh/id_rsa</code>, your SSH client may not automatically find it. You can specify the identity (private key) file using the <code>-i</code> argument to the SSH command.}}
 
With other SSH clients:
# Your key must be in OpenSSH format when you send it to your professor; this format is used by the default SSH client on Mac OS/X and Linux as well as PuTTY. If it is in SSH2 format, used by some other client programs, you can convert it with this command on a Linux system with OpenSSH (such as Matrix):
ssh-keygen -i -f ~/.ssh/''SSH2_PUBLIC_KEY_FILE''.pub > ~/.ssh/''OPENSSH_PUBLIC_KEY_FILE''.pub
 
== Disconnect/Reconnect Ability ==
The [[Screen Tutorial|screen]] utility provides disconnect/reconnect capability, which is very useful for unstable network connections, long interactive operations, and changing your work location.