[pca] xref aged 1603 considered up to date?

Martin Paul martin.paul at univie.ac.at
Mon Nov 4 12:29:21 CET 2013


Glen,

> Based on the end time (09:54:15) and the ctime of /var/tmp/patchdiag.xref (09:54:15) if looks like the pca error processing may have resulted in the updating of ctime.

It's probably because PCA moves patchdiag.xref to patchdiag.xref.tmp 
before trying the download, so it has a backup copy if the download fails.

> (Note:  I checked the ctime for patchdiag.xref on several servers and it appears that NetBackup is causing ctime to be updated when the file is backed up.)

Yes, looks like, after some googling. It does that for a similiar 
purpose - marking files which have been backuped for the nexte 
incremental backup.

BTW, do you know PCA's "-y, --nocheckxref" option? It will make PCA skip 
the check for updates of the xref file. If you use it with a frozen 
patchdiag.xref file, everything should be fine.

Martin.




More information about the pca mailing list