-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm not under the impression that anything changed with Max Wait Time anyway.
Christian Sakshaug wrote: > You have probability right, RelaseNotes file :) > > But I cannot se anything about "Max Wait Time", only perhaps. > > "- New Client Connect Wait directive in Storage daemon so that > users can configure how long SD waits for FD connection." > > Anyway, it works :-) > > > Regards, > Christian Sakshaug > > > Ryan Novosielski skrev: > Christian Sakshaug wrote: >>>> Good morning >>>> >>>> It seems like everything is just fine again. Last night I removed the >>>> "Max Wait Time" from the job resource and everything works again >>>> (every job is OK). >>>> >>>> I have probably used the "Max Wait Time" wrong in my configuration. >>>> >>>> What about to make a "Migrate from ver >= ver" section in the user >>>> guide where it will be listed the configuration changes and other >>>> thing that is importent between the version. Some of the other Open >>>> Source system I'm using has this feature and it making the upgrade >>>> job much easier and safer. >>>> >>>> It is probably not so important between the "major updates, 1.x to >>>> 2.x" but between 2.0.3 to 2.2.0, 2.2.0 -> 2.2.3 has been nice. >>>> >>>> Perhaps you guys have allready written that, perhaps I have miss it. > > Pretty sure that stuff is in the release notes -- I haven't upgraded > anew in quite some time, but the last time I needed that information, > that's where it was. > >>>> Christian Sakshaug skrev: >>>>> Hey >>>>> >>>>> Have tested some more now, it seems that jobs that I was getting >>>>> error after "normal schedule" is working when I have a small number >>>>> of concurrent jobs running. >>>>> >>>>> I wonder what have been change since 2.0.3 that could have this >>>>> affects? >>>>> >>>>> I have been reading the changelog and documentation and I can not >>>>> find anything special except the "critical bug fixed in 2.2.3" that >>>>> trigger my upgrade at the first place. >>>>> >>>>> Actually I have 3 different bacula site-location that have been in >>>>> used for some times now without troubles. I have upgrade two of >>>>> those with 2.2.3 and I having trouble with both. But with the third >>>>> (running 2.0.3) everything is working great/normal. > - -- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG6p9Wmb+gadEcsb4RAtEIAJ9HF9YpZW6p0f/YO9W3l1IEQTZjKgCfRAzw UESIbd/V9Zjl89/GM1WAxpo= =9/Y6 -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
