Keep in mind that this is number of retries per download operation. We'd retry 3 times to get a manifest, just as we'd retry three times to get ~1mb of file data. Retrying 20-30 times for files would mean that you could end up waiting up to 15 minutes for a chunk, in the worst case. That hardly seems acceptable to me.
-j On Tue, Jun 10, 2008 at 05:21:54PM -0700, Brock Pytlik wrote: > [EMAIL PROTECTED] wrote: > > [snip] > > They are the same variable, it's just that in filelist MAX_TIMEOUT_COUNT > > is imported explicitly, whereas all of misc is imported in image. At > > least right now, the timeouts are one and the same. Was there a case > > you're envisioning where we'd want to set these separately? > > > > -j > > > > I'm not sure if there's a good use case or not for it. My thinking was > roughly that manifests are (usually) small compared to the files that > are downloaded from the depot. I might want to set the manifest timeout > to 1, since if getting manifests times out (more than once), it suggests > that getting larger files is going to be very painful. So I might to set > manifests to 1, while setting the file timeout to 20 or 30 basically > saying if I am going to try getting the larger files, continue trying > until you succeed. I'm not sure if this really makes sense, or is > realistic, but it tickled the back of my brain, so I wanted to at least > throw it out there and see what people thought. > > Brock > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
