Re: NFS daemons in D state for 2 minutes at shutdown

[Trond Myklebust <trond.myklebust@fys.uio.no>]

>>>>> " " == VDA  <VDA@port.imtp.ilyichevsk.odessa.ua> writes:

     > Well, do you mean I must update my shutdown script whenever I
     > install something new just because this "something new" does
     > not like standard, well accepted method of signalling apps to
     > exit?  Come on, this sounds like The Wrong Way.

Bullshit. killall5 is definitely *not* a well accepted method for
shutting down applications. Try doing that while your network is
running via a ppp link...

Some programs *have* to be shutdown in a certain order. All RPC
servers fall into that category.

     > So, why modified killall5 does the job?

I've no idea how you modified killall5, but if it manages to kill nfsd
before killing the portmapper, then all will work.

     > Why not make portmapper+NFS daemons killable by TERM, giving
     > them the chance to do proper cleanups rather than abrupt KILL?

NFS daemons *do* perform proper cleanups. That's the whole essence of
your problem - they are waiting on the portmapper to acknowledge that
it has unregistered their service. These are *kernel* daemons and so
KILL acts just like any signal as far as they are concerned.

Cheers,
   Trond