Child pages
  • What Linux systems are available?

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Please keep in mind that there are many non-SICE research systems available to all IU researchers.  This includes various large computing and storage systems, including Big Red II3, Karst, MasonCarbonate, and the Scholarly Data Archive (SDA) that we encourage you to take advantage of.  See the Research System Knowledge Base Page and the UITS Research Technologies Homepage for further information about these systems.

...

  • Sharks - The Sharks systems are available to all SICE faculty, staff, and graduate students (CS and Informatics). Access can also be granted to undergraduate and non-SICE students and guests with sponsorship by a member of the SICE faculty. Accounts are created automatically for all SICE graduate students (CS and Informatics). Accounts for other users can be created by having the faculty sponsor make the account request using the Help Desk.
     
  • iris/cat - ILS maintains login servers iris and cat. Iris is available to those currently taking SICE graduate level courses. Cat is reserved for faculty/staff. These hots provide command line access and mount ILS Linux home directories.
     
  • Ella/Info - ILS maintained web servers. Include support for perl,php, etc. (running as user). Ella is for use by those currently enrolled in SICE graduate level courses. Info is for faculty, staff and professional associations. 
    • Accounts for the above listed ILS servers are generated based on enrollment data provided by the registrar near the start of each semester. 
    • Web based tools to kill one's own runaway scripts and to view one's own error logs are pre-loaded into users' web accounts – password protected behind a secure login.

 



Caveats and Tips

These systems are shared resources that are used by many people. While there are few limitations on their use, please use them in a way that minimizes your overall impact on other users. For example, limit the number of simultaneous CPU or memory intensive process, kill runaway processes, and use nice for long-running processes that consume a lot of CPU cycles. For more information about viewing and killing processes as well as using nice to adjust a processes priority, please see the following KB page:

...