From a5e0b213d636e76e72dd412beaf9452791606744 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Tue, 22 Nov 2005 18:21:06 +0000 Subject: [PATCH] Add new Feature Request from Phil git-svn-id: https://bacula.svn.sourceforge.net/svnroot/bacula/trunk@2622 91ce42f0-d328-0410-95d8-f526ca767f89 --- bacula/ChangeLog | 1 + bacula/ReleaseNotes | 1 + bacula/autoconf/configure.in | 2 +- bacula/configure | 2 +- bacula/kes-1.38 | 4 +- bacula/projects | 98 +++++++++++++++++++++++++++++++++++- 6 files changed, 104 insertions(+), 4 deletions(-) diff --git a/bacula/ChangeLog b/bacula/ChangeLog index edd6b404bd..b74ee95511 100644 --- a/bacula/ChangeLog +++ b/bacula/ChangeLog @@ -9,6 +9,7 @@ Changes to 1.38.2: - Fix memory overrun in bfile.c in building OS X resource fork filename. Bug #489 - Add Pool name to SD status output. +- Add Python install dir for Solaris to configure. Bug #492 Changes to 1.38.1: - Apply SunOS patch for ACLs submitted by David Duchscher. diff --git a/bacula/ReleaseNotes b/bacula/ReleaseNotes index d0efbc54d1..363546204e 100644 --- a/bacula/ReleaseNotes +++ b/bacula/ReleaseNotes @@ -14,6 +14,7 @@ Changes to 1.38.2: - Fix memory overrun in bfile.c in building OS X resource fork filename. Bug #489 - Add Pool name to SD status output. +- Add Python install dir for Solaris to configure. Bug #492 Changes to 1.38.1: - Corrected ACL for Solaris (David Duchscher and Attila Fulop). diff --git a/bacula/autoconf/configure.in b/bacula/autoconf/configure.in index 44c232f29e..1844cb79fe 100644 --- a/bacula/autoconf/configure.in +++ b/bacula/autoconf/configure.in @@ -604,7 +604,7 @@ AC_ARG_WITH(python, PYTHON_LIBS= if test "$withval" != "no"; then if test "$withval" = "yes"; then - for python_root in /usr /usr/local; do + for python_root in /usr /usr/local /usr/sfw; do if test -f $python_root/include/python2.2/Python.h; then PYTHON_INCDIR=-I$python_root/include/python2.2 PYTHON_LIBS="-L$python_root/lib/python2.2/config -lpython2.2" diff --git a/bacula/configure b/bacula/configure index a19250e0d5..48c8e5a5bf 100755 --- a/bacula/configure +++ b/bacula/configure @@ -14948,7 +14948,7 @@ if test "${with_python+set}" = set; then PYTHON_LIBS= if test "$withval" != "no"; then if test "$withval" = "yes"; then - for python_root in /usr /usr/local; do + for python_root in /usr /usr/local /usr/sfw; do if test -f $python_root/include/python2.2/Python.h; then PYTHON_INCDIR=-I$python_root/include/python2.2 PYTHON_LIBS="-L$python_root/lib/python2.2/config -lpython2.2" diff --git a/bacula/kes-1.38 b/bacula/kes-1.38 index ead3818bda..f3491fef9a 100644 --- a/bacula/kes-1.38 +++ b/bacula/kes-1.38 @@ -6,7 +6,8 @@ General: Changes to 1.38.2: 20Oct05 - Fix crash in tray-monitor when daemon disconnects. Bug #479. -- Fix bnet-server bug found on OpenBSD. Bug #486 +- Fix bnet-server bug found on OpenBSD. Bug #486 (bug originator + says this does not fix *his* bug). - Fix cancel failure bug. Bug #481 - Fix failure when Pool name has spaces. Bug #487 - Fix SD crash in autochanger code. Mutex failure. Bug #488 @@ -14,6 +15,7 @@ Changes to 1.38.2: - Fix memory overrun in bfile.c in building OS X resource fork filename. Bug #489 - Add Pool name to SD status output. +- Add Python install dir for Solaris to configure. Bug #492 Changes to 1.38.1: 14Oct05 diff --git a/bacula/projects b/bacula/projects index a671a88ee1..55fec7bf02 100644 --- a/bacula/projects +++ b/bacula/projects @@ -1,7 +1,7 @@ Projects: Bacula Projects Roadmap - 08 November 2005 + 22 November 2005 Below, you will find more information on future projects: @@ -399,6 +399,102 @@ Item 17: Quick release of FD-SD connection Why: Makes backup of laptops much easier. +Item 18: Add support for CACHEDIR.TAG + Origin: Norbert Kiesel + Date: 21 November 2005 + Status: + + What: CACHDIR.TAG is a proposal for identifying directories which + should be ignored for archiving/backup. It works by ignoring + directory trees which have a file named CACHEDIR.TAG with a + specific content. See + http://www.brynosaurus.com/cachedir/spec.html + for details. + + From Peter Eriksson: + I suggest that if this is implemented (I've also asked for this + feature some year ago) that it is made compatible with Legato + Networkers ".nsr" files where you can specify a lot of options on + how to handle files/directories (including denying further + parsing of .nsr files lower down into the directory trees). A + PDF version of the .nsr man page can be viewed at: + + http://www.ifm.liu.se/~peter/nsr.pdf + + Why: It's a nice alternative to "exclude" patterns for directories + which don't have regular pathnames. Also, it allows users to + control backup for themself. Implementation should be pretty + simple. GNU tar >= 1.14 or so supports it, too. + + Notes: I envision this as an optional feature to a fileset + specification. + +Item 19: Implement new {Client}Run{Before|After}Job feature. + Date: 26 September 2005 + Origin: Phil Stracchino + Status: + + What: Some time ago, there was a discussion of RunAfterJob and + ClientRunAfterJob, and the fact that they do not run after failed + jobs. At the time, there was a suggestion to add a + RunAfterFailedJob directive (and, presumably, a matching + ClientRunAfterFailedJob directive), but to my knowledge these + were never implemented. + + An alternate way of approaching the problem has just occurred to + me. Suppose the RunBeforeJob and RunAfterJob directives were + expanded in a manner something like this example: + + RunBeforeJob { + Command = "/opt/bacula/etc/checkhost %c" + RunsOnClient = No + RunsAtJobLevels = All # All, Full, Diff, Inc + AbortJobOnError = Yes + } + RunBeforeJob { + Command = c:/bacula/systemstate.bat + RunsOnClient = yes + RunsAtJobLevels = All # All, Full, Diff, Inc + AbortJobOnError = No + } + + RunAfterJob { + Command = c:/bacula/deletestatefile.bat + RunsOnClient = Yes + RunsAtJobLevels = All # All, Full, Diff, Inc + RunsOnSuccess = Yes + RunsOnFailure = Yes + } + RunAfterJob { + Command = c:/bacula/somethingelse.bat + RunsOnClient = Yes + RunsAtJobLevels = All + RunsOnSuccess = No + RunsOnFailure = Yes + } + RunAfterJob { + Command = "/opt/bacula/etc/checkhost -v %c" + RunsOnClient = No + RunsAtJobLevels = All + RunsOnSuccess = No + RunsOnFailure = Yes + } + + + Why: It would be a significant change to the structure of the + directives, but allows for a lot more flexibility, including + RunAfter commands that will run regardless of whether the job + succeeds, or RunBefore tasks that still allow the job to run even + if that specific RunBefore fails. + + Notes: By Kern: I would prefer to have a single new Resource called + RunScript, and within that resource an additional directive: + + RunBeforeJob = Yes|No + + If no, it runs it after the job. + + ============= Empty RFC form =========== Item n: One line summary ... Date: Date submitted -- 2.39.5