SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am finding my CPU to be taken up with the process "update-status". I am wondering why this is, and how to correct it. I recently discovered that my update icon wasn't working because zmd wasn't running. I restarted my computer and I no longer get that message, but now update-status seems to run forever. It used to be that it would run for a short time after restart, I'm guessing in order to check for updates when logging in, however, it no longer seems to stop. Any ideas on this one? I am running Open Suse 10.2 with KDE 3.6 on a P4 Prescott 3.0 GHz with 2 GB of RAM
It appears as though I have a Zenworks issue. Adding sources to Yast work but sychronizing with Zenworks fails, and comes back with errors. I am wondering if a reinstall of Zenworks, and all bits and pieces that go with it would be in order?
I have endured similar ZEN problems to these that you describe. In my case, I concluded that the installation of the ZEN package itself wasn't broken; zen is just cpu intensive. But Zen's setup of my update repository catalog was easily and unpredicatbly damaged. It would work for a few updates, then I'd get undecipherable error messages. That might be what's happened to you.
Here are the gory details of what I went through getting updating working on my machine. Perhaps it will save you some time debugging your problem.
SUSE 10.2 is my first encounter with ZEN and I don't find much to like. The YaST online updater in 10.0 worked fine and I wish Novell had left it alone.
I have been experiencing the same thing on a nfs server. In my case I have a SMT server setup for updates plus it also had Novells update server in the list. I disabled the Novell server, then right clicked the zen gnome icon on the systray went to configure and selected not to load on login.
I have a feeling the not load on login probably just doesn't load the icon on the systray, either way I have been running smooth for a few hours now, where as before it was constantly running at 90%-97% cpu time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.