Arno Lehmann wrote:
Hello,
Thinking about directories ending with \n - in the few minutes I thought
about this I couldn't find a solution for this. Except, and that's the
reason for my other suggestions, encouraging the backup admins to really
take care for their filesets - like making sure
hello to everyone,
Is there a method to exclude files from backup that have no change
since specific time or date?
for example, if I want exclude all files that are not changed
before -mm-dd , how can I do?
thanks in advance for any suggest or help
Marco
marco wrote:
Is there a method to exclude files from backup that have no change
since specific time or date?
for example, if I want exclude all files that are not changed
before -mm-dd , how can I do?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
marco wrote:
hello to everyone,
Is there a method to exclude files from backup that have no change
since specific time or date?
for example, if I want exclude all files that are not changed
before -mm-dd , how can I do?
Hello,
Bacula
On Wednesday 29 June 2005 11:47, Russell Howe wrote:
marco wrote:
Is there a method to exclude files from backup that have no change
since specific time or date?
for example, if I want exclude all files that are not changed
before -mm-dd , how can I do?
On Wed, 29 Jun 2005 12:22:29 +0200, Kern Sibbald wrote
On Wednesday 29 June 2005 11:47, Russell Howe wrote:
marco wrote:
Is there a method to exclude files from backup that have no change
since specific time or date?
for example, if I want exclude all files that are not changed
Hello,
marco wrote:
hello Russel, Michel, Kern and thanks for your reply,
I find your suggestions to be useful, especially the command -find-
if I want to exclude all files that have been not modified before 90 dd
i can do from console : find -mtime +90
but, I'm not still familiar with
Kern Sibbald wrote:
I guess my reaction is that if someone really wants \n s in their filenames
(i.e. is crazy enough), then I prefer that they write their own little script
that encloses the names in quotes then Bacula should handle them fine.
I suppose you are not worried about the
To jump in on this discussion:
Kern Sibbald wrote:
On Wednesday 29 June 2005 13:40, Russell Howe wrote:
filenames with \n in them, output by a script:
OK, I see what you mean.
I guess my reaction is that if someone really wants \n s in their filenames
(i.e. is crazy enough), then I prefer
Hi,
Russell Howe wrote:
Kern Sibbald wrote:
I guess my reaction is that if someone really wants \n s in their filenames
(i.e. is crazy enough), then I prefer that they write their own little script
that encloses the names in quotes then Bacula should handle them fine.
I suppose you are
On Wednesday 29 June 2005 14:54, Russell Howe wrote:
Kern Sibbald wrote:
I guess my reaction is that if someone really wants \n s in their
filenames (i.e. is crazy enough), then I prefer that they write their own
little script that encloses the names in quotes then Bacula should handle
On Wed, 2005-06-29 at 13:54 +0100, Russell Howe wrote:
Kern Sibbald wrote:
I guess my reaction is that if someone really wants \n s in their filenames
(i.e. is crazy enough), then I prefer that they write their own little
script
that encloses the names in quotes then Bacula should
Hello,
Russell Howe wrote:
Arno Lehmann wrote:
Thinking about it some more I'd suggest to implement some basic security
features before passing any script output to baculas working parts.
- paths without leading / (or drive letter, for windows) should be
considered an error,
- \0 should be
13 matches
Mail list logo
