/var is busy? the hell??

[ron.peterson at yellowbank.com (Ron Peterson)]

On Wed, 5 Sep 2001, Derek Martin wrote:

> After shutting down services (like sendmail, syslog, etc), your system
> will send all processes the SIGTERM signal, which should cause them to
> clean up and terminate, and close their open files.

So maybe there's an init script out of order in the shutdown process.  You
might want to check the script numbering for your default runlevel, as
well as levels 0 and 6.

> This can also happen if a process which lives in /var or has a file
> open in there somehow gets wedged in I/O wait state ( 'D' status in
> the ps output).  These processes are generally uninterruptable, and
> even kill -9 won't kill them.  In these cases, the fs will not umount
> cleanly, and you'll have to fsck.

Speaking of uninterruptable NFS mounts, can anyone explain why the 'intr'
option exists?  Meaning, why is it even an option?  Why would you want an
uninteruptable NFS mount?  And why is this the default?

-- 

-Ron-
https://www.yellowbank.com/

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).