Warning Livedoc is no longer being updated and will be deprecated shortly. Please refer to https://documentation.tjhsst.edu.


From Livedoc - The Documentation Repository
Revision as of 22:42, 20 March 2006 by William Yang (talk | contribs)
Jump to: navigation, search

Apollo is currently being used for the Sun Ray (proprietary thin client) lab. This lab is currently used by all AP Computer Science classes, and before the 2004-05 school year, was used as a general-purpose computer lab. Apollo is one of the most reliable servers (any "crashes" were later found to actually have been user-induced and not related to hardware or the OS). The "sunracks" are currently in pre-production and are targeted to replace the loner Apollo with a more reliable, up-to-date (software), load-balanced, multi-server system.
Apollo is a Sun [Ultra] Enterprise 450.

Technical Specifications

Server Type Hardware type::
RAM 4096MiB
Hard Disks 4x Seagate Cheetah (10k RPM) 36GB UltraSCSI-3
  • 3 in use, 4th used for King partial backup (from the Crash)
OS Sun Solaris 9
Purchase Date


  • TODO:when was apollo obtained and how?
  • 2003-2004: Sun Ray/general-purpose computer lab
  • 2004-present: Sun Ray/all AP Computer Science classes


  • 2005-2006: Lee Burton (2007), Barnett Trzcinski (2007), William Yang (2008)
  • 2004-2005: Bryan Fleming (2005)
  • before 2004: Richard Washer (staff)

Power Outage Instructions

  • If at all possible, bring apollo down cleanly while its UPS's last since its filesystems are non-journaling! This means any unclean shutdown may require an extensive fsck after it is powered back on.


  • Users are discouraged from running anything processor-intensive unrelated to AP Computer Science during class since Apollo is already heavily loaded by being required to support ~20+ users running Java programs. So please save compiling applications (e.g. window managers) for off-hours, and avoid using load-demanding applications such as NetBeans (especially anything >4.1).
  • Apollo should be considered a mission-critical (within school hours) production system since all AP Computer Science classes rely on it on a daily basis. Therefore, no major system changes should be made to it in order to preserve stability.