Well, when the equipment was running our softswitch code,
a number of processes would be launched and design was very
picky about what was running on the system with their
software. So we needed to sense an uptick in resource use
and shut down processes. This way, when errors popped
up, they wouldn't have to worry if SETI@Home were somehow
to blame.

Unfortunately, when problems did pop up, they did a ps and
saw "setirunner". In other words, we unfortunately named
the script poorly, and it was easily picked out. We should
have named it something unobtrusive... something vaguely
UNIX-system-like. Ah, well.

Rob