Robert Lewis wrote: > Robert Lewis wrote: > >> In addition, why does it hang for a very long time at the end of >> >> an updater operation at 99%. In fact often it goes to 100% and >> then drops back to 99%. During this time top reports: >> >> 7222 root 25 0 82432 44m 6248 R 91.7 4.4 5:09.40 update-status >> >> That's 91.7% CPU utilization for a very very long time. >> This is ridiculous. >> Is it a race condition or what? >> >> > For example: > A) Do we have a buy in from the developers that the issues are real and > worthy > of fixing? > It would probably really help if you would realize in 10.2 there are now 2 choices. One is called zen-updater, the other is called opensuseupdater. By you subject, which one would you suspect you are talking about? Wrong, you are describing zen-updater. By confusing the 2 you do not add clarity to the updater problems. > B) That the mechanism is way to slow often taking an hour or tmore to > install one rpm > Since the 2 are aimed at different use scenarios, maybe you are making this harder than NOW is necessary. The developers do realize there are problems. That is why they created opensuseupdater. Try it, you'll like it. It is much more lightweight than zen-updater, only trying to notify the user of security updates. Zen-updater is designed to notify of an update in every configured repository. Which do you think would need more resources? Add to that load the fact that it isn't just a matter of seeing something newer, but making sure it isn't a rogue package by verifying the gpg signature. That is why IMHO zen-updater is doomed by design. I would suggest trying the product you mention in your subject.
-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
