Do you mean that the boot process is taking longer, or that individual
processes are running slower on an alredy-booted system?
If you mean the first, I'm pretty much stumped, assuming you are shutting
down properly. If you aren't using "shutdown" or "halt" before powering off,
your system will fsck the drives when you boot, and as they get fuller, that
will take longer. But this seems like a long shot. Beyond that, I'd suggest
a look at the dmesg buffer and whichever log you have recording boottime
messages (perhaps /var/log/messages, though that varies) to see what might
be different.
If you mean the second, my first thought is a memory leak. (This means that
when a process ends, the kernel fails to free up all the memory it used, or,
more commonly, that a background process fails to release memory and
gradually ties up more and more memory. Over time, this causes the kernel to
see more and more memory as in use, eventually increasing the use of swap
... and swap always slows things to a crawl.) Use "free" or "top" to track
over time what is happening with memory. Also, see if a reboot fixes things.
Disk fragmentation is a possibility, but a remote one. I think there is a
way to get fsck to report the percent fragmentation; check the man page for
your version to see. If it's high, there is a defragger available somewhere.
Sorry if I've misinterpreted your description. Hope this helps.
At 01:03 PM 8/1/99 -0500, Richard Salts wrote [in part]:
>Up until about yesterday, my Linux was behaving very nicely, loading up in
>record time. Now, it seems to have slowed down quite considerably, making
>the Windows loading very fast by comparison.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA 94303-3603 [EMAIL PROTECTED]
----------------------------------------------------------------
