earlier today...
later
charles Ulwelling
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of HAL 9000
Sent: Sunday, March 26, 2000 8:19 PM
To: [EMAIL PROTECTED]
Subject: [newbie] slow Linux
hello all.. i just installed Mandrake and i used a larger swap
.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of KompuKit
Sent: Sunday, March 26, 2000 5:27 AM
To: [EMAIL PROTECTED]
Subject: Re: [newbie] slow Linux
How do you check for multiple instances of apache running...?
that could be my problem also...netscape keeps
At the moment SETI@Home is taking 97% of my CPU (PII 450), and I'm having no
problems with speed at all.
Charles Ulwelling wrote:
Check to see if you have a bunch of instances of httpd running, thats apache
and it screwed me earlier today...
later
charles Ulwelling
nope, not
-Original Message-
From: Anthony Huereca [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 27, 2000 1:39 PM
To: [EMAIL PROTECTED]
Subject: Re: [newbie] slow Linux
At the moment SETI@Home is taking 97% of my CPU (PII 450), and I'm having no
problems with speed at all.
Charles Ulwelling wrote
]
Subject: [newbie] slow Linux
hello all.. i just installed Mandrake and i used a larger swap
partition. now its acting a bit laggy. i have SETI@Home running, but
it has never acted the way it is now. i can watch the windows
maximizing and iconifying aand its a bit "jumpy when that happens.
Charles Ulwelling wrote:
Check to see if you have a bunch of instances of httpd running, thats apache
and it screwed me earlier today...
later
charles Ulwelling
nope, not one instance of httpd seti@home is taking up about 27% of
my CPU... would that greatly affect the performance??
"HAL" == HAL 9000 [EMAIL PROTECTED] writes:
[snip]
HAL nope, not one instance of httpd seti@home is taking up
HAL about 27% of my CPU... would that greatly affect the
HAL performance??
Hello, HAL.
Yes.
(Why is _HAL_ running seti@home, anyway ? ;-) )
--
Mike Fieschko,
Uhhm...
I'd say there's something wrong there...
First of all, let me state that seti@home, even if it consumes all available
CPU, isn't neccessarily a drag on the system. I run 2 seti@homes myself on a
dual celeron (because one wouldn't grab all available CPU-time since it's not
written
