Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!sun-barr!newstop!sun!coherent!next!surak
From: surak@next.com (Jayson Adams)
Newsgroups: comp.sys.next
Subject: Re: Problem Solved ( Re: How to get rid of defunct proc. )
Message-ID: <227@next.com>
Date: 17 Aug 90 23:10:34 GMT
References: <90219.135712PVJQC@CUNYVM.BITNET> <90225.091620PVJQC@CUNYVM.BITNET>
Organization: NeXT Inc., Palo Alto
Lines: 13

In article <90225.091620PVJQC@CUNYVM.BITNET>, PVJQC@CUNYVM writes:
> In article <90219.135712PVJQC@CUNYVM.BITNET>, <PVJQC@CUNYVM> says:
> >...CPU cycles. I have shut down and rebooted the m/c n no. of times. NeXT
> >tech support could not figure out what was going on. Rebuilding the disk...
> ----------
> Finally the above problem was solved....

PVJQC neglected to mention how he acquired this solution.  Just to set the
record straight, a NeXT Technical Support Engineer talked to him soon after
his first posting and discovered the cause of his problems.

__jayson  :-)
Team Leader, NeXT Developer Support