We've recently started having some regular meetings at work, which hasgiven me an opportunity to look back at past meetings and reflect onwhat I think does and doesn't work in meetings for system administrators.(Note that I am pretty sure that some of these do not generalize toother sorts of meetings.)

Meetings can be an efficient way of holding discussions, but you needsomeone to corral the digressions. They are not usually an effectiveway of giving status reports, unless the status reports are really

I periodically find myself dealing with structures that are basically ordered lists with namedfields, where elements 0, 1, and 2 are naturally named 'a', 'b', and'c' and sometimes you want to refer to them by name instead of havingto remember their position. This pattern even crops up in the standardPython library, often with functions that started out just returningan ordered list and grew the named fields portion later as peoplediscovered how annoying it was to have to remember that the hour

The Computer Science department is strongly against rejecting email justbecause it might be spam (at least by default); enough people wouldrather sort through spam than risk rejecting legitimate email. Peopleare willing to have known viruses removed from their email (althoughnot executables in general).

(For clarity: the weekly spam summaries I do are not for CSLab's mailsystem.)

I once summarized CSLab's general rule is 'thou shalt not reject emailjust because it smells bad'. We can reject email

This week, we:

• got 15,188 messages from 253 different IP addresses.
• handled 21,573 sessions from 1,281 different IP addresses.
• received 238,853 connections from at least 71,848 different IPaddresses.
• hit a highwater of 10 connections being checked at once.

Connection and session volume is down a bit from last week . Day to day volume fluctuated up anddown through the week: