On 03/08/10 13:32, Jesper Krogh wrote:
> Phil Stracchino wrote:
>> If the problem still occurs, something else is going on. But this
>> should fix the problem in probably >99% of cases in which the 50-second
>> timeout is only infrequently being exceeded.
>
> It hugely depends on your fileset sizes.. I have some in the order of
> 10m records.. and exceeding 100s is definately not a problem.
Yes, but when you're dealing with filesets that large, you're going to
be REGULARLY exceeding it, right? Doubling it to 100s *should* take
care of almost all cases in which it just occasionally goes over 50s.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
alaric AT caerllewys DOT net alaric AT metrocast DOT net phil AT
co.ordinate DOT org
Renaissance Man, Unix ronin, Perl hacker, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|