🚀 go-pugleaf

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.  

I am now contemplating returning to 2.1, since it seems to be
a much more coherent and dependable system for my configuration.

Our smaller systems haven't had this problem, but our 32M RAM
system with 1.6G of disk has been suffering.  Since it's used
by over 200 users, and since I can't depend on NeXTstep 3.0,
back to 2.1 it looks like I shall go.

It's a real disappointment when a company like NeXT does
something like this.  I started with NeXTstep 0.8 and it
was better than this.  Perhaps they want me to trash my
cube and replace it with a 486....

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>
> root        -1   0.0  0.0    0K    0K ?  SW<   0:00 <mach-task>
> root        -1   0.0  0.0    0K    0K ?  S     0:10 <mach-task>
> root        -1   0.0  0.0   16K   16K ?  S     0:23 <mach-task>
> root        -1   0.0  0.0    0K    0K ?    N   0:00 <mach-task>
> root        -1   0.0  0.0    0K    0K ?    N   0:00 <mach-task>
> root        -1   0.0  0.0    0K    0K ?  S     0:04 <mach-task>
> root        -1   0.0  0.0    0K    0K ?    N   0:00 <mach-task>
> root        -1   0.0  0.0    0K    0K ?    N   0:00 <mach-task>
> root        -1   0.0  0.0    0K    0K ?    N   0:00 <mach-task>
> root        -1   0.0  0.0    0K    0K ?    N   0:00 <mach-task>
> root        -1   0.0  0.0    0K    0K ?    N   0:00 <mach-task>
> root        -1   0.0  0.0    0K    0K ?    N   0:00 <mach-task>
> root        -1   0.0  0.0    0K    0K ?    N   0:00 <mach-task>
> root        -1   0.0  0.0    0K    0K ?  ?W<   0:00 <mach-task>
> 
> 
> why so many and what can be done about it or is this just another 3.0  
> feature?
> 
> Scott