>>>>> On Wed, 24 Jan 2024 18:00:56 +0100, Marco Gaiarin said:
>
> Suppose that setting 5 or 1 options depend on setting options; eg, it is
> totally unuseful to have:
> Options {
> Signature = MD5
> accurate = <...>1
> }
>
> so, calculating MD5 and checking SHA1.
In fact, I think that will check MD5. The implementation can only store one
type of checksum in the catlog and incremental backups just check whatever was
stored (and assume it is the same type as in the original backup).
> But options 'i' what mean? Compare THE inode number? Or the number of inodes
> of that particolar file?
'i' is the st_ino field in the stat, i.e. the number that uniquely identifies
the data for the file in the file system. Note that there is always exactly 1
inode that references the data for each file in a UNIX file system.
> Also, 'n' mean soft or hard link? What is the interrelation between 'i' and
> 'n' options?
'n' is the st_nlinks field in the stat, i.e. the number of hard links to the
inode. Nothing records the number of soft links.
> Anyway, i'm currently trying:
>
> Options {
> Signature = MD5
> accurate = pugsmcd5
> }
I think you need to remove 'c' otherwise you will get the same results as
before when the ctime changes.
__Martin
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
