🚀 go-pugleaf

>In article <1992Oct29.035859.26265@cronkite.ocis.temple.edu> ray@astro.ocis.temple.edu (Ray Lauff) writes:
>I contacted NeXT yesterday about this problem.  The person I spoke
>with kept me on hold for about 10 minutes and then told me that
>the processes were nothing to worry about and that I should just
>ignore them.
>
>Unfortunately, it's kinda hard to ignore the 300+ of them on
>my system and hard to ignore the slow system response time and
>hard to ignore the eventual system crash that results.
>
>Ray
>ray@astro.temple.edu
>
>S.A.McIntyre@durham.ac.uk wrote:
>>
>> from my process table:
>> root        -1   0.0  0.0	0K    0K ?  U	  2:36 <mach-task>
>> root 	2   0.0  0.8 1.45M  248K co S	  0:08	(mach_init)
>> root        -1   0.0  0.0	0K    0K ?  U	  0:09 <mach-task>
>> root        -1   0.0  0.0	0K    0K ?  S	  0:00 <mach-task>

    Hmmm... it sounds like one or more processes were unable to deallocate
    resources on exit.	This can happen, for example, if an exiting process
    is blocked on a serial port.  While I've never seen processes on my
    own 3.0 machine do the above, I have seen processes 'freeze' where
    even a KILL -9 doesn't take them out... due to hanging on a serial port
    which has lost CTS.  This is definitely a bug, when you kill a process
    it isn't supposed to remain blocked on devices!

    Your problem could be relate to something of that sort but I think only
    a NeXT systems programmer would understand the problem... I doubt their
    technical support is that sohpisticated so you may not get results from
    NeXT unless you can find out *which* process is hanging!

    It could be related to something your users do when they login or
    logout.

				    -Matt

>> Scott

--

    Matthew Dillon		dillon@Overload.Berkeley.CA.US
    1005 Apollo Way		uunet.uu.net!overload!dillon
    Incline Village, NV. 89451	ham: KC6LVW (no mail drop)
    USA 			Sandel-Avery Engineering (702)831-8000