- Please, use the 'nice' command for long running programs on Lucas. Also, let the Lab Administrators know who and why you need to run these processes. Otherwise, they will be killed off as needed.
- We have made changes on Lucas and it's dedicated clients such that you should not be prompted for your password a second time as you ssh into Lucas and then it redirects you to a dedicated Lucas client. The only thing you may need to do is to "accept" the client's SSH signature as it connects you.
- Lucas and NOVA use an LDAP server for authentications in the back-end. To access account information and to update passwords correctly in Linux, use the smbldap-tools.
- THERE IS NO TELNET OR FTP INTO THIS SYSTEM. To replace these are the SSH, SCP and SFTP commands. To learn more click here .
- DO NOT WORK DIRECTLY ON THE SERVER.
- If you are logged into a lab client, just do your work from there. All of the user directories and software are installed the same way as the server systems.
- If you are connecting remotely through ssh, once into Lucas itself you will be reconnected to a random dedicated Lucas client. This is like a High Performance cluster in that we try to distribute the users across mulitple systems.
- If you find yourself at a 'Lucas>' prompt, just type 'gotoclient' to be reconnected to a dedicated client system.
- In Windows, you are NOT ALLOWED TO INSTALL SOFTWARE, EVEN FREEWARE. This is not just University Policy. By installing software you are going to change the behaviour of the local machine, even if you install to your Z: Drive. It will affect all following users and will break/change other softwares behaviour.
- Store all of your files on Z:. Even if the default storage location is in "My Documents" or on your Desktop, it is part of your profile. The larger your profile, the longer it takes to login and logout, and the more likely there will be an error and your profile will be lost or corrupted. Everytime you start a new file/project/download you should specify the location as starting with "Z:\".
- Grad students are allowed to run long running, distributed programs on one or more of the dedicated clients, but PLEASE, use the 'nice' command to make it a lower priority task than the interactive users. For long running research projects, please notify the Lab Administrators about what you are running, for how long and why it is needed.
If you are a student, staff or faculty member with an account on this system you can use this Java based SSH login to this system
About Lucas' Hardware
Lucas is a Student Server in the Temple University CIS department. It is currently a pair of Linux systems setup in a fail-over pair of High Availability systems. This fail-over is not automatic and a work in progress.
System Hardware Configuration
- Dell PowerEdge 830 Pentium D Processor
- 4 GB SDRAM
- 2.4 TB Total Disk Space in a RAID-10 configuration using 6 x 400 GB SATA HDDs, giving 1.2 TB of usable disk space
- 3 x 1Gb Network interfaces
Dedicated Lucas Clients
The dedicated clients are used so as to keep the users from doing thier work directly on the Lucas server itself. If this was a true High Availability/High Performance cluster, these clients would be the worker nodes.
But, this is not a true cluster. Lucas does have it's server processes running directly on the server, not distributed across multiple worker nodes. In a true cluster, each service would be redirected to a worker node who is actually running that process on the server's behalf. In our case, we are only distributing the SSH protocol port. This is the SSH interactive shell login users.
The whole reason to do this is to keep mis-behaving programs and rebooting systems from affecting the majority of the users. By having a dedicated client fail, a handful of users, the ones connected to that same client system, are affected, not all currently logged in users to the Lucas server itself.
Here is a list of the current Lucas Dedicated Clients:
NOTE:We try to keep hostnames to eight characters or less for compatability reasons.
|Superman||Up||FC10||P4 2.8GHz, 1GB RAM|
|Batman||Up||FC10||P4 2.8GHz, 1GB RAM|
|WonderW||Up||FC10||P4 2.8GHz, 1GB RAM|
|GrnLntrn||Up||FC10||P4 2.8GHz, 1GB RAM|
|Flash||Up||FC10||P4 2.8GHz, 1GB RAM|
|CaptAmer||Up||FC10||P4 2.8GHz, 1GB RAM|
|Ironman||Up||FC10||P4 2.8GHz, 1GB RAM|
|Antman||Up||FC10||P4 2.8GHz, 1GB RAM|
|Cyclops||Up||FC10||Core2 Duo 2.13GHz, 4GB RAM|
|Colosus||Up||FC10||Core2 Duo 2.13GHz, 4GB RAM|
|Storm||Up||FC10||Core2 Duo 2.13GHz, 4GB RAM|
|Gambit||Up||FC10||Core2 Duo 2.13GHz, 4GB RAM|
|Rouge||Up||FC10||Core2 Duo 2.13GHz, 4GB RAM|
|Wolverine||Up||FC10||Core2 Duo 2.13GHz, 4GB RAM|
|Kitty||Up||FC10||Core2 Duo 2.13GHz, 4GB RAM|
To connect to any Linux or Unix system inside Temple, please use a Secure Shell ( SSH ) client software instead of Telnet or FTP. Inside more Unix/Linux based systems just use "ssh username@hostname" from your command prompt. For Windows please use the Java Applet SSH Login, or the SSH icon if you are in our labs, or download one of these programs for at home:
- PuTTY, a free, small, and feature rich Telnet and SSH tool
- WinSCP is a MS Windowsprogram to display Unix server directories as a Window for drag and drop file transfers. This program uses the scp feature of SSH since we have FTP disabled for security reasons