Hello, On Thursday 01 November 2007 16:22, GDS.Marshall wrote: > I am working on a patch for "status dir" and expired volumes. I am not > sure if this is the right place to ask this kind of question or if I am > just going to put peoples backs up. I hope the latter is not the case.
This is the correct place, and I doubt that anyone will be upset certainly not me. > > >From debugging, I believe I need to modify find_next_vol_for_append (I can > > do this bit). I have determined, that in ua_status.c line 412 (ps the > debugging is really good and helpful thank you) sp->runtime contains the > time of the next run, jcr->run_time is 0 and jcr->sched_time is the time > now. What do I screw up if anything by updating jcr->sched_time with the > sp->runtime value just prior to ua_status.c line 412? This would allow me > to use jcr->sched_time in the sql. Modifying jcr->sched_time is possible to cause problems someplace. Can you explain why you want to change it and for which SQL statement? That might help tie down what would be the right way to approach it or at least allow me to verify that modifying sched_time in this case will not be a problem. I assume you are trying to make as if the job is actually run in the future, which would be nice ... By the way, please take a look at www.bacula.org -> FSFE License, fill out two copies, send them in, and let me know by email when you have done so. That speeds up accepting any possible patch you would submit. Regards, Kern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
