Bug 37307 – KDE problems on an openmosix kernel

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Peter Bienstman (RETIRED) 2004-01-05 08:36:52 UTC]

Just running openmosix-2.4.22-r2 (even without the openmosix daemon running or without /mfs mounted) gives me KDE problems: KDE starts really slowly, and bringing up applications like Konsole or Konqueror takes forever.

Setting using 'mosctl stay' or 'mosctl lstay' doesn't help.

Similar problems have been reported here: http://forums.gentoo.org/viewtopic.php?t=40431&highlight=openmosix+kde

This only seems to occur on a P4 system, a P3 system works fine. I do have most of my P4 system built with -march=pentium3 however, so CFLAGS are probably not the problem.

When booting from a ClusterKnoppix live CD, I don't see these problems.


Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Michael Imhof (RETIRED) 2004-01-07 16:11:31 UTC]

Could you please give me some more information about your system (emerge info) etc.?

What kernel does Clusterknoppix use? Do you think this problem is related to the kernel or do you have any suggestions?

[Comment 2 Michael Imhof (RETIRED) 2004-01-07 16:20:25 UTC]

On Wed, Jan 07, 2004 at 07:23:16PM +0100, Peter Bienstman wrote:

>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> Hi, 
>>  
>>  We're building an openmosix cluster of desktop machines (gentoo openmosix 
>> 2.4.22-r3), but we want to avoid components of KDE migrating to other 
>> machines, becauses that kills the responsivity or sometimes even causes the 
>> UI to hang. 


sure, that is awful when dcopserver or kdeinit migrates elsewhere 
i had the same problem a few months ago

i just tell to "init" not to migrate the display manager and their son
processes, with mosrun -h in the /etc/inittab file,  and it works for me
(i.e all kde processes stay on local node)

# Run xdm in runlevel 5
# xdm is now a separate service
x:5:respawn:/bin/mosrun -h /etc/X11/prefdm -nodaemon

tell me if it works for you?

ML

[Comment 3 Michael Imhof (RETIRED) 2004-01-07 16:22:37 UTC]

so does it work?

[Comment 4 Peter Bienstman (RETIRED) 2004-01-08 00:54:42 UTC]

This is what I had:

x:a:once:/bin/mosrun -h /etc/X11/startDM.sh

But that didn't seem to be enough: kdeinits were still migrating away.

(PS: ingnore my comments about P3's working OK)

[Comment 5 Rene Androsch 2004-02-16 06:25:47 UTC]

A stupid question!

mosrun, mosrun, .. where are they?

I have:

[ebuild   R   ] sys-kernel/openmosix-sources-2.4.24  -build  0 kB
[ebuild   R   ] sys-cluster/openmosix-user-0.3.5   0 kB
[ebuild   R   ] sys-cluster/openmosixview-1.5   0 kB

but no binaries?

[Comment 6 Stephen Diener (RETIRED) 2004-02-16 07:53:41 UTC]

If you can't find it, you might need to check your path.  You should also make sure that your /usr/src/linux link points to the om-kernel before emerging openmosix-user.

$ emerge gentoolkit
$ qpkg -l openmosix-user
sys-cluster/openmosix-user-0.3.5 *
CONTENTS:
[snip]
/bin/mosmon
/bin/mosrun
[snip]

[Comment 7 Konstantin Arkhipov (RETIRED) 2004-05-23 07:55:01 UTC]

*** This bug has been marked as a duplicate of 32309 ***