10.1: zmd... anyone else have problems with it?
Since upgrading from 10.0 to 10.1, every time I want to do anything that involves adding or removing packages with Yast2, zmd wants to get involved. For instance, bringing up "yast2 sw_single" will get zmd running with the following command line: /usr/lib/zmd/query-system /var/lib/zmd/zmd.db ...and it will take literally two or three minutes for the program to come up to the package selection screen. In the meantime, CPU utilization goes up to 2+ according to top, and the system is dog slow. Since nobody else has complained here about it, I figure it must have something to do with my system. This zmd stuff hammers my system so bad that I am considering downgrading back to 10.0. Why do we need zmd, and how is it an improvement over the 10.0 way of doing things? Michael -- San Francisco, CA
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-05-15 at 05:14 -0700, Michael Nelson wrote:
Since nobody else has complained here about it, I figure it must have something to do with my system. This zmd stuff hammers my system so bad that I am considering downgrading back to 10.0.
Try dissabling it. Can't say yet if this is good advice or not, though. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEaI4PtTMYHG2NR9URAtGMAJ9tJ+eLMINuuIfWQic0PturOtXQNgCfXuG3 xbuMuGzW4gYWMbowyiFpytA= =d99A -----END PGP SIGNATURE-----
On Mon, May 15, 2006 at 04:19:57PM +0200, Carlos E. R. wrote:
Try dissabling it. Can't say yet if this is good advice or not, though.
At least as a test, I removed the following packages: suseRegister rug zen-updater zmd libzypp-zmd-backend So far, the stuff I have used still works, and the massive delays are gone. I'm using apt-get for updates. Michael -- San Francisco, CA
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-05-15 at 07:43 -0700, Michael Nelson wrote:
On Mon, May 15, 2006 at 04:19:57PM +0200, Carlos E. R. wrote:
Try dissabling it. Can't say yet if this is good advice or not, though.
At least as a test, I removed the following packages:
suseRegister rug zen-updater zmd libzypp-zmd-backend
It should have been enough with "rczmd stop", I think.
So far, the stuff I have used still works, and the massive delays are gone. I'm using apt-get for updates.
That pinpoints zmd as problematic... - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEaOjitTMYHG2NR9URAhUQAJ9QudBSJPzyePn7wbcalW3jM6r2xgCeMTQS vQWYgGP/zgYHNifVk4uH4Zg= =6P2c -----END PGP SIGNATURE-----
On Monday 15 May 2006 16:47, Carlos E. R. wrote:
It should have been enough with "rczmd stop", I think.
So far, the stuff I have used still works, and the massive delays are gone. I'm using apt-get for updates.
That pinpoints zmd as problematic...
I'm having /some/ kind of problem with zmd/YOU/rug... not well defined yet but long 'thinking hangs' even after turning off zmd... I can't add/remove installation sources or 'register'... every combination of checkboxes yields "there are no packages to register"... I can't run 'Software Management'. And what is the difference between "Online Update Configuration" and "Online Update Setup"? I'm afraid that poor little SuSEwatcher applet is starting to look awfully tempting right now. Is it me, or is there really a problem with this aspect of 10.1? TIA & regards, Carl
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-05-15 at 19:03 -0400, Carl Hartung wrote:
I'm having /some/ kind of problem with zmd/YOU/rug... not well defined yet but long 'thinking hangs' even after turning off zmd... I can't add/remove installation sources or 'register'
Exit yast. Change only one source, then exit yast again. I found that sometimes that's the only thing that works for changes to be accepted. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEaQ2qtTMYHG2NR9URAj0VAJ41rXyWF2WJmDpy7NTsQBmRo84D1ACggsX8 5VgzHF0S6w5EVXUueXDzV3s= =PeF0 -----END PGP SIGNATURE-----
On Monday 15 May 2006 19:24, Carlos E. R. wrote:
Exit yast. Change only one source, then exit yast again.
I found that sometimes that's the only thing that works for changes to be accepted.
Thanks a lot, Carlos. I'll give it a try later tonight and report back (I"m in 10.0 right now.) Carl
I would just share this with you ... I was having the same problem with excessive use of the CPU with this new zmd I did not turn it off yet but after changing to Xgl and Compiz things return to normal.. zdm still claims that there is a lot of update which I ignore for now. I will try to return to SuSEWatcher as this was working great in SuSE 10.0 if it is possile.
cheer..
Carl Hartung
Exit yast. Change only one source, then exit yast again.
I found that sometimes that's the only thing that works for changes to be accepted.
Thanks a lot, Carlos. I'll give it a try later tonight and report back (I"m in 10.0 right now.) Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com |__|___|___|__\\|// - ?__|___|_____|___|_____| |__|___|___|__(o o)______|___|_____|___|_____| |__|___|___oOOO(_)OOOo____|___|_____|___|_____| email : ephlodur@rocketmail.com What we need is Awareness we can't get carelless. --------------------------------- Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2¢/min with Yahoo! Messenger with Voice.
On Monday 15 May 2006 19:35, Carl Hartung wrote:
Thanks a lot, Carlos. I'll give it a try later tonight and report back (I"m in 10.0 right now.)
Follow-up: It worked, Carlos. Thanks for the heads-up! My impression is that something in the installation source verification process is still intolerant of server-side delays, including those induced by incorrect paths (which has always been the case.) It seems now to take an excessive amount of time to error out... when it *does* error out... but it now acts as though it's having a difficult time distinguishing between proper, or 'hard' errors (such as incorrect paths) and 'soft' errors like sluggish responses from busy servers. regards, Carl
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-05-16 at 08:29 -0400, Carl Hartung wrote:
Follow-up:
It worked, Carlos. Thanks for the heads-up!
Good. Or bad, it shouldn't be that way, it is a bug (and I think it was reported as solved).
My impression is that something in the installation source verification process is still intolerant of server-side delays, including those induced by incorrect paths (which has always been the case.) It seems now to take an excessive amount of time to error out... when it *does* error out... but it now acts as though it's having a difficult time distinguishing between proper, or 'hard' errors (such as incorrect paths) and 'soft' errors like sluggish responses from busy servers.
Once I saw that the network was active, downloading something; but Yast doesn't say a word about what it is doing, so it seems hung. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEad4btTMYHG2NR9URAjYBAJ0b8tSFgTlBMOtdnLtPmZfzh9InXwCgi/g2 9qCA+cMEo9fzcS63dLTUdEo= =+j5l -----END PGP SIGNATURE-----
participants (4)
-
Carl Hartung -
Carlos E. R. -
Michael Nelson -
MindBender