BTW: If you do a 'fink --yes fetch-missing' and hit ctrl-c in the middle,
it will abort the current download attempt, but continue the
fetch-missing. If you hit ctrl-z and kill the fink process, it appears
that fetch-missing keeps running in an orphaned process. Likely as a
result of a user level shell not having permissions to kill a root child,
therefore the child is orphaned??
(I bet the christian right wouldn't be too happy about the last sentence
of that paragraph. Especially if I were to mention that all of this
should be triggered by the cron daemon.)
On Sunday, April 28, 2002, at 12:01 PM, Max Horn wrote:
> At 11:44 Uhr -0400 28.04.2002, Bill Bumgarner wrote:
>>
>> - skip things that have already been downloaded
>
> fink fetch-missing does that.
Doh! Missed that-- and I even read the docs and everything. Cool.
>> - only download those packages that changed since the last download
>
> Hu?
I suppose this is moot if fetch-missing fills in the gaps based on the
current package information. Cool.
>> - automatically retry mirrors
>
> Pass the "--yes" option, then fink will retry several times before going
> on to the next.
Unfortunately, --yes causes Fink to retry forever on files that could not
be downloaded because the server is down or the file has been
renamed/moved. Ahh-- but it gives up after 5 tries and moves on to the
next file. Cool. Anyway to adjust the retries? I would like it to
retry once for the give-up/retry questions and have it cycle through
several mirrors before giving up on those.
>> *sigh* I wish there were 40 hours in the day!
>
> Be careful for what you wish :-)
Clones are likely more feasible anyway. I just don't want to deal with
myself as a two year old.
>
> Max
>
b.bum
....lying there snoring,
breath smelling like a 1948 buick.
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
