After a few hours of running, the new version of swapd 0.2-4 systematically starts hogging all available CPU ressources. With a niceness of -1 (not nice) it's obviously not being nice but you could have guessed that. Worst thing is that the previous version of swapd was running very fine on my systems. Has anyone encountered the same problem?
I'm running unstable on an Inspiron 4000 (196 MiB RAM) with 2.4.17
signature.asc
Description: This is a digitally signed message part