I am running Beta 6 on which I installed factory packages from Mar 16: rug zmd libzypp libzypp-zmd-backend zen-updater First when I do a "rug ping" I get: ZMD 7.1.1, Copyright (C) 2005 Novell, Inc. Started at 2006-03-17 06:41:01 (uptime: 0 days, 0 hours, 2 minutes) RSS size: 17568 Network Connected: Yes OS Target: SUSE LINUX 10.0 (i586) Module Name | Description -------------------+------------------------------------------------- Inventory | Software and Hardware inventory module for Linux NetworkManager | NetworkManager support Package Management | Package Management module for Linux ZENworks Server | SOAP methods used by a ZENworks server XML-RPC interface | Export ZMD public interfaces over XML-RPC This is different from what is on the http://en.opensuse.org/Examples_using_rug where OS Target: SUSE LINUX 10.1 (i586) when I do a rug service-add, it quickly gets to 33%, I can see from network activity that it is downloading, after a while net activity stops and it is parsing the data and taking most of the system resources. My question is whether it is totally caput, or is it just a hog and it actually finishes at some point? I have left mine for a few hours but it never moves from 33%. I also used the zen updater gui to add a service which I assume is just a front-end for rug, with the same results. My test machine is an AMD 1600 with 256Mb. Peter 'Pflodo' Flodin
"Peter Flodin"
I am running Beta 6 on which I installed factory packages from Mar 16: rug zmd libzypp libzypp-zmd-backend zen-updater
First when I do a "rug ping" I get: ZMD 7.1.1, Copyright (C) 2005 Novell, Inc. Started at 2006-03-17 06:41:01 (uptime: 0 days, 0 hours, 2 minutes) RSS size: 17568 Network Connected: Yes
OS Target: SUSE LINUX 10.0 (i586)
Module Name | Description -------------------+------------------------------------------------- Inventory | Software and Hardware inventory module for Linux NetworkManager | NetworkManager support Package Management | Package Management module for Linux ZENworks Server | SOAP methods used by a ZENworks server XML-RPC interface | Export ZMD public interfaces over XML-RPC
This is different from what is on the http://en.opensuse.org/Examples_using_rug where OS Target: SUSE LINUX 10.1 (i586)
You need the suse-release from Beta8 to get the target string above;-)
when I do a rug service-add, it quickly gets to 33%, I can see from network activity that it is downloading, after a while net activity stops and it is parsing the data and taking most of the system resources.
My question is whether it is totally caput, or is it just a hog and it actually finishes at some point? I have left mine for a few hours but it never moves from 33%.
It should finish. For now try to add something smaller, e.g. the inst-source-extra tree.
I also used the zen updater gui to add a service which I assume is just a front-end for rug, with the same results.
rug and zen-updater are frontends for zmd.
My test machine is an AMD 1600 with 256Mb.
I've created blocker bug already for the parser that uses up to 800 MB parsing the factory tree - it takes 3 minutes on my laptop, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 17 Mar 2006 at 6:58, Peter Flodin wrote:
My question is whether it is totally caput, or is it just a hog and it actually finishes at some point? I have left mine for a few hours but it never moves from 33%.
Typical tortures for such programs are: 1) strace 2) ltrace 3) valgrind 4) enable debug output 5) gdb ;-) Ulrich
participants (3)
-
Andreas Jaeger
-
Peter Flodin
-
Ulrich Windl