On 08/21/2010 02:44 AM, Linda Walsh pecked at the keyboard and wrote:
Michael S. Dunsaavage wrote:
On 8/20/2010 11:57 PM, Linda Walsh wrote:
On another system, also suse 11.2, but x86-64, a simple 'zypper refresh' is all that was needed (no "--non-interactive")...
Did u get an error trying that ?
nope -- just the 'zypper refresh', was all that was needed.
Also, if you run kudpdateapplet in KDE it refreshes periodically. And it can be set up YaST too.
I usually am not running a kde desktop on that computer. For the
most part I use the command line though I use remote-X for alot of things.
Also, if I may ask, why would you want to run a refresh in cron, unless you're running zypper up in cron too. which isn't a good idea.
Because when I run zypper, if my local cache isn't fairly fresh,
then there's a greater chance that what's in the local cache won't match what is on the server, resulting in occasion glitches or errors.
If the cache is not up to date a refresh is run in the background automatically. There should _not_ be any errors.
When I run zypper interactively, it's because I want to install (or
change) packages, not refresh. When you have several repos, auto-refresh is pain in the posterior.
No, it is a necessary part of the download process. The repos will change because of updated packages being added and your cache needs to match the update so they are in sync. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org