:02, Clark Hartness wrote:
Arno said:
alternatively, you could run your script from a RunScript resource in the
Job.
I am writing a filelist to the CLIENT MACHINE which I am using the
following in the include as such in the FileSet
If that's all your script does, you can use its output
15:17, Clark Hartness wrote:
Hi Arno,
-Original Message-
From: Arno Lehmann [mailto:a...@its-lehmann.de]
Sent: Wednesday, December 02, 2009 4:19 AM
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Is it possible to Set a Job
Level with a
Schedule
I know that subject doesn't make a lot of sense
I have a job that I manually start at the completion of a script to backup a
list of files on the Client.
I don't want the job to run on Schedule but I would like to be able to set the
level of the Job by days following something like this
the Job?
Hello,
01.12.2009 17:56, Clark Hartness wrote:
I know that subject doesn't make a lot of sense
I have a job that I manually start at the completion of a script to
backup a list of files on the Client.
Manually meaning you pass something like 'run job=name yes' to bconsole?
Yes we
Arno said:
alternatively, you could run your script from a RunScript resource in the Job.
I am writing a filelist to the CLIENT MACHINE which I am using the
following in the include as such in the FileSet
Include {
Options {
compression=GZIP
signature = MD5
}
#
I am calling a ruby script that decends a workspace and writes a list of files
that need to be protected on the client to /var/lib/bacula/backup.files
The Script functions as it should.
With my setup included below I call the script on the client before the job to
write the file.
If
Hello,
Have you really a file named :
File =
/mnt/fog006/ddrswa/jckh/dlr_leopard_dev_12/dfb/doc/001-10043-dfb-BROS-starB.
doc
on your system ? If yes, i'm very surprised.
Don't forget to read what you've written 10 lines before:
The names should start in column 1 and should not be quoted even
I am attempting to send a list of files to Bacula from the Client using
this syntax described in the manual:
Any file-list item preceded by a less-than sign () will be taken to be
a file. This file will be read on the Director's machine at the time the
Job starts, and the data will be assumed
