agreed - 10.0 was a great release, i've installed it on several client servers and desktops and never had a problem with it. in fact my company's colo server is running mdk10 right now with 128 days of trouble-free uptime. unfortunately i found 10.1 to be flaky and unstable. apparently it doesn't take much to go from a great release to a marginal one (not that mandrake is the only distro to fall victim to this kind of behavior, redhat's .0 releases have historically been subpar as well).

jason

Jon Carnes wrote:
Just as another data point, I'm running Mandrake 10.0 on a few of my
main production servers. They've run perfectly for quite sometime now
with up-times of almost a year (that's how long Mandrake 10 had been
out).

===
top - 14:29:28 up 340 days, 3:54, 1 user, load average: 0.00, 0.00, 0.00
Tasks:  89 total,   1 running,  88 sleeping,   0 stopped,   0 zombie
Cpu(s): 0.0% us, 0.1% sy, 0.0% ni, 99.9% id, 0.0% wa, 0.0% hi,  0.0% si
Mem:  1032232k total,  1012260k used,    19972k free,    38900k buffers
Swap: 1084348k total,    29780k used,  1054568k free,   863352k cached
===

My production servers run in RC3 so no KDE problems there.

I tested Mandrake 10.1 when it came out and I didn't think it was stable
enough for a production server. Mandrake 10.0 though is still rock
solid.

Jon (I never trust those .1 releases) Carnes

On Sat, 2005-04-09 at 14:12, Jason Tower wrote:

i can't tell you how to fix it as i'm no longer running mdk 10.1, but i experienced the same problem. my (brief) attempt at finding the root cause of the problem did not yield anything useful. but at least you know you're not alone.

Michael Hrivnak wrote:

I'm running Mandrake 10.1 Official with KDE.

Once in a while, a kdeinit process will start sucking down CPU cycles like there's no tomorrow. That is accompanied by various things not working, for example I can't get konqueror to start. If I try to start it from the command line, I can't get any useful feedback out of it. The only way to kill he kdeinit process is with a SIGSTOP. Even once it's been killed though, the broken stuff remains broken.


--
TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ  : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc

Reply via email to