access
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| access [2023/09/13 09:31] – [Private servers] olivier | access [2025/12/01 14:40] (current) – [X2GO] olivier | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| Once connected to the server, you will be presented with a Linux command line. If unfamiliar with the Linux environment, | Once connected to the server, you will be presented with a Linux command line. If unfamiliar with the Linux environment, | ||
| + | To use Key access, refer to the following page: [[access: | ||
| ==== Private servers ==== | ==== Private servers ==== | ||
| - | Some CIM computers are on a private (internal) McGill vlan (10.69.54.0/ | + | Some CIM computers are on a private (internal) McGill vlan (10.69.54.0/ |
| The command to connect to a private CIM computer is: | The command to connect to a private CIM computer is: | ||
| < | < | ||
| - | ssh -j < | + | ssh -J < |
| </ | </ | ||
| Line 30: | Line 30: | ||
| ==== PuTTY ==== | ==== PuTTY ==== | ||
| - | If you are on another type of operating | + | The Windows commandline now includes an SSH client, but if you routinely log into a remote |
| When you open PuTTY, you'll be presented with a configuration screen where only two options need to be configured, the server address (barn.cim.mcgill.ca) and the connection type (SSH). | When you open PuTTY, you'll be presented with a configuration screen where only two options need to be configured, the server address (barn.cim.mcgill.ca) and the connection type (SSH). | ||
| Line 40: | Line 40: | ||
| === Private servers === | === Private servers === | ||
| To access private CIM servers, you'll need to configure an SSH proxy in PuTTY. | To access private CIM servers, you'll need to configure an SSH proxy in PuTTY. | ||
| + | |||
| + | ==== X2GO ==== | ||
| + | |||
| + | For remote desktop access to CIM servers, you can use x2go. (most CIM servers should be setup for it, but please contact us if a machine does not have the x2go server installed) | ||
| + | |||
| + | To use x2go, you will need the x2go client install on your local machine. | ||
| + | |||
| + | < | ||
| + | # sudo apt-get install x2goclient | ||
| + | </ | ||
| + | |||
| + | Once the client is installed, you can configure the connection with the following settings: (change the login to your username and the host from barbados.cim.mcgill.ca to the machine you want to connect to) | ||
| + | |||
| + | {{ :: | ||
| + | |||
| + | Once the connection is configured, you should be able to connect and use the remote desktop. | ||
| + | |||
| + | {{ :: | ||
| + | |||
| + | If you need to use the GPU for graphical applications, | ||
| ===== File Access ===== | ===== File Access ===== | ||
| Line 55: | Line 75: | ||
| It is also possible to define an ssh jump host to the scp commands by adding '' | It is also possible to define an ssh jump host to the scp commands by adding '' | ||
| + | |||
| + | ==== sshfs ==== | ||
| + | To mount directories with sshfs, while going through a jump host, the following command can be used: | ||
| + | < | ||
| + | sshfs -o ProxyJump=< | ||
| + | </ | ||
| + | |||
| + | If you prefer defining the jump host in your ssh_config file for more convenient access, you should specify the jump host and the target hostname separately, as such: | ||
| + | |||
| + | < | ||
| + | Host barn | ||
| + | HostName barn.cim.mcgill.ca | ||
| + | User < | ||
| + | |||
| + | Host < | ||
| + | HostName < | ||
| + | ProxyJump barn | ||
| + | User < | ||
| + | </ | ||
| + | |||
| + | You can then use the following command to mount remote directories: | ||
| + | |||
| + | < | ||
| + | sshfs < | ||
| + | </ | ||
| ==== Filezilla ==== | ==== Filezilla ==== | ||
| Line 64: | Line 109: | ||
| Set the protocol to '' | Set the protocol to '' | ||
| + | |||
| + | |||
| + | ===== Sudo on CIM Workstations ===== | ||
| + | |||
| + | > "With great power comes great responsibility..." | ||
| + | |||
| + | > "God, root, what is difference?" | ||
| + | |||
| + | Generally speaking, users do not have sudo/root access on CIM workstations. This is because, unlike Windows or MacOS, Linux gives much more power to the user. Windows will give you warnings and/or prevent you from erasing critical system files, whereas if you use sudo carelessly, Linux will delete the running kernel without so much as a warning. | ||
| + | |||
| + | Things to consider as a user with sudo: | ||
| + | * sudo is the same as root which is the same as administrator. | ||
| + | * sudo can be used to break your system. If you share your system with other users, you can/will break the system for them too. | ||
| + | * If in doubt, ask us before trying something. Some things on CIM systems are done for a reason, or are configured in a specific way. There is often a reason for this. | ||
| + | |||
access.1694611911.txt.gz · Last modified: by olivier
