[an error occurred while processing this directive]
The Sat and Sun tasks are:
Once a day before 5pm:
|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.
|2) Walk through these labs; note any major problems; note "no food" violations||
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||
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.
UNIX printer commands: see /share/b/pub/printers.help
Print spooler administration on iprint.eecs (Nov 2007):
Print spooler administration on scotland.eecs (Apr 2010):
5) Confirm that the Instructional WEB server is working
Go to URL
Log of WEB server activity is in /share/weblogs/ on Cory.
6) Inform faculty and students if their lab is down (more than about
Post signs in labs,
post to class newgroups and/or
send email to affected users.
7) Send a brief report to "firstname.lastname@example.org"
List which labs you checked and any problems that you saw.
Off-hours trouble calls: (for staff)
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)
When students break the rules: (for staff)
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.
Group email addresses:
Supports all Instructional servers and these labs:
271, 273, 274, 285 277, 330, 349 Soda
105, 119, 199 Cory
C30, C50 Hearst Field Annex
Supports the EE and CS150 labs that include electronics and
instrumentation (125, 140, 218, 204 and 353 Cory) and labs
that are assigned to student groups (246 Cory, 444 Soda).
See http://inst.eecs.berkeley.edu/~inst/iesglabs.html for more info.
an alias for staff (not students), since some of the support work
is done by people who are not in the "inst@eecs" group. It goes to
inst@eecs as well as Ming Wong and Ferenc Kovac. "inst@eecs" does
the software/spooler maintenance. Ming does printer hardware repairs.
ISG and ESG each replace the paper and toners in their own labs from
the shared supplies in 130A Cory and 251 Soda.
Students are told to send bug reports about the printers to their lab
support group - either "inst@eecs" or "esg@eecs". This should be
posted on each printer.
Supports the projectors and audio in classrooms and auditoriums in
Soda and Cory Halls. Includes some ESG staff as well as Chris Colbert
(Cory Hall staff), CS office staff and some faculty.
Friday, April 09, 2010 email@example.com