SSSC User's Guide

Account Information

Policy

Any SOI team member may obtain a personal account on the SSSC. Logins are permitted on any of the machines listed below. There are no individual quotas on disk space usage nor on processing time, but users should respect both the system pipeline processing requirements and the needs of the users at the SSSC itself. Disk working space allocations are described below.

Machines

All hosts listed are in the domain stanford.edu.

tarax - a Silicon Graphics (SGI) Power Challenge system containing 12 R8000 75 MHz MIPS processors and 3 GB of RAM, running IRIX 6.1, the SGI unix operating system. This is the pipeline processing system. Public use may be subject to restrictions at times.
fault - SGI system containing 4 R4400 150 MHz MIPS processors and 768 MB memory, running IRIX 5.3. This system is the designated ``analysis machine''.
SGI Workstations - all 200 MHz R4400's with 128 MB memory running IRIX 5.3 except as noted.
- corona - 250 MHz, running IRIX 6.2
- khors - 256 MB
- phil
- phoebus
- rick - 192 MB
- shaman - 250 MHz
- shock - 256 MB
- shoom
- soieof - 150 MHz, 64 MB
- yeti - 100 MHz R4000, 112 MB
Sun Workstations - all running SunOS in version noted.
- quiver - SPARC-20, 5.5
- shiver - SPARC-10, 4.1.3
- skaelv - SPARC-10, 4.1.3
quake - a Digital Equipment (DEC) RISC system 5500 running Ultrix X.Y.
DEC Workstations - all running Ultrix 4.3 except as noted.
- flytrap
- griffin
- rumble

There are also a number of NCD X-terminals scattered around the SSSC. There are a few special-purpose machines which should not be used for computing or logins (general logins may even be disabled on them):

soi - DEC 3100, Ultrix 4.2 : the World Wide Web server
soidb - SGI R4400, IRIX 5.3

Disk Space

Policy

Files on user home directories are backed up daily. There is insufficient space on the files systems containing these directories to permit the storage of large working data sets of more than 10's of MB (a few MDI images), and working space is provided on separate file systems that are not backed up. Working space is provided in two flavors: scratch space, which is specifically designated for individual users or groups of users and whose maintenance is wholly their responsibility; and temporary space, which is open to all and is subject to automatic purge when usage exceeds certain limits.

Scratch directories are designated /scrX, where X is a one- or two-digit number. The number of the scratch directory indicates the machine on which the corresponding file system is mounted. Temporary directories are designated /tmpX, with the same convention. Although most of the file systems are cross mounted via nfs, it is generally preferable to run I/O intensive jobs on the machine on which the files being accessed are mounted locally, if possible.

Scratch Space Assignments

For the current list of scratch space assignments, see http://quake.stanford.edu/scratch_space.html

Working Space Mounts

0,1: flytrap
40-59: tarax

Requests for system accounts should be directed to Rick Bogart. Scratch disk space allocations are established and periodically reviewed by a committee consisting of Jim Aloise, Rick Bogart, Brian Roberts, and Jesper Schou.

This page last revised 15 August, 1996.

SSSC User's Guide - SOI home page