Title: Re: [Sisuite-devel] python-xml in systemimager.spec (trunk)
Hi Andrea:
 
I rebuilt trunk with your updates and monitoring seems to work again, however I am still having network issues.  I have an Intel PRO/100+ NIC on the client node and for whatever reason, the following is the output of dmesg | grep Intel:
 
Intel(R) PRO/1000 Network Driver - version 6.3.9-k4-NAPI
Copyright (c) 1999-2005 Intel Corporation.
Intel(R) PRO/10GbE Network Driver - version 1.0.100-k2
Copyright (c) 1999-2005 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
Intel ISA PCIC probe: not found.
 
Is that normal?  It appears that multiple drivers were loaded.  Also, I think this is not a module as I don't see it in "lsmod" - so this is probably loaded in kernel?
 
BTW, I'd like to suggest the following patch for si_monitortk - minor text formatting that makes it look a bit more condensed:
 
Index: sbin/si_monitortk
===================================================================
--- sbin/si_monitortk   (revision 3480)
+++ sbin/si_monitortk   (working copy)
@@ -681,10 +681,10 @@
         } else {
             if ($client->{$mac}->{'speed'} < 1000) {
                 $client->{$mac}->{'speed'} =
-                    sprintf("%.3fKB/s", $client->{$mac}->{'speed'});
+                    sprintf("%.0fKB/s", $client->{$mac}->{'speed'});
             } else {
                 $client->{$mac}->{'speed'} =
-                    sprintf("%.3fMB/s", $client->{$mac}->{'speed'} / 1000);
+                    sprintf("%.2fMB/s", $client->{$mac}->{'speed'} / 1000);
             }
         }
                # Format the total amount of RAM.
 
I think the function "autodetect_hardware_and_load_modules()" in "functions" is no longer necessary, I'll work on removing that as well as other references to "discover".
 
Cheers,
 
Bernard


From: Andrea Righi [mailto:[EMAIL PROTECTED]
Sent: Sat 25/03/2006 14:44
To: Bernard Li
Cc: sisuite-devel@lists.sourceforge.net
Subject: Re: [Sisuite-devel] python-xml in systemimager.spec (trunk)

Bernard Li wrote:
> Okay, how about I put it as BuildRequires for "systemimager" and
> Requires for "systemimager-server"?

seems good.

>
> BTW, I think I was able to successfully build SystemImager 3.7.2 x86
> RPM and I'm testing it right now...  however, there must be something
> wrong with the node's network card configuration (probably
> udev/hotplug related), because it is taking forever to image a
> node...  also, I think si_monitor is broken - it gets stuck in the
> initialization phase and virtual console says "host unreachable:
> cannot gather previous messages!"

have you tried also with the most recent trunk? I did some fixes for
monitoring with udev...

Cheers,
-Andrea

Reply via email to