Your message dated Fri, 5 Jan 2007 21:46:30 +0100
with message-id <[EMAIL PROTECTED]>
and subject line openmosix removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: openmosix
Version: 1:0.3.4-7
Severity: normal
Even when bugs #230460 and #217346 are fixed by putting
[ -f /etc/default/openmosix ] && . /etc/default/openmosix
towards the top of /etc/init.d/openmosix, there is still a problem
when the network interface connecting to the cluster is not eth0, the
default used by openmosix's setpe.
The problem lies in /etc/init.d/openmosix where a pre-check of
/etc/openmosix.map is done. This pre-check does not use any of
the settings in /etc/default/openmosix, specifically, it doesn't
use the MYOMID variable to set the node's ID (and thus the IP and thus
the NIC) via the "-p" flag.
I fix this as shown in this diff:
coop:~# diff -u /etc/init.d/openmosix{~,}
--- /etc/init.d/openmosix~ 2003-10-22 09:30:21.000000000 -0400
+++ /etc/init.d/openmosix 2004-07-15 17:17:39.000000000 -0400
@@ -21,6 +21,9 @@
# Description: Start the openMosix kernel extension
### END INIT INFO
+[ -f /etc/default/openmosix ] && . /etc/default/openmosix
+
+
# Define some variables pointing to openMosix's necessary executables
# which should be found in the userland-tools
SETPE="/usr/sbin/setpe"
@@ -76,7 +79,11 @@
# Check the map-file for sanity
if [ $AUTODISC -eq 0 ]; then
- $SETPE -c -f $OMOSIX_MAP &> /dev/null
+ setpe_args=""
+ if [ -n "$MYOMID" ] ; then
+ setpe_args="-p $MYOMID"
+ fi
+ $SETPE $setpe_args -c -f $OMOSIX_MAP &> /dev/null
if [ ! $? -eq 0 ]; then
echo "$OM_MSG_WARN Invalid configuration in map-file $OMOSIX_MAP"
echo "$OM_MSG Falling back to autodiscovery mode using $OMDISCD"
Here are related config files for node 1:
coop:~# egrep -v '^#|^$' /etc/openmosix.map
1 192.168.42.1 4
coop:~# egrep -v '^#|^$' /etc/default/openmosix
MYOMID=1
MIGRATE=yes
BLOCK=no
MFS=yes
-Brett.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-om
Locale: LANG=C, LC_CTYPE=C
Versions of packages openmosix depends on:
ii bash 2.05b-12 The GNU Bourne Again SHell
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libmos 1:0.3.4-7 Libraries which help talk to the O
ii libncurses5 5.4-3 Shared libraries for terminal hand
-- no debconf information
--- End Message ---
--- Begin Message ---
Openmosix was removed in January 2006 because it was "outdated and
buggy". This package was only in woody which is no longer supported.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
