On 7/2/07, Mark Post <[EMAIL PROTECTED]> wrote:
> Surprised. But at least it takes away their last possible motivation > to start a "zmd" process that burns my valuable cycles for no reason. No, you'll still need to have zmd started when you want to figure out what patches are available for your system. YaST Online Update uses zmd and rug to figure that out. Once it has done that, you can stop zmd again. This is true, even if you're using YUP to mirror the entire tree of updates.
Assuming you want to have your production systems to find out what patches there are. Back then when I cared about those things, preventive maintenance required planning and testing. I would not want the production system to be interested in what other upgrades there are beyond what I have tested and planned to install. But I understand some people manage their systems differently. Anyhow, I could not resist to complain again about that "zmd" thing that appears to be burning cycles even when there is nothing to do... Rob ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
