Mailinglist Archive: opensuse (2234 mails)
| < Previous | Next > |
Re: [SLE] R: [SLE] No Luck Yet: System S L O W after upgrade
- From: grimmer@xxxxxxx (Lenz Grimmer)
- Date: 1 Sep 1999 10:02:51 +0200
- Message-id: <Pine.LNX.4.10.9909010956010.28472-100000@xxxxxxxxxxxxx>
Hi,
On Wed, 1 Sep 1999, Papini Stefano wrote:
> tonight I examined top
> while disk throttling: process "nobody" was doing a FIND , with priority 13
> (16).
>
> More, from the exam of /var/log/messages, it seems that my machine
> effectively tries to launch a cron op (oops Ole!!, sorry) (never set
> by me) and can't execute it as the resource searched is locked by a
> certain PID (I seem 163).
This is normal. Cron.daily runs some housekeeping jobs in the backround
and they need some time to finish (it runs "updatedb", which indexes all
files on your hard disk).
> After launching a generic /usr/sbin/cron, the disk stopped.
cron.daily will also stop, as soon as it has finished its job.
> More, after "playing" a while with KDE supplied with the first release
> of 6.1, my machine (hardware is ok) stopped totally. I couldn't log
> from a different tty and kill the "killer" process.
Did you use KDE as root? There is a known bug in the kaudioserver, which
will eat up all your memory and makes the machine freeze.
Maybe this is what´s happening in your case?
Bye,
LenZ
--
------------------------------------------------------------------
Lenz Grimmer SuSE GmbH
mailto:grimmer@xxxxxxx Schanzaeckerstr. 10
http://www.suse.de/~grimmer 90443 Nuernberg, Germany
--
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
| < Previous | Next > |