At a terminal in the Pierce computer lab, I was able to examine a memory location from my student account that showed me that all "security auditing" was enabled on my account. Lenny checked his account using the same technique; security auditing was enabled on it, as well. The guy from DEC was closeted in a small room with a computer and printer, watching everything we were doing from our student accounts. (I discovered this by showing up early one day before the tech arrived and following him to the room.) I thought this was a bit overkill since the system was only used by students to complete their lab work, and not connected to any network or phone line. But I found a way to keep him busy: I wrote a very simple script that listed the files in my directory, over and over. Since the security auditing was designed to send a detailed alert for every file opened or read, I knew his printer would be working nonstop. I could picture the guy closed up in his tiny room, pulling his hair out that his printer kept running until it was out of paper. And as soon as he would load more paper, the file lists would start printing out again.