MikesHiddenPage

This is a complex environment with many moving pieces.

• • • Get details from Jack on how he added me to the systems.

Pending Tickets

1544664 - All(?) RHEL6 machines (helike, eukelade, etc) affected by xorg crash

1559311 - Matlab crashes on fedora

1567328 - Add ece apps to launchers 1473459 - Setup add locker for Agilent Golden Gate 2011 1567330 - Delete old lockers for Xilinx 13.2 and setup new lockers for latest version 1568991 - Add locker for openCV

Big Projects

Audit kickstarts

Rework "add" system

Fix Condor

Improve monitoring

Misc Things

We default to tcsh because some parts of afs applications ("add" stuff?) break with bash. There is a contingent of folks who would like to see us move to BASH

---- jacorley: well most of the add initializations are done in tcsh scriptlets, which are obviously not bourne shell compatible 
---- acorley: well most of the add initializations are done in tcsh scriptlets, which are obviously not bourne shell compatible 
---- gsgatlin: well, we have an athena type system here that was originally built around cshell. so each locker has an initilization script that gets run by "add." Most ITECS created lockers (me) have a bash initilization also. Other lockers may be missing that piece.
---- jacorley: poke around lockers and look for dotfiles (.environment for tcsh IIRC, and .environmnet.sh for bash)gsgatlin: I created this web page that helps to explain it. But ignore references to Solaris 10. We have end of lifed that. http://techies.ncsu.edu/wiki/Addable_AFS_Locker
---- slack: msbelang: My advice is become familar with the systems with tcsh.  Once you understand the workings you can help us with the bash push

"add blah" is expected to be run in the shell session each time before you can use the software--there is no persistence.

print server is ece-print-01.ece.ncsu.edu

Kickstarting a System

1) MAC address gets magically associated with a hostname (probably not really magic) 2) Create a symlink in /afs/bp.ncsu.edu/system/config/linux-kickstart/configs/ece/computers to point at the correct kickstart 3) Boot system (ensuring it's not behind a firewall) 4) At "boot:" prompt, simply type the appropirate install type ("client6" for example) 5) Once the system has installed you can manually add users

Manually adding Users

- Local users: Add entry to /etc/users.local
- Remote users: Add entry to /etc/users.local.base
- Sudo users: visudo of course