Once a day before 5pm:

task	procedure
1)   Confirm that mail server on Imail is working; browse inst@eecs email for trouble reports	Read and send mail through imail.eecs.berkeley.edu. A log of mail activity is /var/log/maillog on Imail. Queued, undelivered mail is in /var/spool/mqueue on Imail. See imail:/etc/motd for information about restarting the spam filters, mail server and Postgres server if Imail is rebooted.
2)   Walk through these labs; note any major problems; note "no food" violations	Soda (271,273,275,277,330,349) Cory (105,199) Sutardja Dai (200) For unattended login sessions, log the user out and send the user a notice using the UNIX command /share/b/adm/bin/send-logged-in-reminder.pl. For "no food" violations, report computer name, time and description of offense so we can identify the user later.   You can warn the user that you are doing this and give the user a chance to remove their food from the lab.   If the user complies politely, you do not have to make the report.
3)   Check SunRays for 'gecko' or other problems	Soda (271, 273, 275) Servers:   nova.cs, star.cs, solar.cs Cory (199) Server:   c199.eecs Make a note of any Sunrays that have an hourglass or other problem.   See ~inst/docs/sunrays.help for information about the keystrokes that clear some SunRay problems.   (Admins who can login as 'root' on the Sunray server can run /share/b/adm/bin/fixblank or /share/b/adm/bin/fixgecko on appropriate SunRay server to clear problems.)
4)   Re-stock the printers with paper if needed.   Confirm that printers are running their queues.	Restock paper in the printers if needed.   Printer paper is stored in 130A Cory and 253 Soda. Windows computers use the print spooler scotland.eecs. Windows computers use the print spooler iprint.eecs. UNIX printer commands: see /share/b/pub/printers.help Print spooler administration on iprint.eecs (Nov 2007):   LPRng logs: Accounting logs: LPRng configuration file: To kill and restart lprng:   /usr/local/var/spool/[building]/[printer] /usr/local/var/log /usr/local/etc/printcap /etc/init.d/lprng [stop|start] Print spooler administration on scotland.eecs (Apr 2010):   Scotland is a Windows server using lprng on Cygwin. So work in a Cygwin bash shell to manage the lprng files. For more information, see \\fileservice.eecs.berkeley.edu\software\ScannersCamerasPrinters\lprng\readme.txt'.
5)   Confirm that the Instructional WEB server is working	Go to URL http://inst.eecs.berkeley.edu and https://inst.eecs.berkeley.edu Log of WEB server activity is in /share/weblogs/ on Cory.
6)   Inform faculty and students if their lab is down (more than about 30 min)	Post signs in labs, post to class newgroups and/or send email to affected users.
7)   Send a brief report to "inst@eecs.berkeley.edu"	List which labs you checked and any problems that you saw.

        campus network & computers:     642-4920 (IS&T Trouble Desk)
	EECS network & computers: 	642-7777 (EECS help desk)
        Inst computers & labs:		232-3876 (Kevin)(8am-10pm only please)
        building safety & security:     642-1032 (Facilities Management)
        personal safety & security:     642-6760 (UC Police)
        EMERGENCY:                      9-911

  If you see anyone eating or etc, you can politely say something like 
  
    "Hi, I'm lab support staff, and my boss has told me to report 
    anyone who is eating in the labs.  He makes people clean the 
    labs as a punishment.  But if you remove the food from the lab
    now, I don't have to report it.  Thanks."

  You can report them to Kevin by identifying the time and the computer 
  they were logged into.  This may not always work (such as if they are 
  using a laptop or working in a group), but it is good enough.  It is 
  better to let the student get away with it than to falsely accuse or 
  argue with the student.