Re: [opensuse] why zypper refresh , works @ term, but not in cron?

On Sun, 2010-08-22 at 01:52 -0700, Linda Walsh wrote:

...

...

Cron /usr/bin/zypper --non-interactive refresh >/dev/null

Uh, er, um....(clackityclackityclackit...(test(test)))...er...**

Um...Yeah...Been there! (ignore smoking keyboard behind the screen) done that!... doesn't help!

Failed to download /content from http://download.opensuse.org/distribution/11.2/repo/non-oss/ Abort, retry, ignore? [a/r/i/?] (a): a

**--(doh!) good point! (unfortunately, didn't lead to the burst of enlightenment one might expect from turning normal output... ;-)

At the console FWIW, I've tried

I tried sending output to >/dev/null, closing it and stdin. No luck in reproducing it interactively on this system.

Very weird...

Could Cron be using too low a priority for zypper to retrieve the data? I wonder what { master:~ # /usr/bin/time /usr/bin/zypper --non-interactive refresh > /home/thpnalb/zyppertest.txt } might show you, if run both from console and then from your cron job. At console here on a painfully slow Sprint Aircard, it returns to the prompt with 5.95user 1.21system 8:09.15 elapsed 1%CPU .... and the zypper output is in the text file. Tom in NM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org