AFS/Directory Structure

General Conventions
Usually, if a mount point is read-only, then there will be another read-write mount point with the same name with dot in front of the name. For example, the mount point /afs/csl/service is read-only, but /afs/csl/.service is read-write. Both of those mount points are the same volume (service), but one is a read-only copy, and thus more likely to be available.

We also try to have volume names roughly correspond to where the volume is typically mounted in the directory tree, using dots as delimiters instead of slashes. For example, /afs/csl/service/matlab is a mount point to service.matlab, and /afs/csl/web/www is web.www. They do not have to completely correspond (volume names can only be so long), but they should be similar.

/afs/csl.tjhsst.edu/
This is the read-only mount point for root.cell for our cell. /afs/.csl.tjhsst.edu/ is the read-write mount point, and /afs/csl/ is a symlink to /afs/csl.tjhsst.edu/, and /afs/.csl/ is a symlink to /afs/.csl.tjhsst.edu/

archive/
This contains mountpoints for various volumes that are no longer used in day-to-day operations but that we want to continue to be accessible.

cronos/
All of the home directories before the lab switched to AFS (the old fileserver was called 'cronos', and served data with NFS). They are still around so that their web-docs are still available, so we do not break links.

i1/
Data files for the original Intranet.

legacy/
Deactivated websites are remounted here in subfolders corresponding to their old subdomain.

web.XXX/
These are various old versions of the main tjhsst.edu website.

common/
This contains shared directories for various groups and functions.

fcps/</tt>
Home directories for non-TJHSST FCPS students/staff. They are separated into sub-directories by site.

parents/</tt>
Home directories for parents; primarily webmasters.

staff/</tt>
Staff home directories for accounts that authenticate against the windows servers are stored here.

students/</tt>
Student home directories for accounts that authenticate against the windows servers are stored here, each separated by graduation year.

user/</tt>
Legacy user home directories from when CSL user accounts were separate from the rest of the school.

web/</tt>
Data for various web services. Almost all of the sub-directories here correspond to a subdomain http://&lt;directory&gt;.tjhsst.edu/.

sitemap/</tt>
Contains information for the sitemap for the legacy Krysalis system.

www/</tt>
Data files for the main website under the www subdomain. Other web subdomains (such as arts, activities, sports, etc.) also have their own directories in web/.

webadmin/</tt>
Data files for the webadmin application. See the webadmin article for information on the subdirectories here.

service/</tt>
Various administrative scripts and files are stored here.

sound/</tt>
Contains cron information and scripts to run the bell on the workstations at the appropriate times. The three directories are of different ages, and each was used at one point or another (music is really old, belltab holds the current crontab file, and sound holds the scripts).

httpd.intranet/</tt>
These are directories left over from when a few services ran with configuration files stored in AFS. However, these files are no longer used.

convert/</tt>
A set of scripts to convert the old non-AFS accounts to AFS ones, from the age when the lab was switching to AFS.

emperor_stuff/</tt>
A selection of files that were on emperor before the drives were replaced (HAA stuff and a few random scripts).

images/</tt>
Some data for experimental (now obsolete) workstation images is in here.

imaging/</tt>
Scripts and files for distributing files to workstations without imaging.

<tt>logs/</tt>
When log files start taking up too much space on a server's /var/log, the files were put here to free up space.

<tt>matlab/</tt>
Data for Matlab.

<tt>sysadmins/</tt>
More administrative scripts are in here. There's really not much distinction between these and the ones in service/; the separation is a legacy from previous years. These scripts are largely obsolete.

<tt>haa/</tt>
Scripts for the HAA system.

<tt>tokenizer/</tt>
A set of scripts to let daemons (such as apache for the website) gain permission to access AFS in their init.d scripts and refresh their credentials after a specified interval of time.