On Thu, 2008-10-09 at 10:34 -0400, Michael DeHaan wrote:
> seth vidal wrote:
> > On Wed, 2008-10-08 at 15:36 -0400, Michael DeHaan wrote:
> >   
> >> When putting cobbler reposync on crontab occasionally a network problem 
> >> can occur that prevents synchronization of a specific repository.
> >>
> >> Assume the following commands
> >>
> >> Example:
> >>
> >> cobbler repo add --name=f9-updates-i386 
> >> --mirror=ftp://download.fedora.redhat.com/pub/fedora/linux/updates/9/i386.newkey/
> >> cobbler repo add --name=jimmy-unstable-server-packages 
> >> --mirror=http://example.com/repo
> >> cobbler reposync
> >>
> >> In the above example, the reposync will fail because there obviously is 
> >> no repo there at example.com.   That's silly, but here are two reasons 
> >> but suppose the server is busy or you have a temporary network glitch.   
> >> You still want to synchronize everything else.
> >>
> >> In current versions of Cobbler you can still sync repos one and a time, 
> >> but that's annoying in a crontab:
> >>
> >> cobbler reposync --only=f9-updates-i386
> >>
> >> So, to make this /much/ nicer, I added retry logic to "cobbler reposync".
> >>
> >> cobbler reposync --tries=3
> >>
> >> This will retry each repo 3 times.   However, it will still eventually 
> >> fail because the example.com repo doesn't exist.
> >>
> >> If you want to reposync all repos but not have the failure with one of 
> >> them crash the whole thing, you can do:
> >>
> >> cobbler reposync --tries=3 --no-fail
> >>
> >> This will delay the failure until the end rather than stopping midstream.
> >>
> >> Choice of the retry value is up to you.   The try number defaults to 1 
> >> and "fail early" to be consistent with previous behavior, but this 
> >> should make things much nicer for those who want to put reposync on cron.
> >>
> >> I'll update the Wiki and (devel branch) manpage to reflect these added 
> >> options shortly.
> >>
> >>     
> >
> > Might be best to get this into upstream reposync. You're right, for
> > reposync purposes you don't need to make sure all the repos are present.
> >
> > -sv
> >
> >
> > _______________________________________________
> > cobbler mailing list
> > [email protected]
> > https://fedorahosted.org/mailman/listinfo/cobbler
> >   
> 
> I'd definitely like to work on yum some. Good idea, I'll see about doing 
> this.
> 
> FWIW, cobbler also does some rsync games, where it can rsync something 
> and then run createrepo on the output. So the original source doesn't 
> have to be a repo. So that's why we have it a layer up here.
> 
> Still useful upstream though.

You don't need to put it into yum. It can just show up in reposync. But
you're welcome to contribute to yum, too :)


-sv


_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler

Reply via email to