Back to the Cal Poly Home Page The following table is used to establish procedures to be followed in notifying users of system downtimes:.
| Lead Time | Date Done | |
| Tools Available | After-the-fact | |
| Messages posted on other systems | ||
| Check Lab schedules for conflicting reservations | ||
| System Message of the Day (MOTD) | Point to the relevant System News article | |
| System News article | Posted to let users know the consequences of the unanticipated downtime that occurred. | |
| "nicemail" to all users (NOTE: Takes about 13 hours on a idle system.) | Message should be mailed out if the unscheduled outage affected user files and/or the delivery of mail. | |
| POP Bulletins for POP users | DO NOT use if "nicemail" is used.. If used, the text of the system news article is used with a special header added to indicate that it is a POP bulletin. Should only be used if the unscheduled outage affected user files and/or the delivery of mail. | |
| NETNews article (also email CSc Faculty, NetAdmin, unix-admins, Help Desk, IAS Staff, UNIXMgt, lan-coords) | Posted as to let users know the consequences of the unanticipated downtime that occurred. | |
| Web Pages | Posted as to let users know the consequences of the unanticipated downtime that occurred. | |
| Article in the Mustang Daily | ||
| ByITS Newsletter Article | ||
| Cal Poly Report | ||
| Help Desk Information Session | Details of the unanticipated downtime ASAP after the event has occurred. Problem status and resolution. | |
| Flyers posted in labs, outside Help Desk, in Library | ||
| Training Classes | ||
| Demos and Talks | ||
| COB & Library Training Personnel | ||
| Mailing Lists (internal to ITS, UNIX Admins, Lan Coordinators) | Details of the unanticipated downtime ASAP after the event has occurred. Problem status and resolution. | |
| Internal Training |