Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: jeff@tc.fluke.com (Jeff Stearns)
Newsgroups: comp.sys.sun
Subject: Re: Daemons stuck in 'D' "short-term" wait state
Message-ID: <7078@fluke.COM>
Date: 4 Mar 89 05:01:45 GMT
References: <8902101825.AA14994@independent.uucp>
Sender: usenet@rice.edu
Organization: John Fluke Mfg. Co., Inc., Everett, WA
Lines: 19
Approved: Sun-Spots@rice.edu
Original-Date: 21 Feb 89 22:36:50 GMT
X-Sun-Spots-Digest: Volume 7, Issue 180, message 5 of 12
X-Issue-Reference: v7n161

mcvax!independent!dwight@uunet.uu.net (Dwight Ernest) writes:
>> ... a process which is stuck, reported by ps as in `D' "short term" wait,
>> and has been for two days.  ... Last time it happended, earlier in the week,
>> all the nfsd's got stuck in this state, and the clients froze.
>
>Same thing happened to us once, yesterday, (for the first time) while
>running tops2d, the TOPS version 2 Sun daemon....
>Do we have a generic problem?

On my "generic" 3/60, I've wedged a variety of processes from cp(1) on up.
(Around here, FrameMaker seems to do it a lot.)  The stuck-in-D-wait bug
is much more prominent under SunOS 4.0.  And it isn't limited to
"daemons".

    Jeff Stearns        John Fluke Mfg. Co, Inc.               (206) 356-5064
    jeff@tc.fluke.COM   {uw-beaver,microsoft,sun}!fluke!jeff

PS - Calling all users of the Vitalink TransLAN IV Ethernet bridge! Please
     drop me a line.