This is definitely a very minor issue, but anyway... I have a Pool=Default line in job defaults, that pool doesn't actually exist in my system (the definition exists, but it has no tapes).
Further, in Schedule section I always specify pool to be used (typically "Cycle" or "Archieve"), it works correctly and is shown in log like this: Pool: "Cycle" (From Run pool override) However, when I for some reason need to run an extra job manually from bconsole, and modify the pool to be used before accepting the job to be run, the pool change actually works, and the proper pool name is shown in the log, but it still keeps saying "From Job Resource" as a source for the pool setting: Pool: "Cycle" (From Job resource) So, the pool was properly changed from Default to Cycle, but pool "Cycle" is not definetely specified in the job resource like the line above says (job definition inherits the pool "Default" from Job Defaults), but it was manually modified when entering the run command in bconsole. Just wanted to mention about this. I can live with this, it's up to the developers to decide if this is the desired way of operation or if there is any need to change something. Currently, I'm running 2.2.6 on CentOS5, but the same behaviour has existed in several earlier releases (for as long as I can remember...) -so this didn't appear for the first time very recently. Regards, Timo ------------------------------------------------------------------------- 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
