> I also think that for a longer term, "cleaner" solution it might be a good > idea to add a RunAfterJob, which runs one or more jobs after the current > job, > and by "runs", I mean it starts the job within Bacula, not through a > script > as RunScript does. This, however, needs to be carefully examined -- Eric > what do you think?
I'm not Eric, but I'd observe that job scheduling is general is becoming more and more complex, and perhaps it would be useful to entirely separate the job execution from job scheduling and dependency management. This might be a smart point to consider doing so. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
