A DIFFERENT yum/up2date problem...

[Allan Metts]

I am absolutely baffled.  /var/log/yum.log shows all of these packages were 
updated at 5:26 a.m. this morning.   I was sound asleep at that time -- and 
unless my dogs have picked up Linux, no one else did it.  My system time is 
accurately synced to ntp, and crontab is empty for all users.

I ran "nohup up2date -u" from the command line the day before, and 
nohup.out showed a failure.  Does up2date include some sort of periodic 
retry logic?

If not, the only thing I can think of is that yesterday's process took 12 
hours to successfully finish the download on a broadband connection, and I 
looked at the wrong nohup.out to check the results.

A-----



At 06:47 PM 1/18/2004, you wrote:
>On Sun, 18 Jan 2004, William Hooper wrote:
>
> >
> > Allan Metts said:
> > > Hi Alexander,
> > >
> > > Thanks for the suggestion.  Unfortunately, rebuilding the rpm database
> > > doesn't solve the problem.  Yum still hits the "base", then the "Released
> > > Updates" repositories, and reports that there's nothing new.
> > >
> > > Anything else I can try?
> >
> > At this point I would verify that the updates haven't been applied (by a
> > cron job perhaps?).
> >
> > I see the newest update on the Duke mirror is the 2149 kernel.  What does
> > do you have installed for the kernel?
>
>Or you could just look in the logs. :-)
>
>Tom
>
>
>--
>fedora-list mailing list
>fedora-list at redhat.com
>To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list