"Donald R. Spoon" <[EMAIL PROTECTED]> writes: > The reason I ask is that I have about 5 computers I am trying to keep > updated here. Doing each one manually each day coupled with the > "re-trys" is getting to be quite a PITA. It is a good thing I am > retired, but the wife is getting a little peeved. <g> > > I have been toying with the idea of setting up a cron job to do the > updates, but I haven't figured out a satisfactory way to detect this > condition and abort the update then try again a bit later.
If you're tracking unstable, I would recommend doing interactive updates. > Maybe a script that checks for the presence of this error code and then > exits without completing + logged message to that effect?? I guess you > could set the timing of the cron job that calls this script such that it > gives the delay you want...dunno. Something like this? http://lists.debian.org/debian-user/2001/debian-user-200111/msg01963.html -- Brian Nelson <[EMAIL PROTECTED]>
