But you _want_ to unmount these file systems cleanly. A "busy" in the
shutdown script means something's seriously wrong in your setup.
I had this problem recently, with my big /var disk not getting
unmounted and fsck'd on every reboot. I hadn't any idea why this
happened, so I inserted an "lsof > /debug" jut before the umount in
the shutdown script and tried to analyze its output after rebooting.
It turned out that the Sun JDK, which I had installed on the /var
disk, came with its own copy of libc.so.5.4.something deep inside an
obscurely nested path and ldconfig happily pointed every program out
there, including /bin/sh, to use that instead of the copy in /lib.
This also happened with another library (I think it was libdl). Blech.
(Fix, of course, was to remove all those redundant libraries.)
olaf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu