Synopsis: System Panics after running fsck and re-hup-ing or stopping Apache process
State-Changed-From-To: open-closed State-Changed-By: coar State-Changed-When: Sun Oct 26 12:28:38 PST 1997 State-Changed-Why: The problem is that you're trying to repair a disk while it's in use, which is a major badness under any circumstances. If you try to change a tyre while a vehicle is in motion, and you get run over, you've no-one but yourself to blame. Apache opens some files and immediately unlinks them to prevent any other process from being able to access (and particularly modify) them. This is fairly common practice. The workaround, or actually the correct procedure, is for you to do your repairs on a quiescent filesystem. Thanks for using Apache! Class-Changed-From-To: sw-bug-mistaken Class-Changed-By: coar Class-Changed-When: Sun Oct 26 12:28:38 PST 1997 Severity-Changed-From-To: critical-non-critical Severity-Changed-By: coar Severity-Changed-When: Sun Oct 26 12:28:38 PST 1997
