SUMMARY: post-MU3 problems with e250

The problem appears to have been a rogue httpd. It forked infinitely,
and two hours later, the kernel was showing shared memory errors.
After rebooting the machine and switching out the bad (also new) version
of apache, the machine is operating normally.  My speculation is that
somehow the out-of-control apache managed to write someplace in shared
memory that it shouldn't have.

I only got a couple of responses, both indicating that either I didn't
reboot after installing the MU3, or that a boot -r was required
afterward. I did reboot, though not -r, but nothing in any docs
indicates that -r would be necessary.

Now all I have to do is figure out why adding the mod_headers module
to a known set of options to apache made it go so bonkers.

Lynette Bellini
Systems Administrator
University of Minnesota