On 02/15/16 05:02 PM, David Pearce wrote:
> Thanks for the clue about "AllowedJobCommand". Works for my purpose.
>
> So if "accurate=NO" where in the code do I look for the OS specific checks
> for whether it gets backed up for an incremental backup?
>
Its not to OS specific as it seems but you find it here
src/findlib/find_one.c:305 check_changes() function.
Which essentially does this when now specific check function is specified
(e.g. accurate registers its own check function.)
/*
* For normal backups (incr/diff), we use this default behaviour
*/
if (ff_pkt->incremental &&
(ff_pkt->statp.st_mtime < ff_pkt->save_time &&
(bit_is_set(FO_MTIMEONLY, ff_pkt->flags) ||
ff_pkt->statp.st_ctime < ff_pkt->save_time))) {
return false;
}
So it checks the st_mtime and if not FO_MTIMEONLY(set by the mtimeonly
fileset option) is set also the st_ctime.
>From my Solaris manpage
st_mtime Time when data was last modified. Some of the functions
that change this member are: creat(), mknod(), pipe(),
utime(), and write(2).
st_ctime Time when file status was last changed. Some of the func-
tions that change this member are: chmod(2), chown(2),
creat(2), link(2), mknod(2), pipe(2), rename(2),
unlink(2), utime(2), and write(2).
I think on all UNIX/Linux systems you can set or reset st_mtime but never
st_ctime.
--
Marco van Wieringen [email protected]
Bareos GmbH & Co. KG Phone: +49-221-63069389
http://www.bareos.com
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens,
P. Storz, M. v. Wieringen
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
