On 02/23/10 06:32, Silver Salonen wrote: > I consider it a bug, but looks like devs do not. Any opinions?
I ran into this problem when I first upgraded to 3.0.3. It turned out to be a configuration issue. Make sure you have the desired level of concurrency enabled in ALL applicable resources (i.e, you need "Maximum Concurrent Jobs = 20" set for the SD both in your bacula-sd.conf file AND in your bacula-dir.conf file). If you have different values set in different places, the *lowest* will end up being used. -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 [email protected] [email protected] [email protected] 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 [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
