For the part of my routines BackupPC_fixLinks and BackupPC_deleteFile
that actually try to make new links (or delete old ones), I would like
to make sure that nothing else is creating or deleting links to the
pool to avoid collisions.
Specifically, I would like to be able to do the following:
1. Q
[EMAIL PROTECTED] wrote at about 13:49:38 + on Friday, November 21, 2008:
> 02 I would like to conduct actions prior and post creating an archive.
> Specifically mounting a Truecrypt encrypted removable disk. The following
> command line works exactly as required when executed at the com
SamK wrote:
> QUESTIONS:
> 01 The format of the command line required by BackupPC_archiveStart
> is . Is is possible to specify
> multiple without explicitly listing each of them at the
> command line? (perhaps a wildcard) I have tried an asterisk without
> success.
Asterisks are nor
Craig Barratt wrote:
>
> BackupPC_archiveStart is hardcoded to have no compression and use
> a .raw suffix. It's pretty easy to see where to edit it to change
> that. As Nils' mentioned you can easily compress that file, or
> use BackupPC_tarCreate and compress its output (after all,
> BackupPC_
On Thu, Nov 20, 2008 at 06:01:02PM -0300, Cesar Voulgaris wrote:
> Actually there is no permission problems and all is in the same filesystem
> /var/lib/backuppc is mounted in a disk. in fact when creating the partials
> backups with suficient space, Backuppc_nightly deletes correctly the aged
> b
I often use the trick of putting (empty) "-i" files in my critical
directories to prevent the rm * disasters.
But, at least for me, BackupPC seems to be having problems when the
"-i" file is at the root of a share.
Specifically, I get the following error:
Can't open /var/lib/BackupPC//pc/mymachin
