Recent changes to this wiki:

Modified: trunk/index.mdwn
===================================================================
--- trunk/index.mdwn	2016-10-27 22:51:30 UTC (rev 414)
+++ trunk/index.mdwn	2016-10-27 22:54:13 UTC (rev 415)
@@ -12,8 +12,7 @@
 
 [[!sidebar content="""
 **If you need a new account**, please go to the
-[Account Request
-Form](http://acctreq.cms.caltech.edu/cgi-bin/request.cgi)"""]]
+[Account Request Form](http://acctreq.cms.caltech.edu/cgi-bin/request.cgi)"""]]
 
 
 


Modified: trunk/index.mdwn
===================================================================
--- trunk/index.mdwn	2016-07-19 22:08:20 UTC (rev 413)
+++ trunk/index.mdwn	2016-10-27 22:51:30 UTC (rev 414)
@@ -8,8 +8,7 @@
 
 You may also browse through the [Areas of Knowledge](AOK) to find what you are looking for.
 
-Finally, systems administrators may peruse the [sysadmin](sysadmin/index)-specific
-branch of the wiki.
+Finally, systems administrators may peruse the [sysadmin](sysadmin/index)-specific branch of the wiki.
 
 [[!sidebar content="""
 **If you need a new account**, please go to the


Adding doc to replace Maia Mailguard with CanIt Pro
Added: trunk/faq/can-it-pro-documentation.pdf
===================================================================
(Binary files differ)

Index: trunk/faq/can-it-pro-documentation.pdf
===================================================================
--- trunk/faq/can-it-pro-documentation.pdf	2012-10-05 17:39:53 UTC (rev 412)
+++ trunk/faq/can-it-pro-documentation.pdf	2016-07-19 22:08:20 UTC (rev 413)

Property changes on: trunk/faq/can-it-pro-documentation.pdf
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/pdf
\ No newline at end of property
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2012-10-05 17:39:53 UTC (rev 412)
+++ trunk/faq.mdwn	2016-07-19 22:08:20 UTC (rev 413)
@@ -161,7 +161,7 @@
 
 For detailed instructions on how to configure your mail, see these documents:
 
-[[Maia End User Documentation|Using-Maia-Mailguard-in-CMS.pdf]]  
+[[CanIt Pro End User Documentation|can-it-pro-documentation.pdf]]
 [[Thunderbird End User Documentation|Using-Thunderbird-in-CMS.pdf]]  
 
 ## How do I create a web page?


added mail forwarding instructions
Modified: trunk/NewUsers.mdwn
===================================================================
--- trunk/NewUsers.mdwn	2012-06-04 23:14:02 UTC (rev 411)
+++ trunk/NewUsers.mdwn	2012-10-05 17:39:53 UTC (rev 412)
@@ -7,7 +7,7 @@
 The following information will help you get the most out of your account here in CS, whether you use UNIX or Windows.
 When in doubt, you can find answers to most of your questions on this wiki, or in the [[FAQ]]s.
 
-If you have not read the acceptable use policy for the IMSS cluster, you should do so, the policies are [here]http://www.its.caltech.edu/its/help/policies/).
+If you have not read the acceptable use policy for the IMSS cluster, you should do so, the policies are [here](http://www.its.caltech.edu/its/help/policies/).
 If you have a newly created CS account, the account's temporary password is expired. You have a grace period of 7 days to log in and change your password.
 If you do not log in within 7 days (or you forget your temporary password, or you change your password and forget your new password) your account
 will be locked, and you will need to see the CS Systems Administrators in person to get your account unlocked.
@@ -37,6 +37,24 @@
 
 CS mail service assumes that your CS email address (username AT cs dot caltech dot edu) is **the end-point destination for your mail**.  If you do not intend to read your mail on the CS cluster, you need to forward your CS email to whatever destination address you use to typically read mail, whether that be your caltech.edu email address, your gmail.com address, etc.  If you don't forward your CS email, you won't get important department announcements such as building closures, lab closures, scheduled cluster outages, or your password expiration warnings.  See [[Email]] for more information on forwarding your CS email.
 
+To arrange a mail forward, you need to create a file called
+
+.forward
+
+in your CMS home directory.  To do this, you will need to be familiar with a command-line text editor such as [VI](http://www.lagmonster.org/docs/vi.html).  Log into a CMS workstation in the lab, or log into "login.cms.caltech.edu" remotely via ssh, and at a command prompt type:
+
+vi .forward
+
+VI will launch.  Hit the "I" key to switch to "edit" mode, and type the destination email address for your mail forward, e.g.:
+
+user@gmail.com
+
+Then hit the "Esc" key to exit editing mode, and then
+
+:wq
+
+To write the file.  You should then exit to the command prompt.  Test your email forward by sending yourself an email, and ensure that it winds up at your destination address.
+
 ### File Storage
 
 If you are using a UNIX account, your home directory is an NFS mount point. You should have no local files on any machine that you log into. Everything in your home directory is backed up on an hourly/daily/weekly/monthly basis. For more information on NFS, the filer, and quota structures, see the [[Storage]] section of the wiki.


Added backnet info (see ticket 500 in RT)
Modified: trunk/sysadmin/Operations.mdwn
===================================================================
--- trunk/sysadmin/Operations.mdwn	2012-02-28 21:57:37 UTC (rev 410)
+++ trunk/sysadmin/Operations.mdwn	2012-06-04 23:14:02 UTC (rev 411)
@@ -35,8 +35,31 @@
 With the exception of cabinet 1.3, which houses the critical infrastructure, none of these circuits is backed by uninterupptable power backup.  Cabinet 1.3 has an in-cabinet 12kW 60A UPS, which is described more fully below.
 
 ###Network###
+####Public Network####
 There are 144 public network drops in 1T1, which are supplied via a patch panel on the western wall which is tied into the building switchgear.  These 144 drops are currently on the 131.215.140.0/24 and 131.215.141.0/24 subnets, but all machines in 1T1 should be configured to operate on the 140 network, at which point the 141 overlay will be removed.  There is also a backnet in the server room, which supplies network connectivity to the Eaton Rack PDUs and Rittal Cabinet controllers for the purpose of monitoring and managing the physical power and colling infrastructure.
 
+####Private Network####
+There is a private network backnet in 1T1, originally for monitoring of the physical infrastructure.  This network is supported by two 48-port 100 mbs switches.  Currently, the configuration for the private network is as follows:
+
+Cabinet 1.1 is 10.1.1.0 - 10.1.1.255
+Cabinet 1.2 is 10.1.2.0 - 10.1.2.255
+Cabinet 1.3 is 10.1.3.0 - 10.1.3.255
+...
+Cabinet 2.1 is 10.2.1.0 - 10.2.1.255
+Cabinet 2.2 is 10.2.2.0 - 10.2.2.255
+...
+Cabinet 3.1 is 10.3.1.0 - 10.3.1.255
+
+Generally, a cabinet with the identifying number N.M will possess the private address space 10.N.M.1 - 10.N.M.255.
+
+For every cabinet (except 4.5, which has no LCP unit attached), the LCP unit is assigned the 254 address on the corresponding network.  Thus, the LCP numbered 3.1 is 10.3.1.254, the LCP numbered 4.3 is 10.4.3.254, etc.  The rack-mounted power distribution units have the .253 and (if applicable) the .252 address on their respective subnet.  
+
+Any host that is connected to the backnet in any given cabinet will thus be assigned an IP address in the range of 10.N.M.2 - 10.N.M.250, which allows us to reserve the 10.N.M.1 address for a gateway (if applicable in the future).
+
+The bastion host that access the backnet, in cabinet 1.3, will be 10.1.3.1
+
+Initially, all devices on the backnet will be on a single subnet, and thus use 255.255.0.0 as their broadcast address, with the bastion host serving as a gateway.
+
 The 1T1 room is described more fully in the attached documents:
 
 ###[[Operations/Construction Access List]]


creating index page sysadmin/tips
Added: trunk/sysadmin/tips.mdwn
===================================================================
--- trunk/sysadmin/tips.mdwn	                        (rev 0)
+++ trunk/sysadmin/tips.mdwn	2012-02-28 21:57:37 UTC (rev 410)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/tips/* and ! sysadmin/tips/*/*"]]


Added: trunk/sysadmin/tips/cudaonopensuse.mdwn
===================================================================
--- trunk/sysadmin/tips/cudaonopensuse.mdwn	                        (rev 0)
+++ trunk/sysadmin/tips/cudaonopensuse.mdwn	2012-02-28 21:57:34 UTC (rev 409)
@@ -0,0 +1,48 @@
+[Nvidia_CUDA](http://timelordz.com/wiki/Nvidia_CUDA) has relevant information concerning openSUSE 11.3.
+
+In essence:
+
+CUDA SDK 3.2 Update
+
+UPDATE I just did a fresh install of Suse 11.3 64-bit and the new CUDA SDK 3.2 and found the following issues:
+
+ * Unfortunately, the CUDA SDK 3.2 release notes do not include the same mention of the missing symlinks as do the 3.1 release notes. Follow the procedure in the 3.1 notes, which is also described below.
+ * While I had hoped the new CUDA SDK 3.2 would be compatible with gcc 4.5, it is not as described in this Nvidia Forum thread.
+You will still need to install and configure gcc43 and gcc43-g++ as alternatives as described below in the section GCC Version Issues.
+ * Several X11 development libraries are required. On Suse 11.3 install these and their dependencies with the following:
+
+    zypper install libXi6-devel libXmu-devel xorg-x11-libXmu-devel xorg-x11-libXext-devel
+
+For RHEL the packages are:
+
+    yum install libXi-devel libXmu-devel libXext-devel freeglut freeglut-devel
+
+Make Errors:
+The error:
+
+    86_64-suse-linux/bin/ld: cannot find -lX11
+
+Is caused from a missing xorg-x11-libXext-devel
+Errors like:
+
+    iomanip(64): error: expected an expression
+
+Are likely from using an incompatible version of gcc (like 4.5). This is best resolved by installed gcc43 as an alternative (below)
+or as described on the [Nvidia post](http://forums.nvidia.com/index.php?showtopic=183259):
+
+    A simple workaround to compiling the rest of the SDK would be to remove the folder Interval from the SDK's src folder
+and put it somewhere in your home directory where you will remember it later.
+
+    The complete list of programs that don't compile from the 3.2 SDK with GCC 4.5.1 are:
+    Interval
+    SobelFilter
+    FunctionPointers
+
+Errors regarding:
+
+    AC_PROG_LIBTOOL
+
+Can be solved by installing libtool
+The remaining setup for SDK 3.2 is as given for the previous version.
+
+


Modified: trunk/sysadmin/Tips.mdwn
===================================================================
--- trunk/sysadmin/Tips.mdwn	2012-02-09 20:43:02 UTC (rev 407)
+++ trunk/sysadmin/Tips.mdwn	2012-02-28 21:47:31 UTC (rev 408)
@@ -1,6 +1,7 @@
-
 [[Tips/AddingRPMsToOpenSUSE]] - How to create/edit a repository for openSUSE
 
+[[Tips/CUDAonOpenSUSE]] - How to install/configure CUDA onto a GPU box with openSUSE
+
 [[Tips/DualBootopenSUSEUSBInstaller]] - How we create a Dual-Arch openSUSE Installation from a USB stick
 
 [[Tips/EditingWikiPages]] - Editing Wiki pages via Subversion


Modified: trunk/AOK/VirtualMachine.mdwn
===================================================================
--- trunk/AOK/VirtualMachine.mdwn	2012-01-12 20:57:48 UTC (rev 406)
+++ trunk/AOK/VirtualMachine.mdwn	2012-02-09 20:43:02 UTC (rev 407)
@@ -22,3 +22,8 @@
 TEMUJIN        |pki          |EJBCA        |PRILICIA
 SUBOTAI        |rtweb        |RT           |PRILICIA
 """]]
+
+We are slowly replacing Xen with KVM.
+Some documentation:
+<http://doc.opensuse.org/documentation/html/openSUSE/opensuse-kvm/index.html>
+


Modified: trunk/GettingHelp.mdwn
===================================================================
--- trunk/GettingHelp.mdwn	2012-01-12 20:56:53 UTC (rev 405)
+++ trunk/GettingHelp.mdwn	2012-01-12 20:57:48 UTC (rev 406)
@@ -1,4 +1,4 @@
-Send mail to help(AT)cs.caltech.edu for questions, and help-d(AT)cs.caltech.edu for discussions
+Send mail to help(AT)cms.caltech.edu for questions, and help-d(AT)cms.caltech.edu for discussions
 
 * David Le Blanc is our full-time system administrator handling Unix and central systems.
  * David's office is Annenberg 112.


Modified: trunk/GettingHelp.mdwn
===================================================================
--- trunk/GettingHelp.mdwn	2011-12-02 18:53:04 UTC (rev 404)
+++ trunk/GettingHelp.mdwn	2012-01-12 20:56:53 UTC (rev 405)
@@ -2,13 +2,10 @@
 
 * David Le Blanc is our full-time system administrator handling Unix and central systems.
  * David's office is Annenberg 112.
-    * David's office Phone is: (626) 395-2402
-    * David's pager is: (909) 740-3535
-    * David's pager email address: pager_leblancd(AT)caltech.edu
+ * David's office Phone is: (626) 395-2402
 
 * Patrick Cahalan is our full-time system administrator handling Windows systems.
  * Patrick's office is Annenberg 112.
  * Patrick's office Phone is: (626) 395-3290
- * Patrick's pager is: (626) 473-8862 
 
 Please use the help@cs list as any requests there are logged so there is less of a chance a request will simply be forgotten.


HASH(0x2f34a10)
Modified: trunk/sysadmin/Projects/.htaccess
===================================================================
--- trunk/sysadmin/Projects/.htaccess	2011-12-02 18:30:35 UTC (rev 403)
+++ trunk/sysadmin/Projects/.htaccess	2011-12-02 18:53:04 UTC (rev 404)
@@ -1,4 +1,4 @@
 # Deny from off-campus
-Order deny,allow
-Deny from allow
-Allow from caltech.edu
+order deny,allow
+deny from all
+allow from .caltech.edu


adding .htaccess to Projects
Added: trunk/sysadmin/Projects/.htaccess
===================================================================
--- trunk/sysadmin/Projects/.htaccess	                        (rev 0)
+++ trunk/sysadmin/Projects/.htaccess	2011-12-02 18:30:35 UTC (rev 403)
@@ -0,0 +1,4 @@
+# Deny from off-campus
+Order deny,allow
+Deny from allow
+Allow from caltech.edu


updated Account Request Form
Modified: trunk/index.mdwn
===================================================================
--- trunk/index.mdwn	2011-08-03 20:51:36 UTC (rev 401)
+++ trunk/index.mdwn	2011-11-22 00:36:46 UTC (rev 402)
@@ -14,7 +14,7 @@
 [[!sidebar content="""
 **If you need a new account**, please go to the
 [Account Request
-Form](http://www.cs.caltech.edu/cgi-bin/sysadmin/account_request.cgi)"""]]
+Form](http://acctreq.cms.caltech.edu/cgi-bin/request.cgi)"""]]
 
 
 


Added basic description of server room.
Modified: trunk/sysadmin/Operations.mdwn
===================================================================
--- trunk/sysadmin/Operations.mdwn	2011-08-02 06:51:35 UTC (rev 400)
+++ trunk/sysadmin/Operations.mdwn	2011-08-03 20:51:36 UTC (rev 401)
@@ -17,8 +17,28 @@
 
 The CMS systems administration team is located in 112 Annenberg.
 
-The 1T1 room is described in the following sections:
+###Design Considerations###
+The Annenberg Server Room was designed based upon the historical usage of compute resources by the (then-CS) CMS faculty, projected out to 2025 using the EPA's projected guideline for future power consumption trends.  Barring a cutover to DC power supplies or some other major change in rackmounted server power supplies, this represents a conservative but fiscally responsible baseline for the first 15 years of occupation of the building by the department.  Any major computing effort that exceeds the design parameters of the room will have to be accomodated elsewhere on campus.
 
+###Cooling###
+The server room is supplied by a large (8") chilled water feed that enters the Annenberg building at grade on the north side of the building near the auditorium, travels up into the ceiling at that point, cuts across the northern hallway and into the janitorial closet (1J1), where it drops below the floor and enters the server room.  The emergency shut-off valves for this chilled water pipe are located in 1J1; in the event of a catastropic failure of pipe integrity, the shutoff valves must be engaged in that room.  The key to the janitorial closet is located in 112 Annenberg.
+
+The server room consists of four rows of 5 self-enclosed cabinets with internal cooling sidecars manufactured by Rittal corporation, sharing a common plenum.  One of the four rows has four cooling units, the remaining three rows have five cooling units.  The row with four cooling units has a capacity of approximately 22kW per cabinet, the rows with five cooling units have a capacity of approximately 28kW per cabinet.  Since the rows share a common plenum, it is possible to exceed the base capacity as long as the other cabinets in the row are under the top capacity and the differential is not so great as to impact the airflow in the over-subscribed cabinet.  In any event, it is not expected that CMS will reach heat load capacity in any cabinet in the immediate future.
+
+There is also an in-room CRAC unit for comfort cooling, a Leibert unit that is supplied by the main chilled water feed.
+
+###Power###
+The server room is supplied power via a dedicated 750kVA transformer (T2) in the Main Electrical room (room 1E2, first floor Annenberg, south-east corner of the building).  Access to this room is restricted to campus facilities, in the event of an emergency call x4717.  In the Main Electrical room, there are feeds to the server room which connect to the large electrical panel in the southeast corner of the server room.
+
+There are four outgoing circuits from that room, which attach to the wall-mounted step-down Emerson PDUs (1, 2, and 3) and the in-room CRAC unit.  Essentially, each PDU receives 225kVA @ 480A, where it is stepped-down to the 208 circuits that are connected to the individual power strips (the Eaton Rack PDUs described more fully below) in each cabinet.
+
+With the exception of cabinet 1.3, which houses the critical infrastructure, none of these circuits is backed by uninterupptable power backup.  Cabinet 1.3 has an in-cabinet 12kW 60A UPS, which is described more fully below.
+
+###Network###
+There are 144 public network drops in 1T1, which are supplied via a patch panel on the western wall which is tied into the building switchgear.  These 144 drops are currently on the 131.215.140.0/24 and 131.215.141.0/24 subnets, but all machines in 1T1 should be configured to operate on the 140 network, at which point the 141 overlay will be removed.  There is also a backnet in the server room, which supplies network connectivity to the Eaton Rack PDUs and Rittal Cabinet controllers for the purpose of monitoring and managing the physical power and colling infrastructure.
+
+The 1T1 room is described more fully in the attached documents:
+
 ###[[Operations/Construction Access List]]
 ###*[[Operations/Power Outages]]*
 ###[[Operations/Liebert CRAC Unit]]


Modified: trunk/sysadmin/Tips/openSUSESchedule.mdwn
===================================================================
--- trunk/sysadmin/Tips/openSUSESchedule.mdwn	2011-07-15 16:11:41 UTC (rev 399)
+++ trunk/sysadmin/Tips/openSUSESchedule.mdwn	2011-08-02 06:51:35 UTC (rev 400)
@@ -7,6 +7,10 @@
     * security updates for all included packages
     * critical bugfix updates (usually these are found & fixed in the first few months of its lifetime)
 
-openSUSE 11.3 is due to be released July 15, 2010.
+openSUSE **12.1** is due to be released **November 11, 2011**.
 
+openSUSE **11.4** was released Marh 10, 2011 and **EOL is September 15, 2012**.
+
+openSUSE **11.3** was released July 15, 2010 and **EOL is January 15, 2012**.
+
 openSUSE 11.2 EOL is May 12, 2011.


Checking in the file I added but forgot to check in...
Added: trunk/AOK/Windows.mdwn
===================================================================
--- trunk/AOK/Windows.mdwn	                        (rev 0)
+++ trunk/AOK/Windows.mdwn	2011-07-15 16:11:41 UTC (rev 399)
@@ -0,0 +1,34 @@
+The Windows domain (hereinafter CD-AD) was deployed in 2003 to replace the historical NT4 domain "CS-NT" and an alternative graduate-student deployed "GEMS-NT" domain which was a stripped down Active Directory deployment.
+
+CS-AD currently runs as an Active Directory 2000 domain, running on two Windows 2003 Server installations in Windows 2000 native mode.  We are scheduled to migrate to 2008 in the winter of 2011, but this migration may happen prior, time permitting.
+
+###Infrastructure
+
+Currently, the infrastructure for CS-AD consists of four servers:
+
+ - hammer.cs.caltech.edu, the operations master, infrastructure master, and PDC
+ - anvil.cs.caltech.edu, the SDC
+ - forge.cs.caltech.edu, the print server and file server for the software repository
+ - workshop.cs.caltech.edu, the terminal server
+
+####Common Infrastructure Issues
+
+Occasionally, after a critical update, the domain controllers get slightly out of sync.  The File Replication Service may report errors.  Users will report that they get the error message "Unable to contact CS-AD".  To resolve this, simply log into both domain controllers, reboot one and after it is back online reboot the other.
+
+###Domain Security Policy
+
+The DSP has been modified from the default for a number of reasons.  These changes will be listed here:
+
+####Inherited Policy Bug
+
+The Domain Security Policy does not include password aging, but some user passwords still age.  This has been investigated in the past and likely causes have been elimited.  Best guess is that this is an artifact of the merger of the NT4 domain CS-NT and the half-built GEMS-NT Windows 2000 domain into the CS-AD infrastructure.
+
+####Workstation Security Policy
+
+In addition to the inherited Domain Security Policy, there are the following steps taken at the workstation level.
+ - Remote Assistance is turned off
+ - Remote Desktop connection is turned on
+ - Firewall rules prevent RD from outside the 140-143 net by default
+ - Users are granted Administrator access if they request it
+
+


Modified: trunk/AOK/HTC.mdwn
===================================================================
--- trunk/AOK/HTC.mdwn	2011-06-08 08:36:33 UTC (rev 396)
+++ trunk/AOK/HTC.mdwn	2011-06-08 08:37:43 UTC (rev 397)
@@ -1,6 +1,6 @@
 ## High-Throughput Computing (HTC)
 
-[[!toc]]
+[[!toc startlevel=3]]
 
 ### Introduction
 


Modified: trunk/sysadmin/Projects.mdwn
===================================================================
--- trunk/sysadmin/Projects.mdwn	2011-06-08 01:18:40 UTC (rev 395)
+++ trunk/sysadmin/Projects.mdwn	2011-06-08 08:36:33 UTC (rev 396)
@@ -7,7 +7,7 @@
  *in beta testing*
 
 [[Projects/CondorHTC]]  
- *in alpha testing*
+ *in beta testing*
 
 [[Projects/CMSFileSystemQuota]]   
  *planning*


HASH(0x2f380f0)
Modified: trunk/AOK/HTC.mdwn
===================================================================
--- trunk/AOK/HTC.mdwn	2011-06-08 08:37:43 UTC (rev 397)
+++ trunk/AOK/HTC.mdwn	2011-06-08 01:36:12 UTC (rev 398)
@@ -166,9 +166,9 @@
 
 #### Inspecting Machine ClassAds with `condor_status`
 
-Try the condor_status command to get a summary of information from
+Try the `condor_status` command to get a summary of information from
 ClassAds about the resources available in your pool. Type
-condor_status and hit enter to see a summary similar to the following:
+`condor_status` and hit enter to see a summary similar to the following:
 
     Name               OpSys      Arch   State     Activity LoadAv Mem   ActvtyTime
 
@@ -481,7 +481,7 @@
 
     fib 40
 
-##### Matlab Jobs
+### Matlab Jobs
 
 ***Introduction***
 


HASH(0x2f3b888)
Modified: trunk/AOK/HTC.mdwn
===================================================================
--- trunk/AOK/HTC.mdwn	2011-06-08 01:08:01 UTC (rev 394)
+++ trunk/AOK/HTC.mdwn	2011-06-08 01:18:40 UTC (rev 395)
@@ -1,5 +1,7 @@
 ## High-Throughput Computing (HTC)
 
+[[!toc]]
+
 ### Introduction
 
 For many research and engineering projects, the quality of the
@@ -105,6 +107,15 @@
 migrated the job is started over from the beginning after migration is
 complete.
 
+### Condor in CMS
+
+Currently, the only supported Condor HTC pool is in the ANN 104 lab,
+and LOGIN.CMS.CALTECH.EDU.  You may freely submit jobs from any ANN
+104 machine as well as LOGIN.CMS, however LOGIN.CMS is not an
+**execute** host as submitted jobs will run on idle machines in the
+ANN 104 lab.  Any of the below commands or procedures can be followed
+only within the CMS Condor Pool.
+
 ### How to Use Condor
 
 #### Matchmaking with ClassAds
@@ -673,7 +684,7 @@
     ------------------------------------------
     Setting up environment variables
     ---
-    LD_LIBRARY_PATH is .:/opt/matlab/runtime/glnx86:/opt/matlab/bin/glnx86:/opt/matlab/sys/os/glnx86:/opt/matlab/sys/java/jre/glnx86/jre/lib/i386/native_threads:/opt/matlab/sys/java/jre/glnx86/jre/lib/i386/server:/opt/matlab/sys/java/jre/glnx86/jre/lib/i386/client:/opt/matlab/sys/java/jre/glnx86/jre/lib/i386
+    LD_LIBRARY_PATH is .:/opt/matlab/sys/java/jre/glnx86/jre/lib/i386/client:/opt/matlab/sys/java/jre/glnx86/jre/lib/i386
     Warning: No display specified.  You will not be able to display graphics on the screen.
 
     C =


HASH(0x2f3bcc0)
Modified: trunk/AOK/HTC.mdwn
===================================================================
--- trunk/AOK/HTC.mdwn	2011-05-27 23:05:30 UTC (rev 393)
+++ trunk/AOK/HTC.mdwn	2011-06-08 01:08:01 UTC (rev 394)
@@ -600,8 +600,24 @@
 libraries/binaries in order to execute the compiled function.
 
 Additionally, you could also submit the 'mcc -mv product.m' process as
-a Condor job.
+a Condor job to compile the M-file into an executable.
+An example of a Condor job to compile `product.m` with a submission
+script named `build_product.submit`:
 
+    universe = vanilla
+    executable = /opt/matlab/bin/mcc
+    arguments = "-mv product.m"
+    output = build_product.out
+    error = build_product.err
+    log = build_product.log
+    queue
+
+And then submitting the Condor job with `condor_submit
+build_product.submit`.  The arguments for `mcc`, "-mv product.m",
+state to compile the file `product.m` verbosely (`-mv`)..  This
+produces two files, aside from the Condor output:  `product` and
+`run_product.sh`.
+
 Note that before using the compiler for the first time it needs to be
 configured using:
 
@@ -614,16 +630,19 @@
 be used:
 
     universe = vanilla
-	executable = run_product.sh /opt/matlab 
+	executable = run_product.sh
+	arguments = "/opt/matlab 10"
 	output = product$(PROCESS).out
 	log = product$(PROCESS).log
 	error = product$(PROCESS).err
 	notification = Error
-	queue 10
+	queue
 
-The $(PROCESS) macro takes on the values 0:9 for different Condor
-processes run in the pool so that each receives one input file and the
-corresponding output files are returned to the Condor submit host.
+The `10` value in the arguments line is passed along to the
+`run_product.sh` script, and consequently also passed to the `product`
+compiled executable.
+The $(PROCESS) macro takes on the values of the Condor Job Process ID
+(typically zero for single-queued jobs).
 The input and output file lists can be modified to suit other
 applications. For production runs, the output files should always be
 specified just in case there is a run-time problem and they are not
@@ -637,10 +656,10 @@
     condor_q -held
 
 Once the jobs have been completed, the directory should contain ten
-output files named *output0.mat*, *output1.mat* ... *output9.mat*
+output files named *outputN.mat*, *output1.mat* ... *output9.mat*
 which can then be processed using *collect.m* to generate the final
-result.  There will also be ten log files (*.log), ten stdout files
-(*.out) and ten error files (*.err).  These are largely insignificant
+result.  There will also be one log file (*.log), one stdout files
+(*.out) and one error files (*.err).  These are largely insignificant
 if everything goes according to expectation, but can be used to track
 problems when things have gone unexpectedly.
 
@@ -648,3 +667,43 @@
 with matrices of order n=4000, a serial implementation requires
 approximately 90 minutes of time whereas the Condor system requires on
 the order of 10 minutes.
+
+Finally, the output of our final MATLAB example process, `collect`:
+  
+    ------------------------------------------
+    Setting up environment variables
+    ---
+    LD_LIBRARY_PATH is .:/opt/matlab/runtime/glnx86:/opt/matlab/bin/glnx86:/opt/matlab/sys/os/glnx86:/opt/matlab/sys/java/jre/glnx86/jre/lib/i386/native_threads:/opt/matlab/sys/java/jre/glnx86/jre/lib/i386/server:/opt/matlab/sys/java/jre/glnx86/jre/lib/i386/client:/opt/matlab/sys/java/jre/glnx86/jre/lib/i386
+    Warning: No display specified.  You will not be able to display graphics on the screen.
+
+    C =
+        0.5276    0.2963
+        0.6619    0.7518
+    C =
+        1.5206    1.0850
+        2.0565    1.6617
+    C =
+        1.8254    2.1830
+        2.6913    3.3354
+    C =
+        2.3975    2.6859
+        3.2551    3.8829
+    C =
+        2.6208    2.9524
+        3.5483    3.9551
+    C =
+        3.0777    3.6426
+        4.0091    4.6391
+    C =
+        3.5873    3.8646
+        4.6140    5.0676
+    C =
+        4.4576    4.7594
+        4.9268    5.3963
+    C =
+        4.7315    5.6475
+        5.1057    6.2381
+    C =
+        5.1249    6.5890
+        5.2415    6.5537
+


added some windows/mac docs
Modified: trunk/sysadmin/Automated_Installation.mdwn
===================================================================
--- trunk/sysadmin/Automated_Installation.mdwn	2011-05-26 06:46:16 UTC (rev 392)
+++ trunk/sysadmin/Automated_Installation.mdwn	2011-05-27 23:05:30 UTC (rev 393)
@@ -62,3 +62,19 @@
 [Installation instructions](linux_install) for OpenSUSE
 are in the form of an AutoYaST XML file, editable with any text editor,
 and maintained in a version control repository.
+
+####Windows
+The current default Windows image is based upon Windows XP-64 bit.  This was chosen to support the widest range of possible hardware configurations inside a single base image; both large-memory machines (>4GB) and simultaneously older machines that have a lower-end performance rating and thus may not run an alternative version of Windows (e.g., Windows 7).  It is likely that the deparment will switch over to Windows 7 as the base image prior to the 2011-2012 scholastic year.
+
+The base image is built on the hardware platform used in the instructional lab (Dell Precision 390s), which also matches the hardware platform used by the Administrative staff.  Once the base installation is created, an image is made using Norton Ghost.  Customized versions are built for both the Administrative staff (containing administrative-specific software such as Oracle) and the basic Lab image (containing development tools).
+
+The current image file for the adminstaff is pre-390-admin-2011.gho (a 26GB image file).  The current image file for the academic lab is pre-390-base-lab-2010-fall.gho (a 52GB image file).  These files are currently located on a external USB drive (labled "GHOST"), and the local hard drive of kirk.cms.caltech.edu.  When ACM's archival files are removed from the filer, a copy will be located on the osimage volume.
+
+To install the image, you will need a Ghost bootable CD.  The non-network copy of this .iso image also exists on the GHOST USB drive, filename "ghost-boot-no-net.iso".  Burn a copy of this to a CD, attach the USB drive to the machine to be reinstalled, and boot the machine from the CD.  At the Ghost options screen, choose to install a local disk from an image, and browse to the USB drive and select the appropriate image.  The network installation using Ghost has not been re-enabled since the move from Jorgensen, due to the complications of having three subnets in Annenberg and our inability to run our own DHCP.
+
+After the machine has been installed, using the base image, additional drivers may be necessary if the machine is not a precision 390; typically these can be installed easily using the Dell support site.  The machine, post-install, will need to be configured to use its new hostname and static IP address, and will need to be added to the CS-AD domain to get the default security policy.  This requires knowledge of the CD-AD administrator password.  Note: the machine will be basically operational without joining it to the domain at this point, and thus can be used with a local account if necessary.
+
+####Mac OSX
+The current default Macintosh image is based upon MacOSX, 10.6.  The image file was built on a 13" Macbook Pro but according to IMSS knowledgebase should work on all Intel-based Macintoshes with no modifications.  
+
+The file "Mac-2010-2011-research.dmg" on the "GHOST" USB drive is the current image file for Mac OSX machines.  Note: in order to be installed via the disk imaging process, this file must exist on a HFS-formatted volume.  There is currently a USB key that can be used for this process, but the "GHOST" USB drive itself (being NTFS), cannot be used to image a Mac machine.


Modified: trunk/sysadmin/index.mdwn
===================================================================
--- trunk/sysadmin/index.mdwn	2011-05-26 06:43:31 UTC (rev 391)
+++ trunk/sysadmin/index.mdwn	2011-05-26 06:46:16 UTC (rev 392)
@@ -4,7 +4,7 @@
 
 ###[[History]]
 ###[[Methodology]]
-###[[Disaster Recovery]]
+###[Disaster Recovery](Operations/Continuity_Plan)
 ###[[Operations]]
 ###[[Configuration]]
 ###[[Projects]]


Modified: trunk/sysadmin/Disaster_Recovery.mdwn
===================================================================
--- trunk/sysadmin/Disaster_Recovery.mdwn	2011-05-25 23:34:45 UTC (rev 390)
+++ trunk/sysadmin/Disaster_Recovery.mdwn	2011-05-26 06:43:31 UTC (rev 391)
@@ -1,3 +1,3 @@
 This section will contain descriptions necessary to the recovery after an unscheduled outage, or worse, a disaster.
 
-see [Continuity Plan](Operations/Continuity_Plan/CMS-Continuity-of-Ops-Plan.docx)
+see [[Operations/Continuity Plan]]


Modified: trunk/sysadmin/Disaster_Recovery.mdwn
===================================================================
--- trunk/sysadmin/Disaster_Recovery.mdwn	2011-05-26 06:35:40 UTC (rev 388)
+++ trunk/sysadmin/Disaster_Recovery.mdwn	2011-05-26 06:39:19 UTC (rev 389)
@@ -1,3 +1,3 @@
 This section will contain descriptions necessary to the recovery after an unscheduled outage, or worse, a disaster.
 
-see [Operations/Continuity_Plan/CMS-Continuity-of-Ops-Plan.docx](Continuity Plan)
+see [Continuity Plan](Operations/Continuity_Plan/CMS-Continuity-of-Ops-Plan.docx)


creating index page sysadmin/Operations/Quotes_and_Invoices
Added: trunk/sysadmin/Operations/Quotes_and_Invoices.mdwn
===================================================================
--- trunk/sysadmin/Operations/Quotes_and_Invoices.mdwn	                        (rev 0)
+++ trunk/sysadmin/Operations/Quotes_and_Invoices.mdwn	2011-05-26 06:35:40 UTC (rev 387)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/Operations/Quotes_and_Invoices/* and ! sysadmin/Operations/Quotes_and_Invoices/*/*"]]


creating index page sysadmin/Operations/Continuity_Plan
Added: trunk/sysadmin/Operations/Continuity_Plan.mdwn
===================================================================
--- trunk/sysadmin/Operations/Continuity_Plan.mdwn	                        (rev 0)
+++ trunk/sysadmin/Operations/Continuity_Plan.mdwn	2011-05-26 06:35:40 UTC (rev 388)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/Operations/Continuity_Plan/* and ! sysadmin/Operations/Continuity_Plan/*/*"]]


Added: trunk/sysadmin/disaster_recovery.mdwn
===================================================================
--- trunk/sysadmin/disaster_recovery.mdwn	                        (rev 0)
+++ trunk/sysadmin/disaster_recovery.mdwn	2011-05-26 06:23:35 UTC (rev 385)
@@ -0,0 +1 @@
+This section will contain descriptions necessary to the recovery after an unscheduled outage, or worse, a disaster.


HASH(0x2f432c0)
Modified: trunk/AOK/HTC.mdwn
===================================================================
--- trunk/AOK/HTC.mdwn	2011-05-26 06:39:19 UTC (rev 389)
+++ trunk/AOK/HTC.mdwn	2011-05-25 23:34:45 UTC (rev 390)
@@ -514,7 +514,7 @@
 in paralllel, consider the case where we want to form the sum of p
 matrix-matrix products, i.e. calculate C where:
 
-[[!img pmatrix1.png align="left"]]
+[[!img HTC/pmatrix1.png align="left"]]
 
 
 and A, B, and C are square matrices of order n. It is easy to see that
@@ -532,9 +532,10 @@
 
     function initialize(n)
 	  n = str2num(n);
-      for i = 0:n
-        A=rand(i,i);
-        B=rand(i,i);
+      for i = 1:n
+	    index = i;
+        A=rand(2,2)
+        B=rand(2,2)
         filename=strcat('input',int2str(i));
         save( filename, 'A', 'B', 'index');
     end
@@ -541,25 +542,22 @@
 
 The elements of A and B are given random initial values and are saved
 to files using the Matlab 'save' command. Condor needs the input files
-to be indexed from 0:p-1 so the above code generates ten input files
-named input0.mat, input1.mat .. input9.mat. The M-file also saves the
-index variable to file as this will be needed by the Condor job. This
-M-file can be run on the Sun UNIX service or the Condor server (which
-also has Matlab available) to generate the inputs prior to submitting
-the Condor job. 
+to be indexed from 1:p-1 so the above code generates 'n' input files
+named input1.mat, input2.mat ... inputn.mat. The M-file also saves the
+index variable to file as this will be needed by the Condor job.
 
 The second script will need to form the matrix-matrix products and
-will eventuall be run as a standalone application.  A suitable M-file,
+will be run as a standalone application.  A suitable M-file,
 `product.m` is:
 
     function product(n)
 	  n = str2num(n);
-	  for i = 0:n
+	  for i = 1:n
         filenameI = strcat( 'input', int2str( i ) );
         load( filenameI );
-        C=A*B;
-        filenameO = strcat( 'output', int2str( index ) );
-        save( filenameO, 'C' );
+        S = A * B
+        filenameO = strcat( 'output', int2str( i ) );
+        save( filenameO, 'S' );
 	  end
 
 Note that the function name must be the same as the M-file name (minus
@@ -566,15 +564,9 @@
 the extension). 
 
 Since the same executable is used for each parallel Condor job, the
-job will not know the specific input filename it has to deal with. The
-DOS 'rename' command (issued using Matlab's 'system' command) is
-therefore used to rename the input file prior to the data being loaded
-(note that the index is not known at this stage). Once the matrices
-have been loaded and the product formed, the output is written to
-file. The index is used to give the file an unique name and ensures
-that the output files are named output0.mat, output1.mat, ..
-output9.mat corresponding to the inputs input0.mat, input1.mat, ..
-input9.mat. 
+job will not know the specific input filename it has to deal with.
+Once the matrices have been loaded and the product formed, the output
+is written to file.
 
 The final step is to collect all of the output files together to form
 the sum. This can be achieved using another M-file `collect.m` such as
@@ -582,15 +574,15 @@
 
     function collect(n)
 	  n = str2num(n);
-      S = zeros(i,i);
-      for i = 0:n
+      C = zeros(2);
+      for i = 1:n
         filename = strcat( 'output', int2str( i ) );
         load( filename );
-        S=S+C
-    end
+        C = C + S
+      end
 
 This loads each output file in turn and forms the sum of the
-matrix-matrix products in the S variable. 
+matrix-matrix products in the C variable. 
 
 ***Creating the standalone application***
 
@@ -622,7 +614,7 @@
 be used:
 
     universe = vanilla
-	executable = run_product.sh /opt/matlab
+	executable = run_product.sh /opt/matlab 
 	output = product$(PROCESS).out
 	log = product$(PROCESS).log
 	error = product$(PROCESS).err


HASH(0x2f45d50)
Copied: trunk/sysadmin/Disaster_Recovery.mdwn (from rev 385, trunk/sysadmin/disaster_recovery.mdwn)
===================================================================
--- trunk/sysadmin/Disaster_Recovery.mdwn	                        (rev 0)
+++ trunk/sysadmin/Disaster_Recovery.mdwn	2011-05-25 23:29:13 UTC (rev 386)
@@ -0,0 +1,3 @@
+This section will contain descriptions necessary to the recovery after an unscheduled outage, or worse, a disaster.
+
+see [Operations/Continuity_Plan/CMS-Continuity-of-Ops-Plan.docx](Continuity Plan)

Copied: trunk/sysadmin/Operations/Continuity_Plan/CMS-Continuity-of-Ops-Plan.docx (from rev 385, trunk/sysadmin/Documentation/CMS-Continuity-of-Ops-Plan.docx)
===================================================================
(Binary files differ)

Copied: trunk/sysadmin/Operations/Quotes_and_Invoices/CIT-08-10-23-T50e_Options-CO.pdf (from rev 385, trunk/sysadmin/Documentation/CIT-08-10-23-T50e_Options-CO.pdf)
===================================================================
(Binary files differ)

Copied: trunk/sysadmin/Operations/Quotes_and_Invoices/CIT-08-10-29-FAS2050HA-FAS2050-CO.pdf (from rev 385, trunk/sysadmin/Documentation/CIT-08-10-29-FAS2050HA-FAS2050-CO.pdf)
===================================================================
(Binary files differ)

Copied: trunk/sysadmin/Operations/Quotes_and_Invoices/price-quote-atempo-renewal-2010.pdf (from rev 385, trunk/sysadmin/Documentation/price-quote-atempo-renewal-2010.pdf)
===================================================================
(Binary files differ)


adding price quote for Atempo renewal
Added: trunk/sysadmin/Documentation/price-quote-atempo-renewal-2010.pdf
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Documentation/price-quote-atempo-renewal-2010.pdf
===================================================================
--- trunk/sysadmin/Documentation/price-quote-atempo-renewal-2010.pdf	2011-05-25 23:11:29 UTC (rev 383)
+++ trunk/sysadmin/Documentation/price-quote-atempo-renewal-2010.pdf	2011-05-25 23:11:49 UTC (rev 384)

Property changes on: trunk/sysadmin/Documentation/price-quote-atempo-renewal-2010.pdf
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property

adding continuity of operations plan
Added: trunk/sysadmin/Documentation/CMS-Continuity-of-Ops-Plan.docx
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Documentation/CMS-Continuity-of-Ops-Plan.docx
===================================================================
--- trunk/sysadmin/Documentation/CMS-Continuity-of-Ops-Plan.docx	2011-05-25 23:11:11 UTC (rev 382)
+++ trunk/sysadmin/Documentation/CMS-Continuity-of-Ops-Plan.docx	2011-05-25 23:11:29 UTC (rev 383)

Property changes on: trunk/sysadmin/Documentation/CMS-Continuity-of-Ops-Plan.docx
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property

added our response to EAS internal audit
Added: trunk/sysadmin/Documentation/EAS Computing Environment Questionnaire.docx
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Documentation/EAS Computing Environment Questionnaire.docx
===================================================================
--- trunk/sysadmin/Documentation/EAS Computing Environment Questionnaire.docx	2011-05-25 23:10:50 UTC (rev 381)
+++ trunk/sysadmin/Documentation/EAS Computing Environment Questionnaire.docx	2011-05-25 23:11:11 UTC (rev 382)

Property changes on: trunk/sysadmin/Documentation/EAS Computing Environment Questionnaire.docx
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property

adding the filer quote
Added: trunk/sysadmin/Documentation/CIT-08-10-29-FAS2050HA-FAS2050-CO.pdf
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Documentation/CIT-08-10-29-FAS2050HA-FAS2050-CO.pdf
===================================================================
--- trunk/sysadmin/Documentation/CIT-08-10-29-FAS2050HA-FAS2050-CO.pdf	2011-05-25 23:10:34 UTC (rev 380)
+++ trunk/sysadmin/Documentation/CIT-08-10-29-FAS2050HA-FAS2050-CO.pdf	2011-05-25 23:10:50 UTC (rev 381)

Property changes on: trunk/sysadmin/Documentation/CIT-08-10-29-FAS2050HA-FAS2050-CO.pdf
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property

adding the tape library quote
Added: trunk/sysadmin/Documentation/CIT-08-10-23-T50e_Options-CO.pdf
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Documentation/CIT-08-10-23-T50e_Options-CO.pdf
===================================================================
--- trunk/sysadmin/Documentation/CIT-08-10-23-T50e_Options-CO.pdf	2011-05-24 22:02:01 UTC (rev 379)
+++ trunk/sysadmin/Documentation/CIT-08-10-23-T50e_Options-CO.pdf	2011-05-25 23:10:34 UTC (rev 380)

Property changes on: trunk/sysadmin/Documentation/CIT-08-10-23-T50e_Options-CO.pdf
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property

HASH(0x2f4f4b8)
Modified: trunk/AOK/HTC.mdwn
===================================================================
--- trunk/AOK/HTC.mdwn	2011-05-21 06:49:08 UTC (rev 378)
+++ trunk/AOK/HTC.mdwn	2011-05-24 22:02:01 UTC (rev 379)
@@ -516,6 +516,143 @@
 
 [[!img pmatrix1.png align="left"]]
 
+
 and A, B, and C are square matrices of order n. It is easy to see that
 the p matrix products could be calculated independently and therefor
 potentially in parallel.
+
+In the first step we need to store A and B to Matlab data files which
+can be distributed by Condor for processing. Each Condor job will then
+need to read A and B from file, form the product AB and write the
+output to another Condor data file. The final step will sum all of the
+partial sums read from the output files to form the complete sum C.
+
+The first step can be accomplished using an M-file similar to 
+`initialize.m`:
+
+    function initialize(n)
+	  n = str2num(n);
+      for i = 0:n
+        A=rand(i,i);
+        B=rand(i,i);
+        filename=strcat('input',int2str(i));
+        save( filename, 'A', 'B', 'index');
+    end
+
+The elements of A and B are given random initial values and are saved
+to files using the Matlab 'save' command. Condor needs the input files
+to be indexed from 0:p-1 so the above code generates ten input files
+named input0.mat, input1.mat .. input9.mat. The M-file also saves the
+index variable to file as this will be needed by the Condor job. This
+M-file can be run on the Sun UNIX service or the Condor server (which
+also has Matlab available) to generate the inputs prior to submitting
+the Condor job. 
+
+The second script will need to form the matrix-matrix products and
+will eventuall be run as a standalone application.  A suitable M-file,
+`product.m` is:
+
+    function product(n)
+	  n = str2num(n);
+	  for i = 0:n
+        filenameI = strcat( 'input', int2str( i ) );
+        load( filenameI );
+        C=A*B;
+        filenameO = strcat( 'output', int2str( index ) );
+        save( filenameO, 'C' );
+	  end
+
+Note that the function name must be the same as the M-file name (minus
+the extension). 
+
+Since the same executable is used for each parallel Condor job, the
+job will not know the specific input filename it has to deal with. The
+DOS 'rename' command (issued using Matlab's 'system' command) is
+therefore used to rename the input file prior to the data being loaded
+(note that the index is not known at this stage). Once the matrices
+have been loaded and the product formed, the output is written to
+file. The index is used to give the file an unique name and ensures
+that the output files are named output0.mat, output1.mat, ..
+output9.mat corresponding to the inputs input0.mat, input1.mat, ..
+input9.mat. 
+
+The final step is to collect all of the output files together to form
+the sum. This can be achieved using another M-file `collect.m` such as
+this: 
+
+    function collect(n)
+	  n = str2num(n);
+      S = zeros(i,i);
+      for i = 0:n
+        filename = strcat( 'output', int2str( i ) );
+        load( filename );
+        S=S+C
+    end
+
+This loads each output file in turn and forms the sum of the
+matrix-matrix products in the S variable. 
+
+***Creating the standalone application***
+
+As indicated earlier, the M-file used by the Condor job needs to be
+compiled into a standalone application.
+
+    mcc -mv product.m
+
+If the main M-file calls other functions stored in different M-files
+then these should be listed after the main M-file. Alternatively the
+-a option can be used to specify the directory they are held in. 
+The mcc MATLAB compiler will create runtime shell executables of the
+form `run_<function>.sh` where <function> is the name of the function
+and original binary such that MATLAB can load any dependant
+libraries/binaries in order to execute the compiled function.
+
+Additionally, you could also submit the 'mcc -mv product.m' process as
+a Condor job.
+
+Note that before using the compiler for the first time it needs to be
+configured using:
+
+  mbuild -setup
+
+***Creating the Condor files***
+
+Each Condor job needs a submission file to describe how the job should
+be run. For this example a submission file such as the one below can
+be used:
+
+    universe = vanilla
+	executable = run_product.sh /opt/matlab
+	output = product$(PROCESS).out
+	log = product$(PROCESS).log
+	error = product$(PROCESS).err
+	notification = Error
+	queue 10
+
+The $(PROCESS) macro takes on the values 0:9 for different Condor
+processes run in the pool so that each receives one input file and the
+corresponding output files are returned to the Condor submit host.
+The input and output file lists can be modified to suit other
+applications. For production runs, the output files should always be
+specified just in case there is a run-time problem and they are not
+created.  In this case, Condor will place tje job in the held ('H')
+state.  To release these jobs and run them elsewhere, use:
+
+    condor_release -all
+
+To find out why jobs have been held, use:
+
+    condor_q -held
+
+Once the jobs have been completed, the directory should contain ten
+output files named *output0.mat*, *output1.mat* ... *output9.mat*
+which can then be processed using *collect.m* to generate the final
+result.  There will also be ten log files (*.log), ten stdout files
+(*.out) and ten error files (*.err).  These are largely insignificant
+if everything goes according to expectation, but can be used to track
+problems when things have gone unexpectedly.
+
+This is a rather simplified example, however, as a rough benchmark
+with matrices of order n=4000, a serial implementation requires
+approximately 90 minutes of time whereas the Condor system requires on
+the order of 10 minutes.


Modified: trunk/AOK/HTC.mdwn
===================================================================
--- trunk/AOK/HTC.mdwn	2011-05-21 06:48:23 UTC (rev 377)
+++ trunk/AOK/HTC.mdwn	2011-05-21 06:49:08 UTC (rev 378)
@@ -514,7 +514,7 @@
 in paralllel, consider the case where we want to form the sum of p
 matrix-matrix products, i.e. calculate C where:
 
-[[pmatrix1.png]]
+[[!img pmatrix1.png align="left"]]
 
 and A, B, and C are square matrices of order n. It is easy to see that
 the p matrix products could be calculated independently and therefor


attachment upload
Added: trunk/AOK/HTC/pmatrix1.png
===================================================================
(Binary files differ)

Index: trunk/AOK/HTC/pmatrix1.png
===================================================================
--- trunk/AOK/HTC/pmatrix1.png	2011-05-21 06:48:01 UTC (rev 376)
+++ trunk/AOK/HTC/pmatrix1.png	2011-05-21 06:48:23 UTC (rev 377)

Property changes on: trunk/AOK/HTC/pmatrix1.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property

creating index page AOK/pmatrix1.png
Added: trunk/AOK/pmatrix1.png.mdwn
===================================================================
--- trunk/AOK/pmatrix1.png.mdwn	                        (rev 0)
+++ trunk/AOK/pmatrix1.png.mdwn	2011-05-21 06:48:01 UTC (rev 376)
@@ -0,0 +1 @@
+[[!map pages="AOK/pmatrix1.png/* and ! AOK/pmatrix1.png/*/*"]]


attachment upload
Added: trunk/AOK/pmatrix1.png/pmatrix1.png
===================================================================
(Binary files differ)

Index: trunk/AOK/pmatrix1.png/pmatrix1.png
===================================================================
--- trunk/AOK/pmatrix1.png/pmatrix1.png	2011-05-20 23:40:53 UTC (rev 374)
+++ trunk/AOK/pmatrix1.png/pmatrix1.png	2011-05-21 06:47:59 UTC (rev 375)

Property changes on: trunk/AOK/pmatrix1.png/pmatrix1.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property

HASH(0x2f553c8)
Modified: trunk/AOK/HTC.mdwn
===================================================================
--- trunk/AOK/HTC.mdwn	2011-05-20 23:15:27 UTC (rev 373)
+++ trunk/AOK/HTC.mdwn	2011-05-20 23:40:53 UTC (rev 374)
@@ -514,8 +514,7 @@
 in paralllel, consider the case where we want to form the sum of p
 matrix-matrix products, i.e. calculate C where:
 
-  $$C = \sum_{i=1}^{p} A_iB_i
-  $$
+[[pmatrix1.png]]
 
 and A, B, and C are square matrices of order n. It is easy to see that
 the p matrix products could be calculated independently and therefor


HASH(0x2f57ae0)
Added: trunk/AOK/HTC.mdwn
===================================================================
--- trunk/AOK/HTC.mdwn	                        (rev 0)
+++ trunk/AOK/HTC.mdwn	2011-05-20 23:15:27 UTC (rev 373)
@@ -0,0 +1,522 @@
+## High-Throughput Computing (HTC)
+
+### Introduction
+
+For many research and engineering projects, the quality of the
+research or the product is heavily dependent upon the quantity of
+computing cycles available. It is not uncommon to find problems that
+require weeks or months of computation to solve. Scientists and
+engineers engaged in this sort of work need a computing environment
+that delivers large amounts of computational power over a long period
+of time. Such an environment is called a High-Throughput Computing
+(HTC) environment. In contrast, High Performance Computing (HPC)
+environments deliver a tremendous amount of compute power over a short
+period of time. HPC environments are often measured in terms of
+FLoating point Operations Per Second (FLOPS). A growing community is
+not concerned about operations per second, but operations per month or
+per year. Their problems are of a much larger scale. They are more
+interested in how many jobs they can complete over a long period of
+time instead of how fast an individual job can complete.
+
+The key to HTC is to efficiently harness the use of all available
+resources. Years ago, the engineering and scientific community relied
+on a large, centralized mainframe or a supercomputer to do
+computational work. A large number of individuals and groups needed to
+pool their financial resources to afford such a machine. Users had to
+wait for their turn on the mainframe, and they had a limited amount of
+time allocated. While this environment was inconvenient for users, the
+utilization of the mainframe was high; it was busy nearly all the
+time.
+
+As computers became smaller, faster, and cheaper, users moved away
+from centralized mainframes and purchased personal desktop
+workstations and PCs. An individual or small group could afford a
+computing resource that was available whenever they wanted it. The
+personal computer is slower than the large centralized machine, but it
+provides exclusive access. Now, instead of one giant computer for a
+large institution, there may be hundreds or thousands of personal
+computers. This is an environment of distributed ownership, where
+individuals throughout an organization own their own resources. The
+total computational power of the institution as a whole may rise
+dramatically as the result of such a change, but because of
+distributed ownership, individuals have not been able to capitalize on
+the institutional growth of computing power. And, while distributed
+ownership is more convenient for the users, the utilization of the
+computing power is lower. Many personal desktop machines sit idle for
+very long periods of time while their owners are busy doing other
+things (such as being away at lunch, in meetings, or at home
+sleeping). 
+
+Such is the case for many computer workstations in Annenberg, and
+throughout the CMS Department.
+
+Condor is a software system that creates a High-Throughput Computing
+(HTC) environment. It effectively utilizes the computing power of
+workstations that communicate over a network. Condor can manage a
+dedicated cluster of workstations. Its power comes from the ability to
+effectively harness non-dedicated, preexisting resources under
+distributed ownership.
+
+A user submits the job to Condor. Condor finds an available machine on
+the network and begins running the job on that machine. Condor has the
+capability to detect that a machine running a Condor job is no longer
+available (perhaps because the owner of the machine came back from
+lunch and started typing on the keyboard).
+
+Condor can be a real time saver when a job must be run many (hundreds
+of) different times, perhaps with hundreds of different data sets.
+With one command, all of the hundreds of jobs are submitted to Condor.
+Depending upon the number of machines in the Condor pool, dozens or
+even hundreds of otherwise idle machines can be running the job at any
+given moment. 
+
+Condor provides powerful resource management by match-making resource
+owners with resource consumers. This is the cornerstone of a
+successful HTC environment. Other compute cluster resource management
+systems attach properties to the job queues themselves, resulting in
+user confusion over which queue to use as well as administrative
+hassle in constantly adding and editing queue properties to satisfy
+user demands. Condor implements ClassAds, a clean design that
+simplifies the user's submission of jobs.
+
+ClassAds work in a fashion similar to the newspaper classified
+advertising want-ads. All machines in the Condor pool advertise their
+resource properties, both static and dynamic, such as available RAM
+memory, CPU type, CPU speed, virtual memory size, physical location,
+and current load average, in a resource offer ad. A user specifies a
+resource request ad when submitting a job. The request defines both
+the required and a desired set of properties of the resource to run
+the job. Condor acts as a broker by matching and ranking resource
+offer ads with resource request ads, making certain that all
+requirements in both ads are satisfied. During this match-making
+process, Condor also considers several layers of priority values: the
+priority the user assigned to the resource request ad, the priority of
+the user which submitted the ad, and desire of machines in the pool to
+accept certain types of ads over others. 
+
+### Limitations
+
+Condor imposes several limitations on jobs in the context of
+*checkpointing* -- allowing a running program to be frozen, migrated
+to another resource, and restarted from the point it left off --
+however, Condor in the CMS Department was not built with support for
+checkpointing, so those limitations do not apply.  Therefore, the main
+limitation in Annenberg is that when a running job needs to be
+migrated the job is started over from the beginning after migration is
+complete.
+
+### How to Use Condor
+
+#### Matchmaking with ClassAds
+
+Before you learn about how to submit a job, it is important to
+understand how Condor allocates resources. Understanding the unique
+framework by which Condor matches submitted jobs with machines is the
+key to getting the most from Condor's scheduling algorithm.
+
+Condor simplifies job submission by acting as a matchmaker of
+ClassAds. Condor's ClassAds are analogous to the classified
+advertising section of the newspaper. Sellers advertise specifics
+about what they have to sell, hoping to attract a buyer. Buyers may
+advertise specifics about what they wish to purchase. Both buyers and
+sellers list constraints that need to be satisfied. For instance, a
+buyer has a maximum spending limit, and a seller requires a minimum
+purchase price. Furthermore, both want to rank requests to their own
+advantage. Certainly a seller would rank one offer of $50 dollars
+higher than a different offer of $25. In Condor, users submitting jobs
+can be thought of as buyers of compute resources and machine owners
+are sellers.
+
+All machines in a Condor pool advertise their attributes, such as
+available memory, CPU type and speed, virtual memory size, current
+load average, along with other static and dynamic properties. This
+machine ClassAd also advertises under what conditions it is willing to
+run a Condor job and what type of job it would prefer. These policy
+attributes can reflect the individual terms and preferences by which
+all the different owners have graciously allowed their machine to be
+part of the Condor pool. You may advertise that your machine is only
+willing to run jobs at night and when there is no keyboard activity on
+your machine. In addition, you may advertise a preference (rank) for
+running jobs submitted by you or one of your co-workers.
+
+Likewise, when submitting a job, you specify a ClassAd with your
+requirements and preferences. The ClassAd includes the type of machine
+you wish to use. For instance, perhaps you are looking for the fastest
+floating point performance available. You want Condor to rank
+available machines based upon floating point performance. Or, perhaps
+you care only that the machine has a minimum of 128 Mbytes of RAM. Or,
+perhaps you will take any machine you can get! These job attributes
+and requirements are bundled up into a job ClassAd.
+
+Condor plays the role of a matchmaker by continuously reading all the
+job ClassAds and all the machine ClassAds, matching and ranking job
+ads with machine ads. Condor makes certain that all requirements in
+both ClassAds are satisfied.
+
+#### Inspecting Machine ClassAds with `condor_status`
+
+Try the condor_status command to get a summary of information from
+ClassAds about the resources available in your pool. Type
+condor_status and hit enter to see a summary similar to the following:
+
+    Name               OpSys      Arch   State     Activity LoadAv Mem   ActvtyTime
+
+    slot1@arquebus.cms LINUX      INTEL  Claimed   Busy     0.000  1971  0+07:15:14
+    slot2@arquebus.cms LINUX      INTEL  Claimed   Busy     0.000  1971  0+07:15:15
+    slot1@ballista.cms LINUX      INTEL  Unclaimed Idle     0.000  1971  0+03:55:05
+    slot2@ballista.cms LINUX      INTEL  Unclaimed Idle     0.000  1971  0+15:45:23
+    slot1@bardiche.cms LINUX      INTEL  Owner     Idle     0.000  1971  0+00:55:06
+    slot2@bardiche.cms LINUX      INTEL  Claimed   Busy     0.000  1971  0+00:55:07
+    slot1@cadence.cms. LINUX      INTEL  Owner     Idle     0.050  1744  0+00:40:04
+    slot2@cadence.cms. LINUX      INTEL  Owner     Idle     0.000  1744  0+00:40:05
+
+The `condor_status` command has options that summarize machine ads in a variet of ways.
+For example,
+
+***condor_status -available***
+
+   shows only machines which are willing to run jobs now.
+
+***condor_status -run***
+
+   shows only machines which are currently running jobs.
+
+***condor_status -l***
+
+   lists the machine ClassAds for all machines in the pool.
+
+Below shows the complete machine ClassAd for a single workstation: `arquebus.cms.caltech.edu`.
+Some of the listed attributes are used by Condor for scheduling. Other attributes are for
+information purposes. An important point is that **any** of the attributes in a machine ad
+can be utilized at job submission time as part of a request or preference on
+what machine to use.  Additional attributes can be easily added.  For example, your
+system administrator can add a physical location attribute to your machine ClassAds.
+
+    Machine = "arquebus.cms.caltech.edu"

(Diff truncated)
Modified: trunk/sysadmin/Projects/CondorHTC.mdwn
===================================================================
--- trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-18 08:02:05 UTC (rev 371)
+++ trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-18 08:03:20 UTC (rev 372)
@@ -12,10 +12,10 @@
 
 Current configuration:
 
- - CONSTANTINE (LOGIN.CMS) is MASTER, COLLECTOR, NEGOTIATOR (the "central manager")
- - CONSTANTINE (LOGIN.CMS) is MASTER, SCHEDULER (the "submission node")
- - ALL ANN 104 Lab machines are MASTER, STARTD ("submission node")
- - ALL ANN 104 Lab machines are MASTER, STARTD (EXECUTE node)
+ - CONSTANTINE (LOGIN.CMS) is COLLECTOR, NEGOTIATOR (the "central manager")
+ - CONSTANTINE (LOGIN.CMS) is SCHEDULER (the "submission node")
+ - ALL ANN 104 Lab machines are SCHEDULER ("submission node")
+ - ALL ANN 104 Lab machines are STARTD (EXECUTE node)
 
 In this configuration, a job may be submitted on any EXECUTE node, or LOGIN.CMS, and LOGIN.CMS is the manager of the Condor pool.
 


Modified: trunk/sysadmin/Projects/CondorHTC.mdwn
===================================================================
--- trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-18 08:00:46 UTC (rev 370)
+++ trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-18 08:02:05 UTC (rev 371)
@@ -49,6 +49,8 @@
  - **Killing** : Killing means that the machine has requested the running job to exit the machine immediately, without checkpointing.
 
 
+Further documentation can be found [here](http://www.cs.wisc.edu/condor/manual/v7.6/Contents.html).
+
 ### May 13, 2011 13:30
 Resuming testing after upgrading version/build
 


Modified: trunk/sysadmin/Projects/CondorHTC.mdwn
===================================================================
--- trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-14 06:23:38 UTC (rev 369)
+++ trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-18 08:00:46 UTC (rev 370)
@@ -7,6 +7,48 @@
  - Tools to monitor pool health
 """]]
 
+### May 17, 2011 17:35
+CMS Condor pool is now operational.
+
+Current configuration:
+
+ - CONSTANTINE (LOGIN.CMS) is MASTER, COLLECTOR, NEGOTIATOR (the "central manager")
+ - CONSTANTINE (LOGIN.CMS) is MASTER, SCHEDULER (the "submission node")
+ - ALL ANN 104 Lab machines are MASTER, STARTD ("submission node")
+ - ALL ANN 104 Lab machines are MASTER, STARTD (EXECUTE node)
+
+In this configuration, a job may be submitted on any EXECUTE node, or LOGIN.CMS, and LOGIN.CMS is the manager of the Condor pool.
+
+`condor_status` displays the status of the pool similar to:
+
+    Name               OpSys      Arch   State     Activity LoadAv Mem   ActvtyTime
+    slot1@arquebus.cms LINUX      INTEL  Owner     Idle     0.780  1971  0+00:00:04
+    slot2@arquebus.cms LINUX      INTEL  Unclaimed Idle     0.750  1971  0+00:00:13
+
+Multi-core/CPU machines will have slot1..slotN.
+
+The ***State*** column indicates:
+
+ - ***Unclaimed*** --- The machine is available to run Condor jobs, but it is not currently doing so.
+ - ***Owner*** --- The machine is being used by the machine owner, and/or is not available to run Condor jobs. When the machine first starts up, it begins in this state. After a period of inactivity of 15 minutes, the state will change to ***Unclaimed***.
+ - ***Claimed*** --- The machine has been claimed by a schedd.
+ - ***Matched*** --- The machine is available to run jobs, and it has been matched by the negotiator with a specific schedd. That schedd just has not yet claimed this machine. In this state, the machine is unavailable for further matches. 
+ - ***Preempting*** --- The machine was claimed by a schedd, but is now preempting that claim for one of the following reasons.
+   - the owner of the machine came back 
+   - another user with higher priority has jobs waiting to run
+   - another request that this resource would rather serve was found
+
+**Activity**
+
+ - **Idle** : the machine is experiencing no Condor activity at all, typically due to **State** being either **Owner** or **Unclaimed**.
+ - **Busy** : Once a condor_starter has been started and the claim is active, the machine moves to the Busy activity to signify that it is doing something as far as Condor is concerned.
+ - **Suspending** : If the job is suspended by Condor, the machine goes into the Suspended activity. The match between the schedd and machine has not been broken (the claim is still valid), but the job is not making any progress and Condor is no longer generating a load on the machine. A typical case would be when a Condor job is already running, but there is recent keyboard/mouse activity.
+ - **Retiring** : When an active claim is about to be preempted for any reason, it enters retirement, while it waits for the current job to finish. The MaxJobRetirementTime expression determines how long to wait (counting since the time the job started). Once the job finishes or the retirement time expires, the Preempting state is entered.
+ - **Preempting** : The preempting state is used for evicting a Condor job from a given machine.
+ - **Vacating** : In the Vacating activity, the job that was running is in the process of checkpointing. As soon as the checkpoint process completes, the machine moves into either the Owner state or the Claimed state, depending on the reason for its preemption.
+ - **Killing** : Killing means that the machine has requested the running job to exit the machine immediately, without checkpointing.
+
+
 ### May 13, 2011 13:30
 Resuming testing after upgrading version/build
 


Modified: trunk/sysadmin/Projects/CondorHTC.mdwn
===================================================================
--- trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-14 04:02:17 UTC (rev 368)
+++ trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-14 06:23:38 UTC (rev 369)
@@ -23,7 +23,7 @@
 
  - `condor_config.local` is configured to read `/dev/condor_mouse`, so envokation of `condor_read_mouse` is
  - `/usr/bin/condor_read_mouse /dev/input/mice /dev/condor_mouse`
- - "condor_read_mouse" "input device" "update-file"
+ - "condor-read-mouse" "input device" "update-file"
 
 ### July 27, 2010, 15:30
 Idle keyboard/mouse testing has concluded successfully.


Modified: trunk/sysadmin/Projects/CondorHTC.mdwn
===================================================================
--- trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-14 03:58:31 UTC (rev 367)
+++ trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-14 04:02:17 UTC (rev 368)
@@ -23,7 +23,7 @@
 
  - `condor_config.local` is configured to read `/dev/condor_mouse`, so envokation of `condor_read_mouse` is
  - `/usr/bin/condor_read_mouse /dev/input/mice /dev/condor_mouse`
- - <condor_read_mouse> <input device> <update-file>
+ - "condor_read_mouse" "input device" "update-file"
 
 ### July 27, 2010, 15:30
 Idle keyboard/mouse testing has concluded successfully.


Modified: trunk/sysadmin/Projects/CondorHTC.mdwn
===================================================================
--- trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-07 05:06:25 UTC (rev 366)
+++ trunk/sysadmin/Projects/CondorHTC.mdwn	2011-05-14 03:58:31 UTC (rev 367)
@@ -5,9 +5,26 @@
 **ToDo**:
 
  - Tools to monitor pool health
- - Checkpointing
 """]]
 
+### May 13, 2011 13:30
+Resuming testing after upgrading version/build
+
+New config:
+
+ - DAEMON is MASTER, **COLLECTOR, NEGOTIATOR** (the "central manager")
+ - CADENCE is MASTER, **SCHEDULER** (the "submission node")
+ - SABRE is MASTER, **STARTD** (**EXECUTE** node)
+ - KERIS is MASTER, **STARTD** (**EXECUTE** node)
+
+The launch of `condor_read_mouse` is manual only at this time, as it was not patched into `init.d/condor` in the RPM package yet.
+
+Usage for `condor_read_mouse`:
+
+ - `condor_config.local` is configured to read `/dev/condor_mouse`, so envokation of `condor_read_mouse` is
+ - `/usr/bin/condor_read_mouse /dev/input/mice /dev/condor_mouse`
+ - <condor_read_mouse> <input device> <update-file>
+
 ### July 27, 2010, 15:30
 Idle keyboard/mouse testing has concluded successfully.
 


creating tag page tag/migration
Added: trunk/tag/migration.mdwn
===================================================================
--- trunk/tag/migration.mdwn	                        (rev 0)
+++ trunk/tag/migration.mdwn	2011-05-07 05:06:25 UTC (rev 366)
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged migration"]]
+
+[[!inline pages="tagged(migration)" actions="no" archive="yes"
+feedshow=10]]


Modified: trunk/sysadmin/Projects/CMSEmail.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail.mdwn	2011-05-07 05:04:24 UTC (rev 363)
+++ trunk/sysadmin/Projects/CMSEmail.mdwn	2011-05-07 05:05:39 UTC (rev 364)
@@ -1,6 +1,6 @@
 [[!tag email]]
 [[!sidebar content="""
-Project Status: **Beta**"""]]
+Project Status: **Completed**"""]]
 
 ## CMS Email
 


Modified: trunk/sysadmin/Projects.mdwn
===================================================================
--- trunk/sysadmin/Projects.mdwn	2011-05-06 21:56:24 UTC (rev 362)
+++ trunk/sysadmin/Projects.mdwn	2011-05-07 05:04:24 UTC (rev 363)
@@ -1,6 +1,6 @@
 ##Ongoing projects within CMS
 
-[[Projects/CDSMigration]]
+[[Projects/CDSMigration]]  
  *in planning*
 
 [[Projects/Collaborators]]  


HASH(0x2f611a8)
Added: trunk/sysadmin/Projects/CDSMigration.mdwn
===================================================================
--- trunk/sysadmin/Projects/CDSMigration.mdwn	                        (rev 0)
+++ trunk/sysadmin/Projects/CDSMigration.mdwn	2011-05-06 22:00:09 UTC (rev 365)
@@ -0,0 +1,4 @@
+[[!tag migration]]
+
+[[!sidebar content="""
+Project Status: **Planning**"""]]


HASH(0x2f62048)
Modified: trunk/sysadmin/Projects.mdwn
===================================================================
--- trunk/sysadmin/Projects.mdwn	2011-04-21 00:39:22 UTC (rev 361)
+++ trunk/sysadmin/Projects.mdwn	2011-05-06 21:56:24 UTC (rev 362)
@@ -1,7 +1,7 @@
 ##Ongoing projects within CMS
 
-[[Projects/CMSEmail]]  
-   *awaiting migration from CS -> CMS*
+[[Projects/CDSMigration]]
+ *in planning*
 
 [[Projects/Collaborators]]  
  *in beta testing*
@@ -22,6 +22,9 @@
 
 ##Completed projects
 
+[[Projects/CMSEmail]]  
+ completed
+
 [[Projects/OpenNMS]]  
  completed
 


Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-04-21 00:37:57 UTC (rev 360)
+++ trunk/faq.mdwn	2011-04-21 00:39:22 UTC (rev 361)
@@ -184,7 +184,7 @@
 where "user" is your CMS username. You may optionally name "AuthName" anything you like.
 
 NOTE:  This password protects the directory and all sub-directories below where the `.htaccess` file is located.
-To protect *specific files* instead, replace the "Require" directory above with:
+To protect *specific files* instead, replace the "Require" directive above with:
 
     <Files "filename.html">
       Require valid-user
@@ -198,7 +198,8 @@
 
   NOTE:  the `-c` parameter specifies to CREATE the file, so if the file exists, it will be rewritten and truncated, eliminating any existing usernames/passwords.
 
-Finally, make the two files, `.htaccess` and `.htpasswd`, group-accessible to the 'www' group so that the web server may read them.  Remove world-read/write bits on the files as well, with:
+Finally, make the two files, `.htaccess` and `.htpasswd`, group-accessible to the 'www' group so that the web server may read them.
+Remove world-read/write bits on the files as well, with:
 
     chgrp www .htaccess
     chgrp www .htpasswd


Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-04-20 23:27:24 UTC (rev 359)
+++ trunk/faq.mdwn	2011-04-21 00:37:57 UTC (rev 360)
@@ -172,43 +172,38 @@
 
 First, you need to be aware that http://users.cms.caltech.edu is not encrypted and any passwords involved **should not** be related to your normal CMS password(s) because the passwords involved will be sent as clear plain text.
 
-  To password-protect a directory (in `~/public_html`, or `http://users.cms.caltech.edu/~user`):
+To password-protect a directory (in `~/public_html`, or `http://users.cms.caltech.edu/~user`):
 
-  1. Create a file named `.htaccess` that contains:
+Create a file named `.htaccess` that contains:
 
     AuthUserFile /home/user/public_html/.htpasswd
-	AuthType Basic
-	AuthName "User's Secrets"
-	Require valid-user
+    AuthType Basic
+    AuthName "User's Secrets"
+    Require valid-user
 
-  where "user" is your CMS username. You may optionally name "AuthName" anything you like.
+where "user" is your CMS username. You may optionally name "AuthName" anything you like.
 
-  NOTE:  This password protects the directory and all sub-directories
-  below where the `.htaccess` file is located. To protect *specific
-  files* instead, replace the "Require" directory above with:
+NOTE:  This password protects the directory and all sub-directories below where the `.htaccess` file is located.
+To protect *specific files* instead, replace the "Require" directory above with:
 
     <Files "filename.html">
       Require valid-user
     </Files>
 
-  2. Create the .htpasswd file by envoking (on LOGIN.CMS):
+Next, create the .htpasswd file by envoking (on LOGIN.CMS):
 
     htpasswd2 -c [the location in "AuthUserFile"] username
 
-  where "username" is the username allowed access after
-  authentication.  The above command will prompt you for a password
-  (twice, to confirm).
+where "username" is the username allowed access after authentication.  The above command will prompt you for a password (twice, to confirm).
 
   NOTE:  the `-c` parameter specifies to CREATE the file, so if the file exists, it will be rewritten and truncated, eliminating any existing usernames/passwords.
 
-  3. Finally, make the two files, `.htaccess` and `.htpasswd`,
-  group-accessible to the 'www' group so that the web server may read
-  them.  Remove world-read/write bits on the files as well, with:
+Finally, make the two files, `.htaccess` and `.htpasswd`, group-accessible to the 'www' group so that the web server may read them.  Remove world-read/write bits on the files as well, with:
 
     chgrp www .htaccess
     chgrp www .htpasswd
-	chmod o-rwx .htaccess
-	chmod o-rwx .htpasswd
+    chmod o-rwx .htaccess
+    chmod o-rwx .htpasswd
 
 ## How do I print directly to the printers?
 


added "how to password-protect webpages"
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-04-12 23:25:05 UTC (rev 358)
+++ trunk/faq.mdwn	2011-04-20 23:27:24 UTC (rev 359)
@@ -168,6 +168,48 @@
 
 By default, every user is allowed to host a web page (within the bounds of their quota) on the CMS users site.  To do this, create a folder called public\_html in your home directory, and ensure that the folder is world-readable and executable.  Then any files you place in ~/username/public_html" will be visible at http://users.cms.caltech.edu/~username
 
+## How do I password-protect my web page?
+
+First, you need to be aware that http://users.cms.caltech.edu is not encrypted and any passwords involved **should not** be related to your normal CMS password(s) because the passwords involved will be sent as clear plain text.
+
+  To password-protect a directory (in `~/public_html`, or `http://users.cms.caltech.edu/~user`):
+
+  1. Create a file named `.htaccess` that contains:
+
+    AuthUserFile /home/user/public_html/.htpasswd
+	AuthType Basic
+	AuthName "User's Secrets"
+	Require valid-user
+
+  where "user" is your CMS username. You may optionally name "AuthName" anything you like.
+
+  NOTE:  This password protects the directory and all sub-directories
+  below where the `.htaccess` file is located. To protect *specific
+  files* instead, replace the "Require" directory above with:
+
+    <Files "filename.html">
+      Require valid-user
+    </Files>
+
+  2. Create the .htpasswd file by envoking (on LOGIN.CMS):
+
+    htpasswd2 -c [the location in "AuthUserFile"] username
+
+  where "username" is the username allowed access after
+  authentication.  The above command will prompt you for a password
+  (twice, to confirm).
+
+  NOTE:  the `-c` parameter specifies to CREATE the file, so if the file exists, it will be rewritten and truncated, eliminating any existing usernames/passwords.
+
+  3. Finally, make the two files, `.htaccess` and `.htpasswd`,
+  group-accessible to the 'www' group so that the web server may read
+  them.  Remove world-read/write bits on the files as well, with:
+
+    chgrp www .htaccess
+    chgrp www .htpasswd
+	chmod o-rwx .htaccess
+	chmod o-rwx .htpasswd
+
 ## How do I print directly to the printers?
 
 You should only ever print directly to the printer if you have a networked printer that is not for general use (such as a research group's color printer) or a printer that you can physically monitor. Never print a large print job directly to a printer without first checking with other users who may be using a print queue.


Modified: trunk/sysadmin/Projects/Collaborators.mdwn
===================================================================
--- trunk/sysadmin/Projects/Collaborators.mdwn	2011-04-12 05:45:13 UTC (rev 357)
+++ trunk/sysadmin/Projects/Collaborators.mdwn	2011-04-12 23:25:05 UTC (rev 358)
@@ -2,13 +2,17 @@
 
 [[!sidebar content="""
 Project Status: **Beta**
+"""]]
 
-**ToDo**:
+### 12 APR 2011, 13:10
+Server now **forces** SSL.
 
- - SSL to protect passwords SVN -> HTTP
- - Figure out logging
- - Figure out how to monitor"""]]
+Implementation of Apache2 on openSUSE customizes error messages such that the operator can create gee-whiz nice-looking Error pages.
 
+This implementation was concealing actual Subversion error messages such that the SVN errors would be mangled with custom Apache error messages, `Can't open file '/srv/repos/svn/error/format'`.  There is no such file, of course because `error` in this case is actually supposed to be the name of the repository.
+
+By commenting out the custom error page implementation, the actual Subversion error was exposed, which consisted of `Can't get exclusive lock on file`, supposedly because some part of the Apache/DAV/SVN stack glitched, causing an operation to not succeed, leaving the `write-lock` file in the repository.  Deleting the `write-lock` file fixed the Subversion error.
+
 ### 11 APR 2011, 21:35
 Rebuilt on openSUSE 11.3
 Config is as follows:


Modified: trunk/sysadmin/Projects/Collaborators.mdwn
===================================================================
--- trunk/sysadmin/Projects/Collaborators.mdwn	2011-04-04 21:14:08 UTC (rev 356)
+++ trunk/sysadmin/Projects/Collaborators.mdwn	2011-04-12 05:45:13 UTC (rev 357)
@@ -5,10 +5,93 @@
 
 **ToDo**:
 
- - Test with groups
+ - SSL to protect passwords SVN -> HTTP
  - Figure out logging
  - Figure out how to monitor"""]]
 
+### 11 APR 2011, 21:35
+Rebuilt on openSUSE 11.3
+Config is as follows:
+
+    <Directory "/srv/repos">
+        Options         +Indexes +Multiviews +FollowSymLinks
+        IndexOptions    FancyIndexing \
+                        ScanHTMLTitles \
+                        NameWidth=* \
+                        DescriptionWidth=*
+        order allow,deny
+        allow from all
+    </Directory>
+
+    LDAPSharedCacheSize     200000
+    LDAPCacheEntries        1024
+    LDAPCacheTTL            600
+    LDAPOpCacheEntries      1024
+    LDAPOpCacheTTL          600
+
+    CustomLog /var/log/apache2/svn_logfile "%t %u %{SVN-ACTION}e" env=SVN-ACTION
+
+    <Location />
+    DAV svn
+    SVNParentPath /srv/repos/svn
+    SVNListParentPath on
+    AuthType Basic
+    AuthName "CMS SVN"
+    AuthBasicProvider ldap
+    AuthLDAPURL ldap://ldap.cms.caltech.edu/ou=people,ou=cms,o=caltech,c=us?uid?sub TLS
+    AuthzLDAPAuthoritative off
+    AuthLDAPGroupAttributeIsDN off
+    Require valid-user
+    </Location>
+
+    <Location /ldap-status>
+        SetHandler ldap-status
+        Order deny,allow
+        Deny from all
+        Allow from cs.caltech.edu
+        Allow from cms.caltech.edu
+        AuthType Basic
+        AuthName "LDAP Cache Status"
+        AuthBasicProvider ldap
+        AuthLDAPURL ldap://ldap.cms.caltech.edu/ou=people,ou=cms,o=caltech,c=us?uid?sub TLS
+        AuthzLDAPAuthoritative on
+        Require valid-user
+    </Location>
+
+    # mounted as /srv/repos/svn/staff from FILER:/vol/staff/repo
+    Alias /staff /svn/staff
+    <Location /staff>
+    SVNAutoVersioning on
+    Order allow,deny
+    Allow from all
+    AuthType Basic
+    AuthName "CMS Staff SVN"
+    AuthBasicProvider ldap
+    AuthLDAPURL ldap://ldap.cms.caltech.edu/ou=people,ou=cms,o=caltech,c=us?uid?sub TLS
+    AuthzLDAPAuthoritative on
+    AuthLDAPGroupAttributeIsDN off
+    AuthLDAPGroupAttribute memberUid
+    Require ldap-group cn=staff,ou=Group,ou=CMS,o=Caltech,c=US
+    </Location>
+
+    # mounted as /srv/repos/svn/geometry from FILER:/vol/geometry/collabsvn
+    Alias /geometry /svn/geometry
+    <Location /geometry>
+    SVNAutoVersioning on
+    Order allow,deny
+    Allow from all
+    AuthType Basic
+    AuthName "CMS Geometry SVN"
+    AuthBasicProvider ldap
+    AuthLDAPURL ldap://ldap.cms.caltech.edu/ou=people,ou=cms,o=caltech,c=us?uid?sub TLS
+    AuthzLDAPAuthoritative on
+    AuthLDAPGroupAttributeIsDN off
+    AuthLDAPGroupAttribute memberUid
+    Require ldap-group cn=geometry,ou=Group,ou=CMS,o=Caltech,c=US
+    Require ldap-user leblancd
+    </Location>
+
+
 ### 7 JUL 2010, 14:10
 Creating a collaboration SVN repo:
 


cosmetic fixin's again
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-04-04 19:59:28 UTC (rev 355)
+++ trunk/faq.mdwn	2011-04-04 21:14:08 UTC (rev 356)
@@ -166,7 +166,7 @@
 
 ## How do I create a web page?
 
-By default, every user is allowed to host a web page (within the bounds of their quota) on the CMS users site.  To do this, create a folder called public_html in your home directory, and ensure that the folder is world-readable and executable.  Then any files you place in ~/username/public_html" will be visible at http://users.cms.caltech.edu/~username
+By default, every user is allowed to host a web page (within the bounds of their quota) on the CMS users site.  To do this, create a folder called public\_html in your home directory, and ensure that the folder is world-readable and executable.  Then any files you place in ~/username/public_html" will be visible at http://users.cms.caltech.edu/~username
 
 ## How do I print directly to the printers?
 


added user-private page documentation
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-04-04 19:53:59 UTC (rev 354)
+++ trunk/faq.mdwn	2011-04-04 19:59:28 UTC (rev 355)
@@ -164,6 +164,10 @@
 [[Maia End User Documentation|Using-Maia-Mailguard-in-CMS.pdf]]  
 [[Thunderbird End User Documentation|Using-Thunderbird-in-CMS.pdf]]  
 
+## How do I create a web page?
+
+By default, every user is allowed to host a web page (within the bounds of their quota) on the CMS users site.  To do this, create a folder called public_html in your home directory, and ensure that the folder is world-readable and executable.  Then any files you place in ~/username/public_html" will be visible at http://users.cms.caltech.edu/~username
+
 ## How do I print directly to the printers?
 
 You should only ever print directly to the printer if you have a networked printer that is not for general use (such as a research group's color printer) or a printer that you can physically monitor. Never print a large print job directly to a printer without first checking with other users who may be using a print queue.


fixed a typo.
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-04-04 19:52:53 UTC (rev 353)
+++ trunk/faq.mdwn	2011-04-04 19:53:59 UTC (rev 354)
@@ -159,7 +159,7 @@
     imap.cms.caltech.edu
 Use of SSL/TLS/StartTLS is highly required for the sake of security, to protect your password and privacy.
 
-For detailed instructions on how to configure your mail, see these document:
+For detailed instructions on how to configure your mail, see these documents:
 
 [[Maia End User Documentation|Using-Maia-Mailguard-in-CMS.pdf]]  
 [[Thunderbird End User Documentation|Using-Thunderbird-in-CMS.pdf]]  


another cosmetic change: line breaks
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-04-04 19:49:45 UTC (rev 352)
+++ trunk/faq.mdwn	2011-04-04 19:52:53 UTC (rev 353)
@@ -161,8 +161,8 @@
 
 For detailed instructions on how to configure your mail, see these document:
 
-[[Maia End User Documentation|Using-Maia-Mailguard-in-CMS.pdf]]
-[[Thunderbird End User Documentation|Using-Thunderbird-in-CMS.pdf]]
+[[Maia End User Documentation|Using-Maia-Mailguard-in-CMS.pdf]]  
+[[Thunderbird End User Documentation|Using-Thunderbird-in-CMS.pdf]]  
 
 ## How do I print directly to the printers?
 


cosmetic change
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-04-04 19:38:46 UTC (rev 351)
+++ trunk/faq.mdwn	2011-04-04 19:49:45 UTC (rev 352)
@@ -161,8 +161,8 @@
 
 For detailed instructions on how to configure your mail, see these document:
 
-[[Using-Maia-Mailguard-in-CMS.pdf]]
-[[Using-Thunderbird-in-CMS.pdf]]
+[[Maia End User Documentation|Using-Maia-Mailguard-in-CMS.pdf]]
+[[Thunderbird End User Documentation|Using-Thunderbird-in-CMS.pdf]]
 
 ## How do I print directly to the printers?
 


updated FAQ.
Included Maia/Thunderbird documentation
Replaced instances of "CS" with "CMS"
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-04-04 19:14:47 UTC (rev 350)
+++ trunk/faq.mdwn	2011-04-04 19:38:46 UTC (rev 351)
@@ -3,14 +3,14 @@
 
 ## How do I change my password?
 
-You can change your password either by logging into one of the machines in the domain directly (at the terminal) or by sshing to login.cs.caltech.edu.
+You can change your password either by logging into one of the machines in the domain directly (at the terminal) or by sshing to login.cms.caltech.edu.
 
 Using SSH is as simple as typing
 
-    ssh [yourusername]@login.cs.caltech.edu
+    ssh [yourusername]@login.cms.caltech.edu
 at a command line, if you use a Linux machine. If you use Windows, you'll need to get an SSH client for Windows.
 You can download one of the freely available SSH clients off of the Internet, such as [PuTTY](http://www.chiark.greenend.org.uk/~sgtatham/putty/).
-Use "login.cs.caltech.edu" as the host name, and SSH (port 22) as the protocol.
+Use "login.cms.caltech.edu" as the host name, and SSH (port 22) as the protocol.
 
 At a command prompt, type in 
     **passwd**
@@ -43,18 +43,18 @@
   - contain a mix of alpha and non-alphanumeric characters
   - cannot be similar to your previous password
 
-A common practice is to think of a phrase that you won't forget, like "My CS password is really easy", and then take the first character of each word
+A common practice is to think of a phrase that you won't forget, like "My CMS password is really easy", and then take the first character of each word
 and make it your password, adding a punctuation mark.  In the above example, your password would be "MCpire."
 
  **Note - don't use that particular example!**
 
-## What's the password policy in CS?
+## What's the password policy in CMS?
 
-CS has a password lifecycle of 180 days, adjusted to compensate for change-of-term and end-of-year.
-If you have a CS account, you will be required to change your password twice a year.
+CMS has a password lifecycle of 180 days, adjusted to compensate for change-of-term and end-of-year.
+If you have a CMS account, you will be required to change your password twice a year.
 
-You will be notified via the CS department newsletter when a password changing event is coming up.
-You will also be prompted when/if you log into the CS UNIX hosts that your password is near to expiring for several
+You will be notified via the CMS department newsletter when a password changing event is coming up.
+You will also be prompted when/if you log into the CMS UNIX hosts that your password is near to expiring for several
 days prior to your account being locked out.
 
 If you need practical information on how to change your password, see "How do I change my password?" above.
@@ -62,25 +62,25 @@
 When you change your password, you will be required to follow UNIX-style minimum password requirements.
 If you also have a Windows account, we suggest that you make your password fit the Windows-style minimum password requirements as well, so that you can use the same password for both accounts.
 
-If you forget your password, and you need your account reset, you can email helpATcs.caltech.edu
+If you forget your password, and you need your account reset, you can email helpATcms.caltech.edu
 to contact the system administrators. We will need to be able to confirm your identity somehow in order to reset your account.
 The easiest method of accomplishing this is to physically walk over to our office, in 112 Annenberg, with your Caltech ID.
 
-## What is CS's account policy?
+## What is CMS's account policy?
 
-When you request a CS account through the CS account request form, your account is created with a default expiration date of 4 years from your request date, or your estimated graduation date, whichever is earlier.
-This is for ease of administration - your CS account may be culled if you are no longer affiliated with the Institute.
+When you request a CMS account through the CMS account request form, your account is created with a default expiration date of 4 years from your request date, or your estimated graduation date, whichever is earlier.
+This is for ease of administration - your CMS account may be culled if you are no longer affiliated with the Institute.
 If you are a visitor, your account is enabled only for the length of your stay at Caltech.
 
-CS accounts are intended for use by the requestor of the account *ONLY*. **Do not share your CS username and password with anyone.**
+CMS accounts are intended for use by the requestor of the account *ONLY*. **Do not share your CMS username and password with anyone.**
 
-Each account has a password expiration cycle of 180 days. You must change your CS password at least once every 6 months.
+Each account has a password expiration cycle of 180 days. You must change your CMS password at least once every 6 months.
 If you do not change your password, your interactive login access will be locked. 14 days before your password expires,
-you will be warned at a login prompt when you log into a CS machine, either remotely via login.cs.caltech.edu or at the console.
+you will be warned at a login prompt when you log into a CMS machine, either remotely via login.cms.caltech.edu or at the console.
 Once your password expires, you have a 7 day grace period in which to change your password.
 You will also receive email warnings that your password is going to expire.
-Note that these email warnings go to your CS account (IMSS account for undergrads),
-so if you do not read your CS mail locally, forward your CS mail to an active email account!
+Note that these email warnings go to your CMS account (IMSS account for undergrads),
+so if you do not read your CMS mail locally, forward your CMS mail to an active email account!
 
 
 At the time of your expiration date, your account will become locked - that is, your account will still exist,
@@ -87,8 +87,8 @@
 but you will be unable to log in interactively.
 
 One month after your account has expired, you will be reminded via email that your account has been expired,
-and at that point (if you still need your CS account or expect that you will need your CS account in the future) it is your
-responsibility to inform the CS sysadmins (helpATcs.caltech.edu) that you wish to keep your account,
+and at that point (if you still need your CMS account or expect that you will need your CMS account in the future) it is your
+responsibility to inform the CMS sysadmins (helpATcms.caltech.edu) that you wish to keep your account,
 the reason that you need to keep your account, and (if you are moving to a graduate student position) the sponsoring professor.
 
 Six months after your account expiration date, your data store will be archived, your homedirectory removed, and your
@@ -95,8 +95,8 @@
 local mail delivery halted. This archival process is not backed up, so any data that is remaining in your homedirectory
 is no longer guaranteed to exist past archival date.
 
-As a service to former CS students who have published their CS mail accounts on academic papers, you may leave the CS sysadmins
-with a forwarding address. We will continue to forward all email to your (username)@cs.caltech.edu account to that
+As a service to former CMS students who have published their CMS mail accounts on academic papers, you may leave the CMS sysadmins
+with a forwarding address. We will continue to forward all email to your (username)@cms.caltech.edu account to that
 destination address, provided that the email delivery continues to be allowed.
 It is your sole responsibility to keep your forwarding address current. If your destination address consistently bounces/rejects mail,
 we will remove the mail forward.
@@ -103,62 +103,67 @@
 
 Once we remove you from the mail alias list, we will not re-instate your mail forward.
 
-We do not provide web redirection or other services to former holders of CS accounts.
-Be aware that your CS webspace is available only for the duration of your account.
+We do not provide web redirection or other services to former holders of CMS accounts.
+Be aware that your CMS webspace is available only for the duration of your account.
 
 If you do not graduate within 4 years, or if you stay at the institute as a graduate student,
-you may of course continue to use your CS account. However, since there is no automated fashion in which we can acquire
-this information, it is again the responsibility of the CS account holder to inform the CS sysadmins (via helpATcs.caltech.edu)
+you may of course continue to use your CMS account. However, since there is no automated fashion in which we can acquire
+this information, it is again the responsibility of the CMS account holder to inform the CMS sysadmins (via helpATcms.caltech.edu)
 that you are staying at the institution, and that you need your account active.
 
 It may come to pass after undergraduate graduation or completion of a doctoral program that you will be continuing to
-collaborate on projects with existing CS students or faculty. If this is going to be the case, you may inform the CS
+collaborate on projects with existing CMS students or faculty. If this is going to be the case, you may inform the CMS
 sysadmins that you are requesting collaborator status.
 This MUST be accompanied by approval from a faculty member.
 Collaborator accounts are enabled for a 1 year block of time. At the end of the year, unless informed again by the faculty
 member of an extension for another 1 year period, your account will be expired following the process above.
 
-Finally, it is always the responsibility of the CS account holder to read all email originating from the CS sysadmins,
+Finally, it is always the responsibility of the CMS account holder to read all email originating from the CMS sysadmins,
 so that you will be kept abreast of system outages, changes, etc.
 
 ## What is the remote login policy?
 
-It is *always* better to log into your CS account at a console - that is, sitting in front of a keyboard at the machine you're logging into.
+It is *always* better to log into your CMS account at a console - that is, sitting in front of a keyboard at the machine you're logging into.
 
-This is of course not always feasible. If you are remotely logging into CS machines,
+This is of course not always feasible. If you are remotely logging into CMS machines,
 your sysadmins request that you follow these general rules:
 
- - Do not connect to CS machines from unknown or untrusted hosts!
+ - Do not connect to CMS machines from unknown or untrusted hosts!
 
-This means, don't log into CS machines from a public terminal at a convention somewhere. If you are not absolutely certain
+This means, don't log into CMS machines from a public terminal at a convention somewhere. If you are not absolutely certain
 of the security state of a public machine, and if that machine is compromised, you're giving away your username and password.
  
 This also means that you need to be keeping your personal computer(s) up to date and patched with the latest security updates.
 
- - If you're connecting remotely to ANY resource in CS, we ask that you start at login.cs.caltech.edu.
+ - If you're connecting remotely to ANY resource in CMS, we ask that you start at login.cms.caltech.edu.
  
 So if you need to connect to a particular machine for some reason, and you're coming from your home machine,
-ssh to login.cs.caltech.edu, and then from login.cs.caltech.edu connect to the machine you're trying to reach.
-This seems counter-intuitive, but that way the CS system administrators can keep an eye on the individual auth logs and
+ssh to login.cms.caltech.edu, and then from login.cms.caltech.edu connect to the machine you're trying to reach.
+This seems counter-intuitive, but that way the CMS system administrators can keep an eye on the individual auth logs and
 catch "strange" connections as possible security intrusions. 
  
- - Do not chain through multiple hosts to get to CS machines.
+ - Do not chain through multiple hosts to get to CMS machines.
 
-If you're sitting at your home machine, and you want to connect to CS, ssh to login.cs.caltech.edu directly.
+If you're sitting at your home machine, and you want to connect to CMS, ssh to login.cms.caltech.edu directly.
 For example, don't connect to your account at Berkeley, then your account at your old high school, then your buddy's
-machine in West Germany, and finally to CS.
+machine in West Germany, and finally to CMS.
 If there are any compromises on any of those other machines, you may be giving away your username and password.
 
-## How can I use IMAP to read my mail in CS?
+## How can I use IMAP to read my mail in CMS?
 
-The IMAP server in CS accesses mail stored in Maildir format in your home directory;
+The IMAP server in CMS accesses mail stored in Maildir format in your home directory;
 more specifically the "Maildir" subdirectory in your home directory.
 
 You can read/retrieve IMAP mail by pointing your IMAP client (Mozilla/Thunderbird/Outlook) at:
 
-    imap.cs.caltech.edu
-Use of SSL/TLS/StartTLS is highly recommended for the sake of security, to protect your password and privacy.
+    imap.cms.caltech.edu
+Use of SSL/TLS/StartTLS is highly required for the sake of security, to protect your password and privacy.
 
+For detailed instructions on how to configure your mail, see these document:
+
+[[Using-Maia-Mailguard-in-CMS.pdf]]
+[[Using-Thunderbird-in-CMS.pdf]]
+
 ## How do I print directly to the printers?
 
 You should only ever print directly to the printer if you have a networked printer that is not for general use (such as a research group's color printer) or a printer that you can physically monitor. Never print a large print job directly to a printer without first checking with other users who may be using a print queue.
@@ -165,16 +170,16 @@
 
 Public or semi-public printers in Annenberg include:
 
-  - ann104.cs.caltech.edu (instructional lab)
-  - ann119.cs.caltech.edu (first floor postdoc printer)
-  - ann206b.cs.caltech.edu (second floor printer)
-  - ann305.cs.caltech.edu (third floor copy room printer)

(Diff truncated)
added user docs for mail
Added: trunk/faq/Using-Maia-Mailguard-in-CMS.pdf
===================================================================
(Binary files differ)

Index: trunk/faq/Using-Maia-Mailguard-in-CMS.pdf
===================================================================
--- trunk/faq/Using-Maia-Mailguard-in-CMS.pdf	2011-03-24 23:29:08 UTC (rev 349)
+++ trunk/faq/Using-Maia-Mailguard-in-CMS.pdf	2011-04-04 19:14:47 UTC (rev 350)

Property changes on: trunk/faq/Using-Maia-Mailguard-in-CMS.pdf
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/faq/Using-Thunderbird-in-CMS.pdf
===================================================================
(Binary files differ)

Index: trunk/faq/Using-Thunderbird-in-CMS.pdf
===================================================================
--- trunk/faq/Using-Thunderbird-in-CMS.pdf	2011-03-24 23:29:08 UTC (rev 349)
+++ trunk/faq/Using-Thunderbird-in-CMS.pdf	2011-04-04 19:14:47 UTC (rev 350)

Property changes on: trunk/faq/Using-Thunderbird-in-CMS.pdf
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property

Modified: trunk/sysadmin/Projects/CMSFileSystemQuota.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSFileSystemQuota.mdwn	2011-03-24 23:13:57 UTC (rev 348)
+++ trunk/sysadmin/Projects/CMSFileSystemQuota.mdwn	2011-03-24 23:29:08 UTC (rev 349)
@@ -13,7 +13,7 @@
 `1.3.6.1.4.1.789.1.4.6.1.5` |***qrV2LowKBytesUsed***|`integer32`|  The current number of KBytes used for this qrV2Entry.
 `1.3.6.1.4.1.789.1.4.6.1.8` |***qrV2LowKByesLimit***|`integer32`|  The limit of KBytes that can be used for this qrV2Entry. This will return 0 if qrV2QuotaUnlimited is true.
 `1.3.6.1.4.1.789.1.4.6.1.9` |***qrV2FilesUsed***    |`integer32`|  The current number of files used for this entry.
-`1.3.6.1.4.1.789.1.4.6.1.13`|***qrV2Volume***       |`integer32`|  A number that identifies the volume for which this quota is in effect on. The volume that this value represents is in qvStateName with qvStateVolume set to the value here.
+`1.3.6.1.4.1.789.1.4.6.1.13`|***qrV2Volume***       |`integer32`|  A number that identifies the volume for which this quota is in effect on. The volume that this value represents is in ***qvStateName*** with ***qvStateVolume*** set to the value here.
 `1.3.6.1.4.1.789.1.4.6.1.19`|***qrV2LowKBytesThreshold***|`integer32`| A number of KBytes that when used by this entry produces a warning.
 `1.3.6.1.4.1.789.1.4.4.1.1` |***qvStateVolume***    |`integer32`|  A number that identifies this volume. The mapping of this number to actual volumes may change if volumes are added or deleted. Use qvStateName to unambiguously identify a volume.
 `1.3.6.1.4.1.789.1.4.4.1.2` |***qvStateName***      |`DisplayString`|   Indicates the name of this volume.


Modified: trunk/sysadmin/Projects/CMSFileSystemQuota.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSFileSystemQuota.mdwn	2011-03-24 21:48:27 UTC (rev 347)
+++ trunk/sysadmin/Projects/CMSFileSystemQuota.mdwn	2011-03-24 23:13:57 UTC (rev 348)
@@ -6,7 +6,15 @@
 
 Therefore, the following is a rundown of all the practical SNMP MIBs needed to perform such a report.
 
-[[!table  data="""
+[[!table  header="row" data="""
 OID|Name|Type|Description
-1.3.6.1.4.1.789.1.4.6.1.1|qrV2Index|integer32|A number that identifies this entry in the file /etc/quotas in the given volume
+`1.3.6.1.4.1.789.1.4.6.1.1` |***qrV2Index***        |`integer32`|  A number that identifies this entry in the file /etc/quotas in the given volume
+`1.3.6.1.4.1.789.1.4.6.1.3` |***qrV2Id***           |`integer32`|  The UID (user's numerical ID) or the GID, as applicable, associated with this qrV2Entry.
+`1.3.6.1.4.1.789.1.4.6.1.5` |***qrV2LowKBytesUsed***|`integer32`|  The current number of KBytes used for this qrV2Entry.
+`1.3.6.1.4.1.789.1.4.6.1.8` |***qrV2LowKByesLimit***|`integer32`|  The limit of KBytes that can be used for this qrV2Entry. This will return 0 if qrV2QuotaUnlimited is true.
+`1.3.6.1.4.1.789.1.4.6.1.9` |***qrV2FilesUsed***    |`integer32`|  The current number of files used for this entry.
+`1.3.6.1.4.1.789.1.4.6.1.13`|***qrV2Volume***       |`integer32`|  A number that identifies the volume for which this quota is in effect on. The volume that this value represents is in qvStateName with qvStateVolume set to the value here.
+`1.3.6.1.4.1.789.1.4.6.1.19`|***qrV2LowKBytesThreshold***|`integer32`| A number of KBytes that when used by this entry produces a warning.
+`1.3.6.1.4.1.789.1.4.4.1.1` |***qvStateVolume***    |`integer32`|  A number that identifies this volume. The mapping of this number to actual volumes may change if volumes are added or deleted. Use qvStateName to unambiguously identify a volume.
+`1.3.6.1.4.1.789.1.4.4.1.2` |***qvStateName***      |`DisplayString`|   Indicates the name of this volume.
 """]]


automatic index generation
Added: trunk/sysadmin/projects.mdwn
===================================================================
--- trunk/sysadmin/projects.mdwn	                        (rev 0)
+++ trunk/sysadmin/projects.mdwn	2011-03-24 22:50:51 UTC (rev 346)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/projects/* and ! sysadmin/projects/*/*"]]


Added: trunk/sysadmin/projects/cmsfilesystemquota.mdwn
===================================================================
--- trunk/sysadmin/projects/cmsfilesystemquota.mdwn	                        (rev 0)
+++ trunk/sysadmin/projects/cmsfilesystemquota.mdwn	2011-03-24 22:50:49 UTC (rev 345)
@@ -0,0 +1,11 @@
+CMS central file system (NFS/CIFS) needs a handy way of notifying users of their filespace usage.
+
+One way to do this (as was done in the past) is to crawl the entire filesystem, and perform `du -h` for each user's directory.  Not only does this consume resources, but this is wasteful and does not scale well -- the NetApp already keeps track of users' usage.
+
+The best/easiest way to approach this is to perform SNMP queries upon qtrees and quotas, collect the data, and produce an easily readable report.
+
+Therefore, the following is a rundown of all the practical SNMP MIBs needed to perform such a report.
+
+[[!table  data="""
+1.3.6.1.4.1.789.1.4.6.1.1|qrV2Index|integer32|A number that identifies this entry in the file /etc/quotas in the given volume
+"""]]


Modified: trunk/sysadmin/Projects.mdwn
===================================================================
--- trunk/sysadmin/Projects.mdwn	2011-03-08 01:45:11 UTC (rev 343)
+++ trunk/sysadmin/Projects.mdwn	2011-03-24 22:37:44 UTC (rev 344)
@@ -1,7 +1,7 @@
 ##Ongoing projects within CMS
 
 [[Projects/CMSEmail]]  
-   *in beta testing*
+   *awaiting migration from CS -> CMS*
 
 [[Projects/Collaborators]]  
  *in beta testing*
@@ -9,6 +9,9 @@
 [[Projects/CondorHTC]]  
  *in alpha testing*
 
+[[Projects/CMSFileSystemQuota]]   
+ *planning*
+
 [[Projects/VNCReplacement]]  
  *TBD*
 


HASH(0x2f6e6f0)
Copied: trunk/sysadmin/Projects/CMSFileSystemQuota.mdwn (from rev 346, trunk/sysadmin/projects/cmsfilesystemquota.mdwn)
===================================================================
--- trunk/sysadmin/Projects/CMSFileSystemQuota.mdwn	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSFileSystemQuota.mdwn	2011-03-24 21:48:27 UTC (rev 347)
@@ -0,0 +1,12 @@
+CMS central file system (NFS/CIFS) needs a handy way of notifying users of their filespace usage.
+
+One way to do this (as was done in the past) is to crawl the entire filesystem, and perform `du -h` for each user's directory.  Not only does this consume resources, but this is wasteful and does not scale well -- the NetApp already keeps track of users' usage.
+
+The best/easiest way to approach this is to perform SNMP queries upon qtrees and quotas, collect the data, and produce an easily readable report.
+
+Therefore, the following is a rundown of all the practical SNMP MIBs needed to perform such a report.
+
+[[!table  data="""
+OID|Name|Type|Description
+1.3.6.1.4.1.789.1.4.6.1.1|qrV2Index|integer32|A number that identifies this entry in the file /etc/quotas in the given volume
+"""]]


replaced link with PDF
Modified: trunk/sysadmin/Tips/AddingRPMsToOpenSUSE.mdwn
===================================================================
--- trunk/sysadmin/Tips/AddingRPMsToOpenSUSE.mdwn	2011-03-08 01:42:45 UTC (rev 342)
+++ trunk/sysadmin/Tips/AddingRPMsToOpenSUSE.mdwn	2011-03-08 01:45:11 UTC (rev 343)
@@ -1,8 +1,11 @@
 [[!tag howto]]
 ###Adding a repository for openSUSE installation
 
-[YaST Add-On Creator](http://developer.novell.com/wiki/index.php/Creating_Add-On_Media_with_YaST)
+[[add-on-creator-cool-v1_1.pdf]]
 
     yast2 add-on-creator
 
 Follow the procedure above to create a repo for openSUSE.
+
+
+


attachment upload
Added: trunk/sysadmin/Tips/AddingRPMsToOpenSUSE/add-on-creator-cool-v1_1.pdf
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Tips/AddingRPMsToOpenSUSE/add-on-creator-cool-v1_1.pdf
===================================================================
--- trunk/sysadmin/Tips/AddingRPMsToOpenSUSE/add-on-creator-cool-v1_1.pdf	2011-02-18 22:01:33 UTC (rev 341)
+++ trunk/sysadmin/Tips/AddingRPMsToOpenSUSE/add-on-creator-cool-v1_1.pdf	2011-03-08 01:42:45 UTC (rev 342)

Property changes on: trunk/sysadmin/Tips/AddingRPMsToOpenSUSE/add-on-creator-cool-v1_1.pdf
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property

Modified: trunk/sysadmin/Projects/VNCReplacement.mdwn
===================================================================
--- trunk/sysadmin/Projects/VNCReplacement.mdwn	2011-02-18 21:53:12 UTC (rev 340)
+++ trunk/sysadmin/Projects/VNCReplacement.mdwn	2011-02-18 22:01:33 UTC (rev 341)
@@ -29,5 +29,5 @@
 This project will explore the availability and ease of use with zero
 loss of functionality in other desktop-sharing/collaboration tools.
 
-One such candidate might be [DimDim](http://www.dimdim.com/community/opensource.html),
+One such candidate might be [TeamViewer](http://www.teamviewer.com/en/products/benefits.aspx),
 which was discovered through [this matrix](http://en.wikipedia.org/wiki/Desktop_sharing).


Modified: trunk/sysadmin/Projects.mdwn
===================================================================
--- trunk/sysadmin/Projects.mdwn	2011-02-18 21:52:28 UTC (rev 339)
+++ trunk/sysadmin/Projects.mdwn	2011-02-18 21:53:12 UTC (rev 340)
@@ -22,5 +22,5 @@
 [[Projects/OpenNMS]]  
  completed
 
-[[Projects/ABET]]
+[[Projects/ABET]]  
  completed


Modified: trunk/sysadmin/Projects.mdwn
===================================================================
--- trunk/sysadmin/Projects.mdwn	2011-02-18 00:05:02 UTC (rev 338)
+++ trunk/sysadmin/Projects.mdwn	2011-02-18 21:52:28 UTC (rev 339)
@@ -15,9 +15,6 @@
 [[Projects/Web-LDAP]]  
  ***planning***
 
-[[Projects/ABET]]  
- *implementing*
-
 ***
 
 ##Completed projects
@@ -24,3 +21,6 @@
 
 [[Projects/OpenNMS]]  
  completed
+
+[[Projects/ABET]]
+ completed


Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-02-18 00:02:05 UTC (rev 337)
+++ trunk/faq.mdwn	2011-02-18 00:05:02 UTC (rev 338)
@@ -272,7 +272,7 @@
 
 This ability to have in-line rotating backups allows you to quickly restore something that you have inadvertantly deleted without waiting for the system admin to restore the data from tape.
 
-However, you should *definitely* keep in mind that data that does not get stored across a snapshot will not appear in a snapshot at all.
+**However, you should *definitely* keep in mind that data that is not stored during a snapshot will not appear in a `.snapshot` at all.**
 
 In other words, if you:
 


Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-02-17 23:56:56 UTC (rev 336)
+++ trunk/faq.mdwn	2011-02-18 00:02:05 UTC (rev 337)
@@ -252,39 +252,38 @@
 
 ## What is this `.snapshot` directory I keep seeing?
 
-Snapshots are a native function of our file server.                                                                                                     
-In every directory, when a directory is created the system also creates '.snapshot'.  Periodically throughout the day, 4 times a day, 
-the system copies all *diff* data on disk into the appropriate snapshot.  At 8am, noon, 4pm, and 8pm, data that is different from the                       
-previous snapshot point is linked to its appropriate snapshot, marked as something similar to:
-    hourly.0                                                                                                                                             
-    hourly.1                                                                                                                                             
-etc.                                                                                                                                                 
-                                                                                                                                                        
-There are hourly snapshots (done 4 times a day), nightly snapshots (which is essentially the last hourly snapshot), and weekly (which 
-is basically the last nightly snapshot).                  
-                                                                                                                                                        
-The system keeps:                                                                                                                                       
- - the last 6 hourly snapshots,                                                                                                                        
- - the last 2 nightly snapshots, and                                                                                                                   
- - the last 2 weekly snapshots.                                                                                                                        
-                                                                                                                                                        
-This ability to have in-line rotating backups allows you to quickly restore something that you have inadvertantly deleted without waiting                       
-for the system admin to restore the data from tape.
-                                                                                                                                                        
+Snapshots are a native function of our file server.
+In every directory, when a directory is created the system also creates '.snapshot'.  Periodically throughout the day, 4 times a day, the system copies all *diff* data on disk into the appropriate snapshot.  At 8am, noon, 4pm, and 8pm, data that is different from the previous snapshot point is linked to its appropriate snapshot, marked as something similar to:
+
+    hourly.0
+    hourly.1
+
+There are:
+
+ - hourly snapshots (done 4 times a day),
+ - nightly snapshots (which is essentially the last hourly snapshot), and 
+ - weekly snapshots (which is basically the last nightly snapshot).
+
+The system keeps:
+
+ - the last 6 hourly snapshots,
+ - the last 2 nightly snapshots, and
+ - the last 2 weekly snapshots.
+
+This ability to have in-line rotating backups allows you to quickly restore something that you have inadvertantly deleted without waiting for the system admin to restore the data from tape.
+
 However, you should *definitely* keep in mind that data that does not get stored across a snapshot will not appear in a snapshot at all.
-                    
+
 In other words, if you:
 
- 1. create a file at 9am.
- 2. delete the same file at 11am.
+ 1. *create* a file at 9am.
+ 2. *delete* the same file at 11am.
 
 the file has not been stored long enough to be captured in a snapshot, and cannot be recovered.
-(This is similar to tape backups where you create and destroy data before the backup process has had a chance to write it to a tape for offline
-archive.)
+(This is similar to tape backups where you create and destroy data before the backup process has had a chance to write it to a tape for offline archive.)
 
-Also, you should note that snapshots are *not* for storing data as the data itself is part of your disk usage quota, and snapshots are
-rotated out every 2 weeks.
-                                                                                                                                                        
+Also, you should note that snapshots are *not* for storing data as the data itself is part of your disk usage quota, and snapshots are rotated out every 2 weeks.
+
 For obvious reasons, you cannot delete the .snapshot directory, though it should be "hidden" from most casual directory listings due to the name 
 beginning with a **.**
 


info about .snapshot
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-02-01 23:34:43 UTC (rev 335)
+++ trunk/faq.mdwn	2011-02-17 23:56:56 UTC (rev 336)
@@ -250,6 +250,44 @@
 
 Finally, if you are a grad student or if you are working on a research project, your group may have access to some other applications. For more information, see your research group professor. 
 
+## What is this `.snapshot` directory I keep seeing?
+
+Snapshots are a native function of our file server.                                                                                                     
+In every directory, when a directory is created the system also creates '.snapshot'.  Periodically throughout the day, 4 times a day, 
+the system copies all *diff* data on disk into the appropriate snapshot.  At 8am, noon, 4pm, and 8pm, data that is different from the                       
+previous snapshot point is linked to its appropriate snapshot, marked as something similar to:
+    hourly.0                                                                                                                                             
+    hourly.1                                                                                                                                             
+etc.                                                                                                                                                 
+                                                                                                                                                        
+There are hourly snapshots (done 4 times a day), nightly snapshots (which is essentially the last hourly snapshot), and weekly (which 
+is basically the last nightly snapshot).                  
+                                                                                                                                                        
+The system keeps:                                                                                                                                       
+ - the last 6 hourly snapshots,                                                                                                                        
+ - the last 2 nightly snapshots, and                                                                                                                   
+ - the last 2 weekly snapshots.                                                                                                                        
+                                                                                                                                                        
+This ability to have in-line rotating backups allows you to quickly restore something that you have inadvertantly deleted without waiting                       
+for the system admin to restore the data from tape.
+                                                                                                                                                        
+However, you should *definitely* keep in mind that data that does not get stored across a snapshot will not appear in a snapshot at all.
+                    
+In other words, if you:
+
+ 1. create a file at 9am.
+ 2. delete the same file at 11am.
+
+the file has not been stored long enough to be captured in a snapshot, and cannot be recovered.
+(This is similar to tape backups where you create and destroy data before the backup process has had a chance to write it to a tape for offline
+archive.)
+
+Also, you should note that snapshots are *not* for storing data as the data itself is part of your disk usage quota, and snapshots are
+rotated out every 2 weeks.
+                                                                                                                                                        
+For obvious reasons, you cannot delete the .snapshot directory, though it should be "hidden" from most casual directory listings due to the name 
+beginning with a **.**
+
 ## What computational resources are available to me in the department?
 
 Every member of the CMS department has access to the instructional lab on the first floor.  Please read the acceptable use policy for the instructional lab before using the lab machines!


Fixed an error in DAVE'S documentation
Modified: trunk/sysadmin/Tips/EditingWikiPages.mdwn
===================================================================
--- trunk/sysadmin/Tips/EditingWikiPages.mdwn	2011-02-01 21:06:21 UTC (rev 334)
+++ trunk/sysadmin/Tips/EditingWikiPages.mdwn	2011-02-01 23:34:43 UTC (rev 335)
@@ -13,7 +13,7 @@
 
 comment on the changes/additions are optional.
 
-Then, log into `x-help.cs` as root, and issue on the command-line:
+Then, log into `x-help1.cs` as root, and issue on the command-line:
 
 	ikiwiki -setup /etc/ikiwiki/SysAdminHelp.setup
 


cleaned up URLs in the FAQ
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-02-01 20:54:13 UTC (rev 333)
+++ trunk/faq.mdwn	2011-02-01 21:06:21 UTC (rev 334)
@@ -266,18 +266,14 @@
 
 First, you may have a physical connection problem.  In Annenberg, the wall plates have three jacks, but typically only two of the jacks are for network connectivity, while the third is for the digital phone system.  Check your computer for a physical link light (generally, a solid amber light with a flicerking green light on the port where the computer connects to the cable indicates that you're connected to the network).  If there is no connection light, either you are plugged into a telephone jack, the cable is broken, or the network card in your computer is dead.
 
-Second, you may have been blocked from accessing the campus network because your machine has been compromised.  You can check to see if you're on IMSS Security's blocked list by vising this URL from another computer and entering your MAC address:
+Second, you may have been blocked from accessing the campus network because your machine has been compromised.  You can check to see if you're on IMSS Security's blocked list by vising [this security page][4] from another computer and entering your MAC address.
 
-http://www.its.caltech.edu/cgi-bin/blockcheck.pl
+It is difficult for IMSS Security to keep track of all the hosts on campus, and to ensure the campus network is safe, they sometimes need to block machines without knowing who is the user of the machine.  If you are running your own machine (as opposed to a CMS-managed installation), we recommend that you register your MAC address with IMSS Security, so that they can contact you directly in the event your machine is compromised.  
 
-It is difficult for IMSS Security to keep track of all the hosts on campus, and to ensure the campus network is safe, they sometimes need to block machines without knowing who is the user of the machine.  If you are running your own machine (as opposed to a CMS-managed installation), we recommend that you register your MAC address with IMSS Security, so that they can contact you directly in the event your machine is compromised.  You can register your MAC at this URL:
+You can register your MAC at [this URL][5]
 
-http://www.its.caltech.edu/cgi-bin/macregistry.pl
+If you have multiple hosts to register, you can do that via [this URL][6]
 
-If you have multiple hosts to register, you can do that here:
-
-http://www.its.caltech.edu/cgi-bin/sysadminsignup.pl
-
 ## How do I find out my MAC address?
 
 There are many methods that will work, depending upon your operating system.
@@ -316,8 +312,6 @@
 
 Your "Physical Address" is your MAC address. 
 
-  [1]: http://software.caltech.edu/
-  [2]: http://beaverwulf.caltech.edu/wordpress/
 
 ## How do I redirect my web page?
 
@@ -329,10 +323,8 @@
 
 CMS maintains its own Certificate Authority (CA), which we use to sign SSL certificates for services run in CMS.  Importing the CA certificate will allow your applications to trust any certificate signed by our CA, thus removing the need to import our certificates one at a time in your browser, etc.
 
-You can get the public certificate for our CA from this web page:
+You can get the public certificate for our CA from [our PKI web page][3]:
 
-http://pki.cms.caltech.edu/ejbca/retrieve/ca_certs.jsp
-
 We have two CA certificates, the certificate that we use to sign SSL certificates is the CA: CMS-CA certificate.
 
 Clicking on the "Download to Firefox" link, for example, will open the following dialogue box:
@@ -356,3 +348,11 @@
 [[import-PEM-CMSCA.jpg]]
 
 A dialogue box similar to the one picture above will open, click all three check boxes and hit "OK".  Your mail client will now import the CA certificate.
+
+
+  [1]: http://software.caltech.edu/
+  [2]: http://beaverwulf.caltech.edu/wordpress/
+  [3]: http://pki.cms.caltech.edu/ejbca/retrieve/ca_certs.jsp
+  [4]: http://www.its.caltech.edu/cgi-bin/blockcheck.pl
+  [5]: http://www.its.caltech.edu/cgi-bin/macregistry.pl
+  [6]: http://www.its.caltech.edu/cgi-bin/sysadminsignup.pl


added CA instructions
Added: trunk/faq/Tools-Options-Advanced.jpg
===================================================================
(Binary files differ)

Index: trunk/faq/Tools-Options-Advanced.jpg
===================================================================
--- trunk/faq/Tools-Options-Advanced.jpg	2011-02-01 20:53:18 UTC (rev 332)
+++ trunk/faq/Tools-Options-Advanced.jpg	2011-02-01 20:54:13 UTC (rev 333)

Property changes on: trunk/faq/Tools-Options-Advanced.jpg
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/faq/certificate-manager.jpg
===================================================================
(Binary files differ)

Index: trunk/faq/certificate-manager.jpg
===================================================================
--- trunk/faq/certificate-manager.jpg	2011-02-01 20:53:18 UTC (rev 332)
+++ trunk/faq/certificate-manager.jpg	2011-02-01 20:54:13 UTC (rev 333)

Property changes on: trunk/faq/certificate-manager.jpg
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/faq/downloading-certificate.jpg
===================================================================
(Binary files differ)

Index: trunk/faq/downloading-certificate.jpg
===================================================================
--- trunk/faq/downloading-certificate.jpg	2011-02-01 20:53:18 UTC (rev 332)
+++ trunk/faq/downloading-certificate.jpg	2011-02-01 20:54:13 UTC (rev 333)

Property changes on: trunk/faq/downloading-certificate.jpg
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/faq/import-PEM-CMSCA.jpg
===================================================================
(Binary files differ)

Index: trunk/faq/import-PEM-CMSCA.jpg
===================================================================
--- trunk/faq/import-PEM-CMSCA.jpg	2011-02-01 20:53:18 UTC (rev 332)
+++ trunk/faq/import-PEM-CMSCA.jpg	2011-02-01 20:54:13 UTC (rev 333)

Property changes on: trunk/faq/import-PEM-CMSCA.jpg
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property

added CA instructions
Modified: trunk/faq.mdwn
===================================================================
--- trunk/faq.mdwn	2011-01-13 21:44:50 UTC (rev 331)
+++ trunk/faq.mdwn	2011-02-01 20:53:18 UTC (rev 332)
@@ -324,3 +324,35 @@
 If you want to redirect your user-private web page to an off-CMS web site, the easiest way to do this is by putting an index.html file in your web directory (~/public_html on CMS systems) with the following contents:
 
 [[web-redirect.jpg]]
+
+## How do I import the CMS Certificate Authority?
+
+CMS maintains its own Certificate Authority (CA), which we use to sign SSL certificates for services run in CMS.  Importing the CA certificate will allow your applications to trust any certificate signed by our CA, thus removing the need to import our certificates one at a time in your browser, etc.
+
+You can get the public certificate for our CA from this web page:
+
+http://pki.cms.caltech.edu/ejbca/retrieve/ca_certs.jsp
+
+We have two CA certificates, the certificate that we use to sign SSL certificates is the CA: CMS-CA certificate.
+
+Clicking on the "Download to Firefox" link, for example, will open the following dialogue box:
+
+[[downloading-certificate.jpg]]
+
+Click on all three check boxes, and hit the "OK" button to import the certificate.  Now Firefox will trust the SSL certificates signed by the CMS CA.
+
+To import the certificate into your email client, click on the "Download as PEM" link.  A dialogue box will open, save the file (CMSCA.pem) to your desktop.
+
+After the CA certificate has been downloaded, open up Thunderbird.  Choose the "Tools" menu, and then "Options".  
+
+[[Tools-Options-Advanced.jpg]]
+
+Click on the "View Certificates" button.  The following window will open, hit "Import" to continue:
+
+[[certificate-manager.jpg]]
+
+Browse to the CMSCA.pem file and select it:
+
+[[import-PEM-CMSCA.jpg]]
+
+A dialogue box similar to the one picture above will open, click all three check boxes and hit "OK".  Your mail client will now import the CA certificate.


Modified: trunk/sysadmin/Projects/CMSEmail.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail.mdwn	2011-01-13 21:37:56 UTC (rev 330)
+++ trunk/sysadmin/Projects/CMSEmail.mdwn	2011-01-13 21:44:50 UTC (rev 331)
@@ -65,9 +65,10 @@
 
  - CS domain-specific aliases will be in the `ou=CS,ou=Aliases` branch of the LDAP DIT and `ou=ACM` for ACM aliases, etc.
  - To continue with the process of undergrad accounts getting only a forwarding alias, the aliases will be CS aliases, using the above.
- - Graduate students will have the option of attaching a CS (or ACM/CDS) email address to their account, as well as a forwarding alias upon departure.
+ - Graduate students (and possibly others?) will have the option of attaching a CS (or ACM/CDS) email address to their account, as well as a forwarding alias upon departure.
    - to accomodate this, we will need to modify the User Account Request web form (to provide this option, and have the user check one/all)
    - our new user creation script will need to be modified to accomodate any user legacy email address preferences, and act accordingly
+   - this will also need to be accounted for during the account culling process -- giving the user the option of 4 possible forwarding aliases
 
 ***
 ### 10 Jan 2011


Modified: trunk/sysadmin/Projects/CMSEmail.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail.mdwn	2011-01-10 23:50:38 UTC (rev 329)
+++ trunk/sysadmin/Projects/CMSEmail.mdwn	2011-01-13 21:37:56 UTC (rev 330)
@@ -57,6 +57,19 @@
     info AT cms.caltech.edu           -> sheila AT acm.caltech.edu
 
 ***
+### 13 Jan 2011
+
+The faculty would like to have CS email addresses attached to (grad) accounts by default as part of their branding.
+
+To accomodate this, and create a framework to accomodate the other domains as well, we have modified the LDAP methodology such that:
+
+ - CS domain-specific aliases will be in the `ou=CS,ou=Aliases` branch of the LDAP DIT and `ou=ACM` for ACM aliases, etc.
+ - To continue with the process of undergrad accounts getting only a forwarding alias, the aliases will be CS aliases, using the above.
+ - Graduate students will have the option of attaching a CS (or ACM/CDS) email address to their account, as well as a forwarding alias upon departure.
+   - to accomodate this, we will need to modify the User Account Request web form (to provide this option, and have the user check one/all)
+   - our new user creation script will need to be modified to accomodate any user legacy email address preferences, and act accordingly
+
+***
 ### 10 Jan 2011
 
 New LDAP service has been populated, CS DIT is now the CMS DIT, and read-write LDAP for CS has been disabled.


Modified: trunk/sysadmin/Projects/CMSEmail.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail.mdwn	2010-12-22 01:55:01 UTC (rev 328)
+++ trunk/sysadmin/Projects/CMSEmail.mdwn	2011-01-10 23:50:38 UTC (rev 329)
@@ -57,6 +57,13 @@
     info AT cms.caltech.edu           -> sheila AT acm.caltech.edu
 
 ***
+### 10 Jan 2011
+
+New LDAP service has been populated, CS DIT is now the CMS DIT, and read-write LDAP for CS has been disabled.
+All LDAP clients (except those for SMTP in CS) have been re-aligned to CMS, rather than CS.
+Next up:  Change all @cs.caltech.edu DNS results to point to NAPOLEON.CMS, the new SMTP server for both CMS and CS domains.
+
+***
 ### 20 Dec 2010
 
 MAIA system was re-configured to **label** messages as appropriate per


Modified: trunk/AOK/VirtualMachine.mdwn
===================================================================
--- trunk/AOK/VirtualMachine.mdwn	2010-12-21 00:29:02 UTC (rev 327)
+++ trunk/AOK/VirtualMachine.mdwn	2010-12-22 01:55:01 UTC (rev 328)
@@ -15,6 +15,7 @@
 CONFMASTER1    |bcfg2        |Bcfg2        |CHARYBDIS
 CODEBASE       |collab       |SVN Collab   |CHARYBDIS
 KNIGHT         |loghost      |LogAnalyzer  |CHARYBDIS
+ZULU           |auto_inst    |AutoInst     |CHARYBDIS
 ABET-DEVEL     |ABET         |ABET website |PRILICIA
 GGLAB          |gglab        |Al Barr's VM |PRILICIA
 BUILD          |build        |RPM devel VM |PRILICIA


automatic index generation
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803.mdwn	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803.mdwn	2010-12-21 01:18:54 UTC (rev 323)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/Projects/CMSEmail/Reports/20101215.1803/* and ! sysadmin/Projects/CMSEmail/Reports/20101215.1803/*/*"]]

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1959.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1959.mdwn	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1959.mdwn	2010-12-21 01:18:54 UTC (rev 323)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/Projects/CMSEmail/Reports/20101215.1959/* and ! sysadmin/Projects/CMSEmail/Reports/20101215.1959/*/*"]]

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101216.1634.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101216.1634.mdwn	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101216.1634.mdwn	2010-12-21 01:18:54 UTC (rev 323)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/Projects/CMSEmail/Reports/20101216.1634/* and ! sysadmin/Projects/CMSEmail/Reports/20101216.1634/*/*"]]

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101217.1254.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101217.1254.mdwn	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101217.1254.mdwn	2010-12-21 01:18:54 UTC (rev 323)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/Projects/CMSEmail/Reports/20101217.1254/* and ! sysadmin/Projects/CMSEmail/Reports/20101217.1254/*/*"]]

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101217.1709.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101217.1709.mdwn	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101217.1709.mdwn	2010-12-21 01:18:54 UTC (rev 323)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/Projects/CMSEmail/Reports/20101217.1709/* and ! sysadmin/Projects/CMSEmail/Reports/20101217.1709/*/*"]]

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101217.2004.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101217.2004.mdwn	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101217.2004.mdwn	2010-12-21 01:18:54 UTC (rev 323)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/Projects/CMSEmail/Reports/20101217.2004/* and ! sysadmin/Projects/CMSEmail/Reports/20101217.2004/*/*"]]

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101220.1347.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101220.1347.mdwn	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101220.1347.mdwn	2010-12-21 01:18:54 UTC (rev 323)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/Projects/CMSEmail/Reports/20101220.1347/* and ! sysadmin/Projects/CMSEmail/Reports/20101220.1347/*/*"]]


HASH(0x2f859b0)
Modified: trunk/sysadmin/Projects/CMSEmail.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail.mdwn	2010-12-21 00:25:12 UTC (rev 326)
+++ trunk/sysadmin/Projects/CMSEmail.mdwn	2010-12-21 00:29:02 UTC (rev 327)
@@ -57,6 +57,15 @@
     info AT cms.caltech.edu           -> sheila AT acm.caltech.edu
 
 ***
+### 20 Dec 2010
+
+MAIA system was re-configured to **label** messages as appropriate per
+default.
+
+The MAIA system was re-tested with that setting, and reports were
+published [here](Reports).
+
+***
 ### 17 Dec 2010
 As testing continues, a few glitches were discovered:
 


HASH(0x2f85b78)
Modified: trunk/sysadmin/Projects/CMSEmail/Reports.html
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports.html	2010-12-21 00:22:39 UTC (rev 325)
+++ trunk/sysadmin/Projects/CMSEmail/Reports.html	2010-12-21 00:25:12 UTC (rev 326)
@@ -1,8 +1,5 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
 <HTML>
-<TITLE>
-MStone Results
-</TITLE>
 <HEAD>
 </HEAD>
 <BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000AA" VLINK="#770033" ALINK="#FF0000">


HASH(0x2f874e8)
Modified: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/results.html
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/results.html	2010-12-21 00:18:12 UTC (rev 324)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/results.html	2010-12-21 00:22:39 UTC (rev 325)
@@ -82,10 +82,10 @@
 <A NAME=GraphSection></A>
 <A NAME=connects><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of connections attempted</H3>
-<IMG SRC=connects.png ALT="Connections/sec"></P>
+<IMG SRC=../connects.png ALT="Connections/sec"></P>
 <A NAME=connections><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Total connections</H3>
-<IMG SRC=connections.png ALT="Connections"></P>
+<IMG SRC=../connections.png ALT="Connections"></P>
 <A NAME=errors><HR SIZE=4 WIDTH="90%"></A>
 <BR>Graph "errors" contained no data (conn banner login logout).<BR>
 <A NAME=retrieves><HR SIZE=4 WIDTH="90%"></A>
@@ -92,25 +92,25 @@
 <BR>Graph "retrieves" contained no data (retrieve).<BR>
 <A NAME=submits><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of messages written</H3>
-<IMG SRC=submits.png ALT="Messages/sec"></P>
+<IMG SRC=../submits.png ALT="Messages/sec"></P>
 <A NAME=commands><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Protocol commands</H3>
-<IMG SRC=commands.png ALT="Commands/sec"></P>
+<IMG SRC=../commands.png ALT="Commands/sec"></P>
 <A NAME=readBytes><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Bytes read</H3>
-<IMG SRC=readBytes.png ALT="Bytes/sec"></P>
+<IMG SRC=../readBytes.png ALT="Bytes/sec"></P>
 <A NAME=writeBytes><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Bytes written</H3>
-<IMG SRC=writeBytes.png ALT="Bytes/sec"></P>
+<IMG SRC=../writeBytes.png ALT="Bytes/sec"></P>
 <A NAME=msgTime><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Message transfer time</H3>
-<IMG SRC=msgTime.png ALT="Seconds per message"></P>
+<IMG SRC=../msgTime.png ALT="Seconds per message"></P>
 <A NAME=setupTime><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Connection setup time</H3>
-<IMG SRC=setupTime.png ALT="Seconds per connection"></P>
+<IMG SRC=../setupTime.png ALT="Seconds per connection"></P>
 <A NAME=blocks><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of mstone blocks executed</H3>
-<IMG SRC=blocks.png ALT="Blocks/sec"></P>
+<IMG SRC=../blocks.png ALT="Blocks/sec"></P>
 <!-- INSERT IMAGES HERE - DO NOT DELETE THIS LINE -->
 </CENTER>
 <A NAME=EndSection></A>

Modified: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1959/results.html
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1959/results.html	2010-12-21 00:18:12 UTC (rev 324)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1959/results.html	2010-12-21 00:22:39 UTC (rev 325)
@@ -82,10 +82,10 @@
 <A NAME=GraphSection></A>
 <A NAME=connects><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of connections attempted</H3>
-<IMG SRC=connects.png ALT="Connections/sec"></P>
+<IMG SRC=../connects.png ALT="Connections/sec"></P>
 <A NAME=connections><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Total connections</H3>
-<IMG SRC=connections.png ALT="Connections"></P>
+<IMG SRC=../connections.png ALT="Connections"></P>
 <A NAME=errors><HR SIZE=4 WIDTH="90%"></A>
 <BR>Graph "errors" contained no data (conn banner login logout).<BR>
 <A NAME=retrieves><HR SIZE=4 WIDTH="90%"></A>
@@ -92,25 +92,25 @@
 <BR>Graph "retrieves" contained no data (retrieve).<BR>
 <A NAME=submits><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of messages written</H3>
-<IMG SRC=submits.png ALT="Messages/sec"></P>
+<IMG SRC=../submits.png ALT="Messages/sec"></P>
 <A NAME=commands><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Protocol commands</H3>
-<IMG SRC=commands.png ALT="Commands/sec"></P>
+<IMG SRC=../commands.png ALT="Commands/sec"></P>
 <A NAME=readBytes><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Bytes read</H3>
-<IMG SRC=readBytes.png ALT="Bytes/sec"></P>
+<IMG SRC=../readBytes.png ALT="Bytes/sec"></P>
 <A NAME=writeBytes><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Bytes written</H3>
-<IMG SRC=writeBytes.png ALT="Bytes/sec"></P>
+<IMG SRC=../writeBytes.png ALT="Bytes/sec"></P>
 <A NAME=msgTime><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Message transfer time</H3>
-<IMG SRC=msgTime.png ALT="Seconds per message"></P>
+<IMG SRC=../msgTime.png ALT="Seconds per message"></P>
 <A NAME=setupTime><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Connection setup time</H3>
-<IMG SRC=setupTime.png ALT="Seconds per connection"></P>
+<IMG SRC=../setupTime.png ALT="Seconds per connection"></P>
 <A NAME=blocks><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of mstone blocks executed</H3>
-<IMG SRC=blocks.png ALT="Blocks/sec"></P>
+<IMG SRC=../blocks.png ALT="Blocks/sec"></P>
 <!-- INSERT IMAGES HERE - DO NOT DELETE THIS LINE -->
 </CENTER>
 <A NAME=EndSection></A>

Modified: trunk/sysadmin/Projects/CMSEmail/Reports/20101216.1634/results.html
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101216.1634/results.html	2010-12-21 00:18:12 UTC (rev 324)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101216.1634/results.html	2010-12-21 00:22:39 UTC (rev 325)
@@ -82,10 +82,10 @@
 <A NAME=GraphSection></A>
 <A NAME=connects><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of connections attempted</H3>
-<IMG SRC=connects.png ALT="Connections/sec"></P>
+<IMG SRC=../connects.png ALT="Connections/sec"></P>
 <A NAME=connections><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Total connections</H3>
-<IMG SRC=connections.png ALT="Connections"></P>
+<IMG SRC=../connections.png ALT="Connections"></P>
 <A NAME=errors><HR SIZE=4 WIDTH="90%"></A>
 <BR>Graph "errors" contained no data (conn banner login logout).<BR>
 <A NAME=retrieves><HR SIZE=4 WIDTH="90%"></A>
@@ -92,25 +92,25 @@
 <BR>Graph "retrieves" contained no data (retrieve).<BR>
 <A NAME=submits><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of messages written</H3>
-<IMG SRC=submits.png ALT="Messages/sec"></P>
+<IMG SRC=../submits.png ALT="Messages/sec"></P>
 <A NAME=commands><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Protocol commands</H3>
-<IMG SRC=commands.png ALT="Commands/sec"></P>
+<IMG SRC=../commands.png ALT="Commands/sec"></P>
 <A NAME=readBytes><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Bytes read</H3>
-<IMG SRC=readBytes.png ALT="Bytes/sec"></P>
+<IMG SRC=../readBytes.png ALT="Bytes/sec"></P>
 <A NAME=writeBytes><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Bytes written</H3>
-<IMG SRC=writeBytes.png ALT="Bytes/sec"></P>
+<IMG SRC=../writeBytes.png ALT="Bytes/sec"></P>
 <A NAME=msgTime><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Message transfer time</H3>
-<IMG SRC=msgTime.png ALT="Seconds per message"></P>
+<IMG SRC=../msgTime.png ALT="Seconds per message"></P>
 <A NAME=setupTime><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Connection setup time</H3>
-<IMG SRC=setupTime.png ALT="Seconds per connection"></P>
+<IMG SRC=../setupTime.png ALT="Seconds per connection"></P>
 <A NAME=blocks><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of mstone blocks executed</H3>
-<IMG SRC=blocks.png ALT="Blocks/sec"></P>
+<IMG SRC=../blocks.png ALT="Blocks/sec"></P>
 <!-- INSERT IMAGES HERE - DO NOT DELETE THIS LINE -->
 </CENTER>
 <A NAME=EndSection></A>

Modified: trunk/sysadmin/Projects/CMSEmail/Reports/20101217.1254/results.html
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101217.1254/results.html	2010-12-21 00:18:12 UTC (rev 324)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101217.1254/results.html	2010-12-21 00:22:39 UTC (rev 325)
@@ -82,10 +82,10 @@
 <A NAME=GraphSection></A>
 <A NAME=connects><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of connections attempted</H3>
-<IMG SRC=connects.png ALT="Connections/sec"></P>
+<IMG SRC=../connects.png ALT="Connections/sec"></P>
 <A NAME=connections><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Total connections</H3>
-<IMG SRC=connections.png ALT="Connections"></P>
+<IMG SRC=../connections.png ALT="Connections"></P>
 <A NAME=errors><HR SIZE=4 WIDTH="90%"></A>
 <BR>Graph "errors" contained no data (conn banner login logout).<BR>
 <A NAME=retrieves><HR SIZE=4 WIDTH="90%"></A>
@@ -92,25 +92,25 @@
 <BR>Graph "retrieves" contained no data (retrieve).<BR>
 <A NAME=submits><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of messages written</H3>
-<IMG SRC=submits.png ALT="Messages/sec"></P>
+<IMG SRC=../submits.png ALT="Messages/sec"></P>
 <A NAME=commands><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Protocol commands</H3>
-<IMG SRC=commands.png ALT="Commands/sec"></P>
+<IMG SRC=../commands.png ALT="Commands/sec"></P>
 <A NAME=readBytes><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Bytes read</H3>
-<IMG SRC=readBytes.png ALT="Bytes/sec"></P>
+<IMG SRC=../readBytes.png ALT="Bytes/sec"></P>
 <A NAME=writeBytes><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Bytes written</H3>
-<IMG SRC=writeBytes.png ALT="Bytes/sec"></P>
+<IMG SRC=../writeBytes.png ALT="Bytes/sec"></P>
 <A NAME=msgTime><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Message transfer time</H3>
-<IMG SRC=msgTime.png ALT="Seconds per message"></P>
+<IMG SRC=../msgTime.png ALT="Seconds per message"></P>
 <A NAME=setupTime><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Connection setup time</H3>
-<IMG SRC=setupTime.png ALT="Seconds per connection"></P>
+<IMG SRC=../setupTime.png ALT="Seconds per connection"></P>
 <A NAME=blocks><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of mstone blocks executed</H3>
-<IMG SRC=blocks.png ALT="Blocks/sec"></P>
+<IMG SRC=../blocks.png ALT="Blocks/sec"></P>

(Diff truncated)
HASH(0x2f87b78)
Modified: trunk/sysadmin/Projects/CMSEmail/Reports/20101220.1347/results.html
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101220.1347/results.html	2010-12-21 01:18:54 UTC (rev 323)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101220.1347/results.html	2010-12-21 00:18:12 UTC (rev 324)
@@ -170,36 +170,36 @@
 <A NAME=GraphSection></A>
 <A NAME=connects><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of connections attempted</H3>
-<IMG SRC=connects.png ALT="Connections/sec"></P>
+<IMG SRC=../connects.png ALT="Connections/sec"></P>
 <A NAME=connections><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Total connections</H3>
-<IMG SRC=connections.png ALT="Connections"></P>
+<IMG SRC=../connections.png ALT="Connections"></P>
 <A NAME=errors><HR SIZE=4 WIDTH="90%"></A>
 <BR>Graph "errors" contained no data (conn banner login logout).<BR>
 <A NAME=retrieves><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of messages read</H3>
-<IMG SRC=retrieves.png ALT="Messages/sec"></P>
+<IMG SRC=../retrieves.png ALT="Messages/sec"></P>
 <A NAME=submits><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of messages written</H3>
-<IMG SRC=submits.png ALT="Messages/sec"></P>
+<IMG SRC=../submits.png ALT="Messages/sec"></P>
 <A NAME=commands><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Protocol commands</H3>
-<IMG SRC=commands.png ALT="Commands/sec"></P>
+<IMG SRC=../commands.png ALT="Commands/sec"></P>
 <A NAME=readBytes><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Bytes read</H3>
-<IMG SRC=readBytes.png ALT="Bytes/sec"></P>
+<IMG SRC=../readBytes.png ALT="Bytes/sec"></P>
 <A NAME=writeBytes><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Bytes written</H3>
-<IMG SRC=writeBytes.png ALT="Bytes/sec"></P>
+<IMG SRC=../writeBytes.png ALT="Bytes/sec"></P>
 <A NAME=msgTime><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Message transfer time</H3>
-<IMG SRC=msgTime.png ALT="Seconds per message"></P>
+<IMG SRC=../msgTime.png ALT="Seconds per message"></P>
 <A NAME=setupTime><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Connection setup time</H3>
-<IMG SRC=setupTime.png ALT="Seconds per connection"></P>
+<IMG SRC=../setupTime.png ALT="Seconds per connection"></P>
 <A NAME=blocks><HR SIZE=4 WIDTH="90%"></A>
 <P><H3>Number of mstone blocks executed</H3>
-<IMG SRC=blocks.png ALT="Blocks/sec"></P>
+<IMG SRC=../blocks.png ALT="Blocks/sec"></P>
 <!-- INSERT IMAGES HERE - DO NOT DELETE THIS LINE -->
 </CENTER>
 <A NAME=EndSection></A>


HASH(0x2f890c8)
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/all.wld
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/all.wld	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/all.wld	2010-12-21 00:15:09 UTC (rev 322)
@@ -0,0 +1,79 @@
+<CONFIG>
+  blockID	1
+  clientCount	20
+  comments	SMTP send 1K mesg
+  frequency	7
+  NOEVENTS	0
+  rampTime	20s
+  sysConfig	conf/smtp.html
+  telemetry	1
+  TESTNAME	smtp
+  time	1h
+  title	SMTP message deliveries (no encryption)
+  TStamp	20101215.1803
+  workload	conf/smtp.wld
+</CONFIG>
+
+<MONITOR>
+  name          vmstat.txt
+  command       vmstat %f
+  process       conf/clean_vmstat.pl
+  blockID	2
+
+</MONITOR>
+
+<PRETEST>
+  name    preifconfig.txt
+  command	ifconfig
+  blockID	3
+
+</PRETEST>
+
+<POSTTEST>
+  name 		ifconfig.txt
+  command	ifconfig; uname -a
+  process       conf/clean_ifconfig.pl
+  blockID	4
+
+</POSTTEST>
+
+<DEFAULT>
+  loginFormat	testuser%ld
+  passwdFormat	P@ssw0rd
+  numLogins		0
+  firstLogin	0
+  server	napoleon.cms.caltech.edu
+  smtpMailFrom	testuser0@napoleon.cms.caltech.edu
+  addressFormat	testuser%ld@napoleon.cms.caltech.edu
+  numAddresses	4
+  firstAddress	0
+  blockID	5
+
+</DEFAULT>
+
+<CLIENT HOSTS=localhost>
+  blockID	6
+  maxThreads	1
+  processes	4
+  threads	1
+</CLIENT>
+
+<CLIENT HOSTS=daemon,halo,trebuchet,uranus>
+  blockID	7
+  processes	1
+  threads	4
+</CLIENT>
+
+<SMTP>
+  weight	100
+  useEHLO	1
+  file		en-1k.msg
+  numRecips	1
+  numLoops	1
+  numAddresses	2
+  smtpMailFrom	testuser0@cms.caltech.edu
+  addressFormat	testuser%ld@cms.caltech.edu
+  blockID	8
+
+</SMTP>
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/blocks.png
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/blocks.png
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/blocks.png	2010-12-18 02:11:49 UTC (rev 321)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/blocks.png	2010-12-21 00:15:09 UTC (rev 322)

Property changes on: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/blocks.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-daemon.csv
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-daemon.csv	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-daemon.csv	2010-12-21 00:15:09 UTC (rev 322)
@@ -0,0 +1,3 @@
+client,time,blocks,SMTP:blocks,SMTP:total:Try,SMTP:total:Error,SMTP:total:BytesR,SMTP:total:BytesW,SMTP:total:Time,SMTP:total:TimeMin,SMTP:total:TimeMax,SMTP:total:Time2,SMTP:conn:Try,SMTP:conn:Error,SMTP:conn:BytesR,SMTP:conn:BytesW,SMTP:conn:Time,SMTP:conn:TimeMin,SMTP:conn:TimeMax,SMTP:conn:Time2,SMTP:banner:Try,SMTP:banner:Error,SMTP:banner:BytesR,SMTP:banner:BytesW,SMTP:banner:Time,SMTP:banner:TimeMin,SMTP:banner:TimeMax,SMTP:banner:Time2,SMTP:login:Try,SMTP:login:Error,SMTP:login:BytesR,SMTP:login:BytesW,SMTP:login:Time,SMTP:login:TimeMin,SMTP:login:TimeMax,SMTP:login:Time2,SMTP:cmd:Try,SMTP:cmd:Error,SMTP:cmd:BytesR,SMTP:cmd:BytesW,SMTP:cmd:Time,SMTP:cmd:TimeMin,SMTP:cmd:TimeMax,SMTP:cmd:Time2,SMTP:submit:Try,SMTP:submit:Error,SMTP:submit:BytesR,SMTP:submit:BytesW,SMTP:submit:Time,SMTP:submit:TimeMin,SMTP:submit:TimeMax,SMTP:submit:Time2,SMTP:retrieve:Try,SMTP:retrieve:Error,SMTP:retrieve:BytesR,SMTP:retrieve:BytesW,SMTP:retrieve:Time,SMTP:retrieve:TimeMin,SMTP:retrieve:TimeMax,SMTP:retrieve:Time2,SMTP:logout:Try,SMTP:logout:Error,SMTP:logout:BytesR,SMTP:logout:BytesW,SMTP:logout:Time,SMTP:logout:TimeMin,SMTP:logout:TimeMax,SMTP:logout:Time2,SMTP:idle:Try,SMTP:idle:Error,SMTP:idle:BytesR,SMTP:idle:BytesW,SMTP:idle:Time,SMTP:idle:TimeMin,SMTP:idle:TimeMax,SMTP:idle:Time2,
+0,1292468605,5854,5858,64432,0,990002,6601966,14365.046089,0.000005,2.125077,18261.252056,5858,0,0,0,17.372933,0.000128,0.010509,0.054915,5858,0,304616,0,1.301012,0.000005,0.020677,0.009822,0,0,0,0,0.0,0,0.0,0.0,23432,0,380770,556510,7769.773397,0.000197,2.125077,10449.454229,5858,0,216746,6010308,6558.560337,0.068975,1.528973,7811.667694,0,0,0,0,0.0,0,0.0,0.0,5856,0,87840,35136,17.887418,0.000220,0.044005,0.065376,17570,0,30,12,0.150992,0.000006,0.003028,0.000019,
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-halo.csv
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-halo.csv	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-halo.csv	2010-12-21 00:15:09 UTC (rev 322)
@@ -0,0 +1,3 @@
+client,time,blocks,SMTP:blocks,SMTP:total:Try,SMTP:total:Error,SMTP:total:BytesR,SMTP:total:BytesW,SMTP:total:Time,SMTP:total:TimeMin,SMTP:total:TimeMax,SMTP:total:Time2,SMTP:conn:Try,SMTP:conn:Error,SMTP:conn:BytesR,SMTP:conn:BytesW,SMTP:conn:Time,SMTP:conn:TimeMin,SMTP:conn:TimeMax,SMTP:conn:Time2,SMTP:banner:Try,SMTP:banner:Error,SMTP:banner:BytesR,SMTP:banner:BytesW,SMTP:banner:Time,SMTP:banner:TimeMin,SMTP:banner:TimeMax,SMTP:banner:Time2,SMTP:login:Try,SMTP:login:Error,SMTP:login:BytesR,SMTP:login:BytesW,SMTP:login:Time,SMTP:login:TimeMin,SMTP:login:TimeMax,SMTP:login:Time2,SMTP:cmd:Try,SMTP:cmd:Error,SMTP:cmd:BytesR,SMTP:cmd:BytesW,SMTP:cmd:Time,SMTP:cmd:TimeMin,SMTP:cmd:TimeMax,SMTP:cmd:Time2,SMTP:submit:Try,SMTP:submit:Error,SMTP:submit:BytesR,SMTP:submit:BytesW,SMTP:submit:Time,SMTP:submit:TimeMin,SMTP:submit:TimeMax,SMTP:submit:Time2,SMTP:retrieve:Try,SMTP:retrieve:Error,SMTP:retrieve:BytesR,SMTP:retrieve:BytesW,SMTP:retrieve:Time,SMTP:retrieve:TimeMin,SMTP:retrieve:TimeMax,SMTP:retrieve:Time2,SMTP:logout:Try,SMTP:logout:Error,SMTP:logout:BytesR,SMTP:logout:BytesW,SMTP:logout:Time,SMTP:logout:TimeMin,SMTP:logout:TimeMax,SMTP:logout:Time2,SMTP:idle:Try,SMTP:idle:Error,SMTP:idle:BytesR,SMTP:idle:BytesW,SMTP:idle:Time,SMTP:idle:TimeMin,SMTP:idle:TimeMax,SMTP:idle:Time2,
+0,1292468630,5812,5816,63976,0,982964,6543024,14375.285752,0.000003,2.153906,18274.047658,5816,0,0,0,14.723457,0.000162,0.044084,0.218088,5816,0,302432,0,31.804170,0.000004,0.056994,0.626004,0,0,0,0,0.0,0,0.0,0.0,23264,0,378040,540888,7808.094903,0.000220,2.153906,10516.237054,5816,0,215192,5967216,6508.123397,0.068975,1.524912,7756.812922,0,0,0,0,0.0,0,0.0,0.0,5816,0,87240,34896,12.450434,0.000310,0.051009,0.153585,17448,0,60,24,0.089391,0.000003,0.001175,0.000005,
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-localhost.csv
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-localhost.csv	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-localhost.csv	2010-12-21 00:15:09 UTC (rev 322)
@@ -0,0 +1,6 @@
+client,time,blocks,SMTP:blocks,SMTP:total:Try,SMTP:total:Error,SMTP:total:BytesR,SMTP:total:BytesW,SMTP:total:Time,SMTP:total:TimeMin,SMTP:total:TimeMax,SMTP:total:Time2,SMTP:conn:Try,SMTP:conn:Error,SMTP:conn:BytesR,SMTP:conn:BytesW,SMTP:conn:Time,SMTP:conn:TimeMin,SMTP:conn:TimeMax,SMTP:conn:Time2,SMTP:banner:Try,SMTP:banner:Error,SMTP:banner:BytesR,SMTP:banner:BytesW,SMTP:banner:Time,SMTP:banner:TimeMin,SMTP:banner:TimeMax,SMTP:banner:Time2,SMTP:login:Try,SMTP:login:Error,SMTP:login:BytesR,SMTP:login:BytesW,SMTP:login:Time,SMTP:login:TimeMin,SMTP:login:TimeMax,SMTP:login:Time2,SMTP:cmd:Try,SMTP:cmd:Error,SMTP:cmd:BytesR,SMTP:cmd:BytesW,SMTP:cmd:Time,SMTP:cmd:TimeMin,SMTP:cmd:TimeMax,SMTP:cmd:Time2,SMTP:submit:Try,SMTP:submit:Error,SMTP:submit:BytesR,SMTP:submit:BytesW,SMTP:submit:Time,SMTP:submit:TimeMin,SMTP:submit:TimeMax,SMTP:submit:Time2,SMTP:retrieve:Try,SMTP:retrieve:Error,SMTP:retrieve:BytesR,SMTP:retrieve:BytesW,SMTP:retrieve:Time,SMTP:retrieve:TimeMin,SMTP:retrieve:TimeMax,SMTP:retrieve:Time2,SMTP:logout:Try,SMTP:logout:Error,SMTP:logout:BytesR,SMTP:logout:BytesW,SMTP:logout:Time,SMTP:logout:TimeMin,SMTP:logout:TimeMax,SMTP:logout:Time2,SMTP:idle:Try,SMTP:idle:Error,SMTP:idle:BytesR,SMTP:idle:BytesW,SMTP:idle:Time,SMTP:idle:TimeMin,SMTP:idle:TimeMax,SMTP:idle:Time2,
+0,1292468628,1472,1473,16203,0,248952,1661550,3584.558148,0.000005,2.069600,4573.977306,1473,0,0,0,0.376826,0.000149,0.003522,0.000168,1473,0,76596,0,2.031473,0.000008,0.016915,0.005381,0,0,0,0,0.0,0,0.0,0.0,5892,0,95745,141408,1931.291273,0.000201,2.069600,2604.852732,1473,0,54501,1511298,1650.174268,0.070664,1.505439,1969.118504,0,0,0,0,0.0,0,0.0,0.0,1473,0,22095,8838,0.638803,0.000247,0.009379,0.000521,4419,0,15,6,0.045505,0.000005,0.000379,0.000001,
+1,1292468629,1463,1464,16104,0,247431,1651398,3583.663968,0.000005,2.126148,4590.923521,1464,0,0,0,0.362220,0.000152,0.002104,0.000126,1464,0,76128,0,2.015708,0.000008,0.013662,0.004942,0,0,0,0,0.0,0,0.0,0.0,5856,0,95160,140544,1935.566927,0.000204,2.126148,2622.432600,1464,0,54168,1502064,1645.045243,0.068121,1.546547,1968.485458,0,0,0,0,0.0,0,0.0,0.0,1464,0,21960,8784,0.628274,0.000253,0.004849,0.000395,4392,0,15,6,0.045596,0.000005,0.000395,0.000001,
+2,1292468631,1462,1463,16090,0,247232,1650258,3581.998272,0.000005,2.376984,4589.276681,1463,0,0,0,0.360852,0.000156,0.002347,0.000126,1463,0,76076,0,2.012381,0.000010,0.014218,0.004853,0,0,0,0,0.0,0,0.0,0.0,5852,0,95095,140448,1933.885420,0.000199,2.376984,2624.886498,1463,0,54131,1501038,1645.085677,0.071399,1.568579,1964.384870,0,0,0,0,0.0,0,0.0,0.0,1462,0,21930,8772,0.608408,0.000250,0.003247,0.000333,4387,0,0,0,0.045534,0.000005,0.000550,0.000001,
+3,1292468632,1457,1458,16038,0,246417,1644630,3580.225050,0.000005,2.092851,4593.361990,1458,0,0,0,0.365260,0.000147,0.002893,0.000138,1458,0,75816,0,1.999655,0.000006,0.015053,0.004885,0,0,0,0,0.0,0,0.0,0.0,5832,0,94770,139968,1934.911362,0.000204,2.092851,2631.846015,1458,0,53946,1495908,1642.279733,0.066279,1.454164,1961.510516,0,0,0,0,0.0,0,0.0,0.0,1458,0,21870,8748,0.623336,0.000246,0.009191,0.000435,4374,0,15,6,0.045704,0.000005,0.000455,0.000001,
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-trebuchet.csv
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-trebuchet.csv	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-trebuchet.csv	2010-12-21 00:15:09 UTC (rev 322)
@@ -0,0 +1,3 @@
+client,time,blocks,SMTP:blocks,SMTP:total:Try,SMTP:total:Error,SMTP:total:BytesR,SMTP:total:BytesW,SMTP:total:Time,SMTP:total:TimeMin,SMTP:total:TimeMax,SMTP:total:Time2,SMTP:conn:Try,SMTP:conn:Error,SMTP:conn:BytesR,SMTP:conn:BytesW,SMTP:conn:Time,SMTP:conn:TimeMin,SMTP:conn:TimeMax,SMTP:conn:Time2,SMTP:banner:Try,SMTP:banner:Error,SMTP:banner:BytesR,SMTP:banner:BytesW,SMTP:banner:Time,SMTP:banner:TimeMin,SMTP:banner:TimeMax,SMTP:banner:Time2,SMTP:login:Try,SMTP:login:Error,SMTP:login:BytesR,SMTP:login:BytesW,SMTP:login:Time,SMTP:login:TimeMin,SMTP:login:TimeMax,SMTP:login:Time2,SMTP:cmd:Try,SMTP:cmd:Error,SMTP:cmd:BytesR,SMTP:cmd:BytesW,SMTP:cmd:Time,SMTP:cmd:TimeMin,SMTP:cmd:TimeMax,SMTP:cmd:Time2,SMTP:submit:Try,SMTP:submit:Error,SMTP:submit:BytesR,SMTP:submit:BytesW,SMTP:submit:Time,SMTP:submit:TimeMin,SMTP:submit:TimeMax,SMTP:submit:Time2,SMTP:retrieve:Try,SMTP:retrieve:Error,SMTP:retrieve:BytesR,SMTP:retrieve:BytesW,SMTP:retrieve:Time,SMTP:retrieve:TimeMin,SMTP:retrieve:TimeMax,SMTP:retrieve:Time2,SMTP:logout:Try,SMTP:logout:Error,SMTP:logout:BytesR,SMTP:logout:BytesW,SMTP:logout:Time,SMTP:logout:TimeMin,SMTP:logout:TimeMax,SMTP:logout:Time2,SMTP:idle:Try,SMTP:idle:Error,SMTP:idle:BytesR,SMTP:idle:BytesW,SMTP:idle:Time,SMTP:idle:TimeMin,SMTP:idle:TimeMax,SMTP:idle:Time2,
+0,1292468731,5897,5901,64905,0,997269,6668130,14376.069943,0.000002,2.261932,18297.005276,5901,0,0,0,16.256375,0.000119,0.011661,0.047259,5901,0,306852,0,1.412740,0.000002,0.027999,0.011342,0,0,0,0,0.0,0,0.0,0.0,23604,0,383565,578298,7776.704563,0.000154,2.261932,10480.598788,5901,0,218337,6054426,6565.806475,0.066990,1.560993,7816.302129,0,0,0,0,0.0,0,0.0,0.0,5899,0,88485,35394,15.828476,0.000177,0.013001,0.045741,17699,0,30,12,0.061314,0.000002,0.003009,0.000018,
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-uranus.csv
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-uranus.csv	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/clients-uranus.csv	2010-12-21 00:15:09 UTC (rev 322)
@@ -0,0 +1,3 @@
+client,time,blocks,SMTP:blocks,SMTP:total:Try,SMTP:total:Error,SMTP:total:BytesR,SMTP:total:BytesW,SMTP:total:Time,SMTP:total:TimeMin,SMTP:total:TimeMax,SMTP:total:Time2,SMTP:conn:Try,SMTP:conn:Error,SMTP:conn:BytesR,SMTP:conn:BytesW,SMTP:conn:Time,SMTP:conn:TimeMin,SMTP:conn:TimeMax,SMTP:conn:Time2,SMTP:banner:Try,SMTP:banner:Error,SMTP:banner:BytesR,SMTP:banner:BytesW,SMTP:banner:Time,SMTP:banner:TimeMin,SMTP:banner:TimeMax,SMTP:banner:Time2,SMTP:login:Try,SMTP:login:Error,SMTP:login:BytesR,SMTP:login:BytesW,SMTP:login:Time,SMTP:login:TimeMin,SMTP:login:TimeMax,SMTP:login:Time2,SMTP:cmd:Try,SMTP:cmd:Error,SMTP:cmd:BytesR,SMTP:cmd:BytesW,SMTP:cmd:Time,SMTP:cmd:TimeMin,SMTP:cmd:TimeMax,SMTP:cmd:Time2,SMTP:submit:Try,SMTP:submit:Error,SMTP:submit:BytesR,SMTP:submit:BytesW,SMTP:submit:Time,SMTP:submit:TimeMin,SMTP:submit:TimeMax,SMTP:submit:Time2,SMTP:retrieve:Try,SMTP:retrieve:Error,SMTP:retrieve:BytesR,SMTP:retrieve:BytesW,SMTP:retrieve:Time,SMTP:retrieve:TimeMin,SMTP:retrieve:TimeMax,SMTP:retrieve:Time2,SMTP:logout:Try,SMTP:logout:Error,SMTP:logout:BytesR,SMTP:logout:BytesW,SMTP:logout:Time,SMTP:logout:TimeMin,SMTP:logout:TimeMax,SMTP:logout:Time2,SMTP:idle:Try,SMTP:idle:Error,SMTP:idle:BytesR,SMTP:idle:BytesW,SMTP:idle:Time,SMTP:idle:TimeMin,SMTP:idle:TimeMax,SMTP:idle:Time2,
+0,1292468585,5861,5865,64515,0,991245,6609879,14371.395616,0.000003,2.270999,18288.829889,5865,0,0,0,17.742984,0.000153,0.007903,0.070856,5865,0,304980,0,7.599919,0.000003,0.025999,0.036860,0,0,0,0,0.0,0,0.0,0.0,23460,0,381225,557175,7765.624958,0.000208,2.270999,10460.128253,5865,0,217005,6017490,6566.159100,0.072981,1.552982,7828.439890,0,0,0,0,0.0,0,0.0,0.0,5865,0,87975,35190,14.174060,0.000237,0.178075,0.154009,17595,0,60,24,0.094595,0.000003,0.003020,0.000021,
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/commands.png
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/commands.png
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/commands.png	2010-12-18 02:11:49 UTC (rev 321)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/commands.png	2010-12-21 00:15:09 UTC (rev 322)

Property changes on: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/commands.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/connections.png
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/connections.png
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/connections.png	2010-12-18 02:11:49 UTC (rev 321)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/connections.png	2010-12-21 00:15:09 UTC (rev 322)

Property changes on: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/connections.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/connects.png
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/connects.png
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/connects.png	2010-12-18 02:11:49 UTC (rev 321)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/connects.png	2010-12-21 00:15:09 UTC (rev 322)

Property changes on: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/connects.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/daemon-ifconfig.txt
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/daemon-ifconfig.txt	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101215.1803/daemon-ifconfig.txt	2010-12-21 00:15:09 UTC (rev 322)
@@ -0,0 +1,17 @@
+========
+= ifconfig; uname -a =

(Diff truncated)
Modified: trunk/sysadmin/Projects/CMSEmail.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail.mdwn	2010-12-15 02:35:33 UTC (rev 320)
+++ trunk/sysadmin/Projects/CMSEmail.mdwn	2010-12-18 02:11:49 UTC (rev 321)
@@ -57,6 +57,13 @@
     info AT cms.caltech.edu           -> sheila AT acm.caltech.edu
 
 ***
+### 17 Dec 2010
+As testing continues, a few glitches were discovered:
+
+ - The `ldap-sympa.cf` transport map was corrected to accurately reflect the objectclass/attributes used.
+ - In MAIA, if the domain is set to quarantine spam by default, SPAM gets blocked, however the **recipient has NO QUARANTINE until AFTER the user account is created** in Maia.
+
+***
 ### 14 Dec 2010
 Maia virus/spam scanner connected to Postfix MTA (NAPOLEON.CMS.CALTECH.EDU) complete.
 


Modified: trunk/sysadmin/Projects/CMSEmail.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail.mdwn	2010-12-13 20:11:31 UTC (rev 319)
+++ trunk/sysadmin/Projects/CMSEmail.mdwn	2010-12-15 02:35:33 UTC (rev 320)
@@ -57,6 +57,41 @@
     info AT cms.caltech.edu           -> sheila AT acm.caltech.edu
 
 ***
+### 14 Dec 2010
+Maia virus/spam scanner connected to Postfix MTA (NAPOLEON.CMS.CALTECH.EDU) complete.
+
+Initial test (ham) messages passed through and delivered to user, `~/Maildir`.
+
+Initial test (spam) message held for quarantine per user preference.
+
+Rigorous testing commencing:
+
+  - SMTP message sent to NAPOLEON.CMS port 25
+  - message FROM random `testuser[0-3]@cms.caltech.edu`
+  - message TO random `testuser[0-3]@cms.caltech.edu`
+  - message passed to LEE.CMS.CALTECH.EDU (MAIA) for scanning
+  - message passed back to NAPOLEON for delivery
+
+Next test phases:
+
+  - SMTP message -> MAIA -> Sympa mailing list
+  - SMTP message -> MAIA -> Sympa mailing list -> IMAP read
+
+***
+### 13 Dec 2010
+Web interface for virus/spam scanner [Maia](https://maia.cms.caltech.edu) completed.
+
+Still ToDo:  connect scanner to mail system (at NAPOLEON.CMS.CALTECH.EDU)
+
+***
+### 10 Dec 2010
+Completed installation of mailing list manager [Sympa](https://sympa.cms.caltech.edu)
+Initial testing done with test mail list(s) and test user(s).
+
+All aliases for mailing lists are stored in LDAP,
+`ou=Sympa,ou=Aliases,ou=CMS,o=Caltech,c=US`.
+
+***
 ### 7 Dec 2010
 Testing reports have completed.  These values represent the baseline
 performance of both the MTA (SMTP) and IMAP servers.


HASH(0x2fde398)
Modified: trunk/sysadmin/Projects/CMSEmail.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail.mdwn	2010-12-08 00:06:53 UTC (rev 318)
+++ trunk/sysadmin/Projects/CMSEmail.mdwn	2010-12-13 20:11:31 UTC (rev 319)
@@ -57,7 +57,14 @@
     info AT cms.caltech.edu           -> sheila AT acm.caltech.edu
 
 ***
+### 7 Dec 2010
+Testing reports have completed.  These values represent the baseline
+performance of both the MTA (SMTP) and IMAP servers.
 
+[Reports](Reports)
+
+***
+
 ### 30 Nov 2010
 It came to light that SMTP-AUTH follows shadow functionality, meaning basically that when a user's password expires they are no longer able to authenticate via SMTP.
 This fails without user recourse as there is no mechanism to output a meaningful error to the SMTP client user.


automatic index generation
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446.mdwn
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446.mdwn	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446.mdwn	2010-12-08 01:09:09 UTC (rev 317)
@@ -0,0 +1 @@
+[[!map pages="sysadmin/Projects/CMSEmail/Reports/20101207.1446/* and ! sysadmin/Projects/CMSEmail/Reports/20101207.1446/*/*"]]


HASH(0x2fde4d0)
Modified: trunk/sysadmin/Projects/CMSEmail/Reports.html
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports.html	2010-12-08 01:09:09 UTC (rev 317)
+++ trunk/sysadmin/Projects/CMSEmail/Reports.html	2010-12-08 00:06:53 UTC (rev 318)
@@ -19,7 +19,7 @@
 <TD>100</TD>
 <TD><A HREF="20101207.1446/all.wld">workload</A></TD>
 <TD><A HREF="20101207.1446/stderr">stderr</A></TD></TR>
-<TR><TD><BR><A HREF="20101207.1446/results">20101207.1446</A></TD><TD>imap</TD>
+<TR><TD><BR><A HREF="20101203.1537/results">20101203.1537</A></TD><TD>imap</TD>
 <TD>IMAP reads (no encryption)</TD>
 <TD>1h</TD>
 <TD>100</TD>


HASH(0x2fdee60)
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/all.wld
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/all.wld	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/all.wld	2010-12-08 00:05:44 UTC (rev 316)
@@ -0,0 +1,81 @@
+<CONFIG>
+  blockID	1
+  clientCount	100
+  comments	IMAP: login, list, read, mark deleted, logout
+  frequency	7
+  NOEVENTS	0
+  rampTime	30s
+  telemetry	1
+  TESTNAME	imap
+  time	1h
+  title	IMAP reads (no encryption)
+  TStamp	20101207.1446
+  workload	conf/imap.wld
+</CONFIG>
+
+<MONITOR>
+  name          vmstat.txt
+  command       vmstat %f
+  process       conf/clean_vmstat.pl
+  blockID	2
+
+</MONITOR>
+
+<PRETEST>
+  name    preifconfig.txt
+  command	ifconfig
+  blockID	3
+
+</PRETEST>
+
+<POSTTEST>
+  name 		ifconfig.txt
+  command	ifconfig; uname -a
+  process       conf/clean_ifconfig.pl
+  blockID	4
+
+</POSTTEST>
+
+<DEFAULT>
+  loginFormat	testuser%ld
+  passwdFormat	P@ssw0rd
+  numLogins		0
+  firstLogin	0
+  server	napoleon.cms.caltech.edu
+  smtpMailFrom	testuser0@napoleon.cms.caltech.edu
+  addressFormat	testuser%ld@napoleon.cms.caltech.edu
+  numAddresses	4
+  firstAddress	0
+  blockID	5
+
+</DEFAULT>
+
+<CLIENT HOSTS=localhost>
+  blockID	6
+  maxThreads	1
+  processes	20
+  threads	1
+</CLIENT>
+
+<CLIENT HOSTS=daemon,halo,trebuchet,uranus>
+  blockID	7
+  processes	1
+  threads	20
+</CLIENT>
+
+<IMAP4>
+  weight	100
+  server 	imap.cms.caltech.edu
+  leaveMailOnServer	0
+  idleTime	1s
+  loopDelay	1m
+  numLogins	4
+  firstLogin	0
+  loginFormat	testuser%ld
+  passwdFormat	P@ssw0rd
+  numLoops	10
+  blockTime	2s
+  blockID	8
+
+</IMAP4>
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/blocks.png
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/blocks.png
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/blocks.png	2010-12-07 22:28:37 UTC (rev 315)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/blocks.png	2010-12-08 00:05:44 UTC (rev 316)

Property changes on: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/blocks.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-daemon.csv
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-daemon.csv	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-daemon.csv	2010-12-08 00:05:44 UTC (rev 316)
@@ -0,0 +1,3 @@
+client,time,blocks,IMAP4:blocks,IMAP4:total:Try,IMAP4:total:Error,IMAP4:total:BytesR,IMAP4:total:BytesW,IMAP4:total:Time,IMAP4:total:TimeMin,IMAP4:total:TimeMax,IMAP4:total:Time2,IMAP4:conn:Try,IMAP4:conn:Error,IMAP4:conn:BytesR,IMAP4:conn:BytesW,IMAP4:conn:Time,IMAP4:conn:TimeMin,IMAP4:conn:TimeMax,IMAP4:conn:Time2,IMAP4:banner:Try,IMAP4:banner:Error,IMAP4:banner:BytesR,IMAP4:banner:BytesW,IMAP4:banner:Time,IMAP4:banner:TimeMin,IMAP4:banner:TimeMax,IMAP4:banner:Time2,IMAP4:login:Try,IMAP4:login:Error,IMAP4:login:BytesR,IMAP4:login:BytesW,IMAP4:login:Time,IMAP4:login:TimeMin,IMAP4:login:TimeMax,IMAP4:login:Time2,IMAP4:cmd:Try,IMAP4:cmd:Error,IMAP4:cmd:BytesR,IMAP4:cmd:BytesW,IMAP4:cmd:Time,IMAP4:cmd:TimeMin,IMAP4:cmd:TimeMax,IMAP4:cmd:Time2,IMAP4:submit:Try,IMAP4:submit:Error,IMAP4:submit:BytesR,IMAP4:submit:BytesW,IMAP4:submit:Time,IMAP4:submit:TimeMin,IMAP4:submit:TimeMax,IMAP4:submit:Time2,IMAP4:retrieve:Try,IMAP4:retrieve:Error,IMAP4:retrieve:BytesR,IMAP4:retrieve:BytesW,IMAP4:retrieve:Time,IMAP4:retrieve:TimeMin,IMAP4:retrieve:TimeMax,IMAP4:retrieve:Time2,IMAP4:logout:Try,IMAP4:logout:Error,IMAP4:logout:BytesR,IMAP4:logout:BytesW,IMAP4:logout:Time,IMAP4:logout:TimeMin,IMAP4:logout:TimeMax,IMAP4:logout:Time2,IMAP4:idle:Try,IMAP4:idle:Error,IMAP4:idle:BytesR,IMAP4:idle:BytesW,IMAP4:idle:Time,IMAP4:idle:TimeMin,IMAP4:idle:TimeMax,IMAP4:idle:Time2,
+0,1291765555,100,120,3160,0,93160,16380,70920.503395,0.000005,59.940637,4237477.247425,120,0,0,0,0.021302,0.000140,0.000272,0.000004,120,0,29040,0,0.143521,0.001013,0.001478,0.000173,120,0,1920,3360,0.447728,0.003083,0.010898,0.001862,1300,0,55700,11920,89.388532,0.003340,0.176191,6.995398,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,100,0,6500,1100,0.023117,0.000174,0.000406,0.000005,1400,0,0,0,70830.479195,0.000005,59.940637,4237470.249984,
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-halo.csv
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-halo.csv	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-halo.csv	2010-12-08 00:05:44 UTC (rev 316)
@@ -0,0 +1,3 @@
+client,time,blocks,IMAP4:blocks,IMAP4:total:Try,IMAP4:total:Error,IMAP4:total:BytesR,IMAP4:total:BytesW,IMAP4:total:Time,IMAP4:total:TimeMin,IMAP4:total:TimeMax,IMAP4:total:Time2,IMAP4:conn:Try,IMAP4:conn:Error,IMAP4:conn:BytesR,IMAP4:conn:BytesW,IMAP4:conn:Time,IMAP4:conn:TimeMin,IMAP4:conn:TimeMax,IMAP4:conn:Time2,IMAP4:banner:Try,IMAP4:banner:Error,IMAP4:banner:BytesR,IMAP4:banner:BytesW,IMAP4:banner:Time,IMAP4:banner:TimeMin,IMAP4:banner:TimeMax,IMAP4:banner:Time2,IMAP4:login:Try,IMAP4:login:Error,IMAP4:login:BytesR,IMAP4:login:BytesW,IMAP4:login:Time,IMAP4:login:TimeMin,IMAP4:login:TimeMax,IMAP4:login:Time2,IMAP4:cmd:Try,IMAP4:cmd:Error,IMAP4:cmd:BytesR,IMAP4:cmd:BytesW,IMAP4:cmd:Time,IMAP4:cmd:TimeMin,IMAP4:cmd:TimeMax,IMAP4:cmd:Time2,IMAP4:submit:Try,IMAP4:submit:Error,IMAP4:submit:BytesR,IMAP4:submit:BytesW,IMAP4:submit:Time,IMAP4:submit:TimeMin,IMAP4:submit:TimeMax,IMAP4:submit:Time2,IMAP4:retrieve:Try,IMAP4:retrieve:Error,IMAP4:retrieve:BytesR,IMAP4:retrieve:BytesW,IMAP4:retrieve:Time,IMAP4:retrieve:TimeMin,IMAP4:retrieve:TimeMax,IMAP4:retrieve:Time2,IMAP4:logout:Try,IMAP4:logout:Error,IMAP4:logout:BytesR,IMAP4:logout:BytesW,IMAP4:logout:Time,IMAP4:logout:TimeMin,IMAP4:logout:TimeMax,IMAP4:logout:Time2,IMAP4:idle:Try,IMAP4:idle:Error,IMAP4:idle:BytesR,IMAP4:idle:BytesW,IMAP4:idle:Time,IMAP4:idle:TimeMin,IMAP4:idle:TimeMax,IMAP4:idle:Time2,
+0,1291765563,100,120,3160,0,93160,16380,70920.854792,0.000004,59.940755,4239012.768889,120,0,0,0,0.029626,0.000120,0.010636,0.000116,120,0,29040,0,0.147516,0.000012,0.001529,0.000183,120,0,1920,3360,0.494170,0.002986,0.056263,0.005045,1300,0,55700,11920,76.864161,0.003363,0.092964,4.888989,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,100,0,6500,1100,0.019576,0.000159,0.000297,0.000004,1400,0,0,0,70843.299743,0.000004,59.940755,4239007.874552,
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-localhost.csv
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-localhost.csv	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-localhost.csv	2010-12-08 00:05:44 UTC (rev 316)
@@ -0,0 +1,22 @@
+client,time,blocks,IMAP4:blocks,IMAP4:total:Try,IMAP4:total:Error,IMAP4:total:BytesR,IMAP4:total:BytesW,IMAP4:total:Time,IMAP4:total:TimeMin,IMAP4:total:TimeMax,IMAP4:total:Time2,IMAP4:conn:Try,IMAP4:conn:Error,IMAP4:conn:BytesR,IMAP4:conn:BytesW,IMAP4:conn:Time,IMAP4:conn:TimeMin,IMAP4:conn:TimeMax,IMAP4:conn:Time2,IMAP4:banner:Try,IMAP4:banner:Error,IMAP4:banner:BytesR,IMAP4:banner:BytesW,IMAP4:banner:Time,IMAP4:banner:TimeMin,IMAP4:banner:TimeMax,IMAP4:banner:Time2,IMAP4:login:Try,IMAP4:login:Error,IMAP4:login:BytesR,IMAP4:login:BytesW,IMAP4:login:Time,IMAP4:login:TimeMin,IMAP4:login:TimeMax,IMAP4:login:Time2,IMAP4:cmd:Try,IMAP4:cmd:Error,IMAP4:cmd:BytesR,IMAP4:cmd:BytesW,IMAP4:cmd:Time,IMAP4:cmd:TimeMin,IMAP4:cmd:TimeMax,IMAP4:cmd:Time2,IMAP4:submit:Try,IMAP4:submit:Error,IMAP4:submit:BytesR,IMAP4:submit:BytesW,IMAP4:submit:Time,IMAP4:submit:TimeMin,IMAP4:submit:TimeMax,IMAP4:submit:Time2,IMAP4:retrieve:Try,IMAP4:retrieve:Error,IMAP4:retrieve:BytesR,IMAP4:retrieve:BytesW,IMAP4:retrieve:Time,IMAP4:retrieve:TimeMin,IMAP4:retrieve:TimeMax,IMAP4:retrieve:Time2,IMAP4:logout:Try,IMAP4:logout:Error,IMAP4:logout:BytesR,IMAP4:logout:BytesW,IMAP4:logout:Time,IMAP4:logout:TimeMin,IMAP4:logout:TimeMax,IMAP4:logout:Time2,IMAP4:idle:Try,IMAP4:idle:Error,IMAP4:idle:BytesR,IMAP4:idle:BytesW,IMAP4:idle:Time,IMAP4:idle:TimeMin,IMAP4:idle:TimeMax,IMAP4:idle:Time2,
+0,1291765567,5,6,158,0,4658,819,3546.026228,0.000009,59.939728,211942.126988,6,0,0,0,0.001195,0.000159,0.000261,0.000000,6,0,1452,0,0.007379,0.001169,0.001325,0.000009,6,0,96,168,0.019832,0.003144,0.003624,0.000066,65,0,2785,596,3.899840,0.003511,0.106300,0.253290,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001332,0.000217,0.000301,0.000000,70,0,0,0,3542.096650,0.000009,59.939728,211941.873623,
+1,1291765562,5,6,158,0,4658,819,3546.025872,0.000009,59.939719,211947.013378,6,0,0,0,0.001177,0.000167,0.000241,0.000000,6,0,1452,0,0.009164,0.001129,0.002979,0.000017,6,0,96,168,0.021267,0.003275,0.003793,0.000076,65,0,2785,596,3.858248,0.003595,0.085485,0.246462,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001703,0.000241,0.000558,0.000001,70,0,0,0,3542.134313,0.000009,59.939719,211946.766823,
+2,1291765565,5,6,158,0,4658,819,3546.023929,0.000008,59.939611,211951.571326,6,0,0,0,0.001137,0.000152,0.000255,0.000000,6,0,1452,0,0.007488,0.001190,0.001291,0.000009,6,0,96,168,0.019923,0.003094,0.003608,0.000066,65,0,2785,596,3.818738,0.003507,0.069377,0.240965,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001211,0.000214,0.000278,0.000000,70,0,0,0,3542.175432,0.000008,59.939611,211951.330285,
+3,1291765569,5,6,158,0,4658,819,3546.023446,0.000007,59.939915,211848.752587,6,0,0,0,0.001487,0.000166,0.000310,0.000000,6,0,1452,0,0.007258,0.001110,0.001355,0.000009,6,0,96,168,0.021535,0.003324,0.003838,0.000078,65,0,2785,596,4.677732,0.003546,0.206678,0.409963,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001366,0.000229,0.000332,0.000000,70,0,0,0,3541.314068,0.000007,59.939915,211848.342536,
+4,1291765564,5,6,158,0,4658,819,3546.023242,0.000009,59.939851,211942.201532,6,0,0,0,0.001568,0.000156,0.000559,0.000001,6,0,1452,0,0.006842,0.000906,0.001409,0.000008,6,0,96,168,0.021437,0.003273,0.004005,0.000077,65,0,2785,596,3.896224,0.003532,0.088488,0.252092,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001296,0.000234,0.000278,0.000000,70,0,0,0,3542.095875,0.000009,59.939851,211941.949354,
+5,1291765568,5,6,158,0,4658,819,3546.026494,0.000008,59.939571,211895.355621,6,0,0,0,0.001018,0.000151,0.000193,0.000000,6,0,1452,0,0.007499,0.001198,0.001293,0.000009,6,0,96,168,0.021019,0.003169,0.003890,0.000074,65,0,2785,596,4.291399,0.003449,0.180823,0.347016,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001350,0.000215,0.000342,0.000000,70,0,0,0,3541.704209,0.000008,59.939571,211895.008521,
+6,1291765569,5,6,158,0,4658,819,3546.128029,0.000010,59.940146,211825.732297,6,0,0,0,0.001356,0.000177,0.000285,0.000000,6,0,1452,0,0.007026,0.001086,0.001272,0.000008,6,0,96,168,0.034549,0.003419,0.010366,0.000259,65,0,2785,596,4.974632,0.003498,0.237262,0.482939,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001671,0.000267,0.000406,0.000001,70,0,0,0,3541.108795,0.000010,59.940146,211825.249090,
+7,1291765564,5,6,158,0,4658,819,3546.022557,0.000008,59.938962,211950.321600,6,0,0,0,0.001211,0.000160,0.000275,0.000000,6,0,1452,0,0.007401,0.001102,0.001284,0.000009,6,0,96,168,0.020844,0.003290,0.003658,0.000073,65,0,2785,596,3.827625,0.003488,0.079416,0.242420,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001426,0.000219,0.000320,0.000000,70,0,0,0,3542.164050,0.000008,59.938962,211950.079097,
+8,1291765568,5,6,158,0,4658,819,3546.023633,0.000007,59.938622,211941.575098,6,0,0,0,0.001094,0.000165,0.000216,0.000000,6,0,1452,0,0.007483,0.001200,0.001280,0.000009,6,0,96,168,0.021335,0.003269,0.003837,0.000076,65,0,2785,596,3.901656,0.003601,0.089224,0.252422,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001477,0.000256,0.000320,0.000000,70,0,0,0,3542.090588,0.000007,59.938622,211941.322589,
+9,1291765564,5,6,158,0,4658,819,3546.022528,0.000008,59.939625,211937.407686,6,0,0,0,0.001238,0.000152,0.000274,0.000000,6,0,1452,0,0.007700,0.001159,0.001449,0.000010,6,0,96,168,0.022948,0.003778,0.003885,0.000088,65,0,2785,596,3.935471,0.003524,0.090800,0.257856,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001348,0.000235,0.000297,0.000000,70,0,0,0,3542.053823,0.000008,59.939625,211937.149732,
+10,1291765567,5,6,158,0,4658,819,3546.027517,0.000009,59.938898,211859.216577,6,0,0,0,0.001123,0.000158,0.000252,0.000000,6,0,1452,0,0.006653,0.001016,0.001224,0.000007,6,0,96,168,0.035255,0.003071,0.018345,0.000394,65,0,2785,596,4.593846,0.003350,0.142675,0.367199,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001187,0.000218,0.000267,0.000000,70,0,0,0,3541.389453,0.000009,59.938898,211858.848976,
+11,1291765563,5,6,158,0,4658,819,3546.022490,0.000008,59.938711,211904.294259,6,0,0,0,0.001216,0.000165,0.000232,0.000000,6,0,1452,0,0.007296,0.001072,0.001296,0.000009,6,0,96,168,0.022422,0.003292,0.004178,0.000084,65,0,2785,596,4.212204,0.003527,0.147561,0.305861,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001313,0.000225,0.000282,0.000000,70,0,0,0,3541.778039,0.000008,59.938711,211903.988304,
+12,1291765566,5,6,158,0,4658,819,3546.024010,0.000008,59.940170,211951.434788,6,0,0,0,0.001339,0.000172,0.000276,0.000000,6,0,1452,0,0.007045,0.000967,0.001314,0.000008,6,0,96,168,0.022203,0.003538,0.003813,0.000082,65,0,2785,596,3.819374,0.003629,0.075074,0.241152,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001763,0.000288,0.000405,0.000001,70,0,0,0,3542.172286,0.000008,59.940170,211951.193545,
+13,1291765569,5,6,158,0,4658,819,3546.022222,0.000008,59.939281,211945.093172,6,0,0,0,0.001264,0.000163,0.000278,0.000000,6,0,1452,0,0.007361,0.001104,0.001352,0.000009,6,0,96,168,0.021330,0.003289,0.004016,0.000076,65,0,2785,596,3.870968,0.003473,0.092205,0.248611,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001358,0.000228,0.000357,0.000000,70,0,0,0,3542.119941,0.000008,59.939281,211944.844475,
+14,1291765565,5,6,158,0,4658,819,3546.022739,0.000008,59.940316,211937.726225,6,0,0,0,0.001255,0.000162,0.000239,0.000000,6,0,1452,0,0.007395,0.001130,0.001377,0.000009,6,0,96,168,0.021480,0.003507,0.003669,0.000077,65,0,2785,596,3.933006,0.003596,0.112153,0.259055,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001444,0.000206,0.000377,0.000000,70,0,0,0,3542.058159,0.000008,59.940316,211937.467083,
+15,1291765568,5,6,158,0,4658,819,3546.022797,0.000008,59.939528,211945.541409,6,0,0,0,0.001215,0.000144,0.000360,0.000000,6,0,1452,0,0.007646,0.001200,0.001363,0.000010,6,0,96,168,0.021313,0.003349,0.003866,0.000076,65,0,2785,596,3.868009,0.003484,0.097820,0.248686,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001194,0.000214,0.000274,0.000000,70,0,0,0,3542.123420,0.000008,59.939528,211945.292637,
+16,1291765569,5,6,158,0,4658,819,3546.022874,0.000008,59.938632,211946.692021,6,0,0,0,0.001277,0.000168,0.000279,0.000000,6,0,1452,0,0.007761,0.001204,0.001417,0.000010,6,0,96,168,0.035938,0.003444,0.010891,0.000275,65,0,2785,596,3.857973,0.003483,0.072496,0.246056,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001398,0.000229,0.000347,0.000000,70,0,0,0,3542.118527,0.000008,59.938632,211946.445680,
+17,1291765565,5,6,158,0,4658,819,3546.022233,0.000009,59.939289,211935.629714,6,0,0,0,0.001118,0.000161,0.000249,0.000000,6,0,1452,0,0.007764,0.001233,0.001405,0.000010,6,0,96,168,0.029136,0.003537,0.011023,0.000187,65,0,2785,596,3.949775,0.003523,0.089239,0.258933,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001502,0.000247,0.000340,0.000000,70,0,0,0,3542.032938,0.000009,59.939289,211935.370583,
+18,1291765568,5,6,158,0,4658,819,3546.025702,0.000008,59.939349,211949.642746,6,0,0,0,0.001195,0.000168,0.000236,0.000000,6,0,1452,0,0.007665,0.001135,0.001465,0.000010,6,0,96,168,0.021062,0.003099,0.003896,0.000074,65,0,2785,596,3.836542,0.003620,0.070424,0.242861,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001281,0.000200,0.000337,0.000000,70,0,0,0,3542.157957,0.000008,59.939349,211949.399801,
+19,1291765564,5,6,158,0,4658,819,3546.022228,0.000009,59.939521,211951.462442,6,0,0,0,0.001149,0.000169,0.000256,0.000000,6,0,1452,0,0.007446,0.001135,0.001281,0.000009,6,0,96,168,0.021038,0.003239,0.003726,0.000074,65,0,2785,596,3.817715,0.003493,0.075060,0.241035,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,5,0,325,55,0.001399,0.000207,0.000353,0.000000,70,0,0,0,3542.173481,0.000009,59.939521,211951.221323,
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-trebuchet.csv
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-trebuchet.csv	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-trebuchet.csv	2010-12-08 00:05:44 UTC (rev 316)
@@ -0,0 +1,3 @@
+client,time,blocks,IMAP4:blocks,IMAP4:total:Try,IMAP4:total:Error,IMAP4:total:BytesR,IMAP4:total:BytesW,IMAP4:total:Time,IMAP4:total:TimeMin,IMAP4:total:TimeMax,IMAP4:total:Time2,IMAP4:conn:Try,IMAP4:conn:Error,IMAP4:conn:BytesR,IMAP4:conn:BytesW,IMAP4:conn:Time,IMAP4:conn:TimeMin,IMAP4:conn:TimeMax,IMAP4:conn:Time2,IMAP4:banner:Try,IMAP4:banner:Error,IMAP4:banner:BytesR,IMAP4:banner:BytesW,IMAP4:banner:Time,IMAP4:banner:TimeMin,IMAP4:banner:TimeMax,IMAP4:banner:Time2,IMAP4:login:Try,IMAP4:login:Error,IMAP4:login:BytesR,IMAP4:login:BytesW,IMAP4:login:Time,IMAP4:login:TimeMin,IMAP4:login:TimeMax,IMAP4:login:Time2,IMAP4:cmd:Try,IMAP4:cmd:Error,IMAP4:cmd:BytesR,IMAP4:cmd:BytesW,IMAP4:cmd:Time,IMAP4:cmd:TimeMin,IMAP4:cmd:TimeMax,IMAP4:cmd:Time2,IMAP4:submit:Try,IMAP4:submit:Error,IMAP4:submit:BytesR,IMAP4:submit:BytesW,IMAP4:submit:Time,IMAP4:submit:TimeMin,IMAP4:submit:TimeMax,IMAP4:submit:Time2,IMAP4:retrieve:Try,IMAP4:retrieve:Error,IMAP4:retrieve:BytesR,IMAP4:retrieve:BytesW,IMAP4:retrieve:Time,IMAP4:retrieve:TimeMin,IMAP4:retrieve:TimeMax,IMAP4:retrieve:Time2,IMAP4:logout:Try,IMAP4:logout:Error,IMAP4:logout:BytesR,IMAP4:logout:BytesW,IMAP4:logout:Time,IMAP4:logout:TimeMin,IMAP4:logout:TimeMax,IMAP4:logout:Time2,IMAP4:idle:Try,IMAP4:idle:Error,IMAP4:idle:BytesR,IMAP4:idle:BytesW,IMAP4:idle:Time,IMAP4:idle:TimeMin,IMAP4:idle:TimeMax,IMAP4:idle:Time2,
+0,1291765582,100,120,3160,0,93160,16380,70920.444463,0.000002,59.940810,4238925.576335,120,0,0,0,0.017693,0.000092,0.000240,0.000003,120,0,29040,0,0.152156,0.001011,0.001545,0.000194,120,0,1920,3360,0.501367,0.002915,0.013083,0.002768,1300,0,55700,11920,77.227536,0.003315,0.125943,4.956312,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,100,0,6500,1100,0.021252,0.000128,0.000398,0.000005,1400,0,0,0,70842.524459,0.000002,59.940810,4238920.617054,
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-uranus.csv
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-uranus.csv	                        (rev 0)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/clients-uranus.csv	2010-12-08 00:05:44 UTC (rev 316)
@@ -0,0 +1,3 @@
+client,time,blocks,IMAP4:blocks,IMAP4:total:Try,IMAP4:total:Error,IMAP4:total:BytesR,IMAP4:total:BytesW,IMAP4:total:Time,IMAP4:total:TimeMin,IMAP4:total:TimeMax,IMAP4:total:Time2,IMAP4:conn:Try,IMAP4:conn:Error,IMAP4:conn:BytesR,IMAP4:conn:BytesW,IMAP4:conn:Time,IMAP4:conn:TimeMin,IMAP4:conn:TimeMax,IMAP4:conn:Time2,IMAP4:banner:Try,IMAP4:banner:Error,IMAP4:banner:BytesR,IMAP4:banner:BytesW,IMAP4:banner:Time,IMAP4:banner:TimeMin,IMAP4:banner:TimeMax,IMAP4:banner:Time2,IMAP4:login:Try,IMAP4:login:Error,IMAP4:login:BytesR,IMAP4:login:BytesW,IMAP4:login:Time,IMAP4:login:TimeMin,IMAP4:login:TimeMax,IMAP4:login:Time2,IMAP4:cmd:Try,IMAP4:cmd:Error,IMAP4:cmd:BytesR,IMAP4:cmd:BytesW,IMAP4:cmd:Time,IMAP4:cmd:TimeMin,IMAP4:cmd:TimeMax,IMAP4:cmd:Time2,IMAP4:submit:Try,IMAP4:submit:Error,IMAP4:submit:BytesR,IMAP4:submit:BytesW,IMAP4:submit:Time,IMAP4:submit:TimeMin,IMAP4:submit:TimeMax,IMAP4:submit:Time2,IMAP4:retrieve:Try,IMAP4:retrieve:Error,IMAP4:retrieve:BytesR,IMAP4:retrieve:BytesW,IMAP4:retrieve:Time,IMAP4:retrieve:TimeMin,IMAP4:retrieve:TimeMax,IMAP4:retrieve:Time2,IMAP4:logout:Try,IMAP4:logout:Error,IMAP4:logout:BytesR,IMAP4:logout:BytesW,IMAP4:logout:Time,IMAP4:logout:TimeMin,IMAP4:logout:TimeMax,IMAP4:logout:Time2,IMAP4:idle:Try,IMAP4:idle:Error,IMAP4:idle:BytesR,IMAP4:idle:BytesW,IMAP4:idle:Time,IMAP4:idle:TimeMin,IMAP4:idle:TimeMax,IMAP4:idle:Time2,
+0,1291765554,100,120,3160,0,93160,16380,70920.587432,0.000004,59.940511,4237628.003962,120,0,0,0,0.024330,0.000127,0.002991,0.000013,120,0,29040,0,0.144636,0.000013,0.001479,0.000177,120,0,1920,3360,0.465190,0.002984,0.011183,0.002130,1300,0,55700,11920,88.214361,0.003316,0.208830,6.855541,0,0,0,0,0.0,0,0.0,0.0,0,0,0,0,0.0,0,0.0,0.0,100,0,6500,1100,0.022513,0.000165,0.000320,0.000005,1400,0,0,0,70831.716402,0.000004,59.940511,4237621.146096,
+

Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/commands.png
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/commands.png
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/commands.png	2010-12-07 22:28:37 UTC (rev 315)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/commands.png	2010-12-08 00:05:44 UTC (rev 316)

Property changes on: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/commands.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/connections.png
===================================================================
(Binary files differ)

Index: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/connections.png
===================================================================
--- trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/connections.png	2010-12-07 22:28:37 UTC (rev 315)
+++ trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/connections.png	2010-12-08 00:05:44 UTC (rev 316)

Property changes on: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/connections.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/sysadmin/Projects/CMSEmail/Reports/20101207.1446/connects.png
===================================================================
(Binary files differ)


(Diff truncated)