Re: refuse to update certain files upon extraction

Lasse Kliemann <[email protected]> wrote:

> At first, I could not see how sleep(1) could prevent the same file to get =

> archived twice. It will in fact not make any difference when using snapsh=
ots =

> of live filesystems. But if there is a cycle: change files, dump, change =

> files, dump, ..., then it will prevent files to be archived multiple time=
s.

I am no longer sure how to do the sleep(1) correctly..... I'll fall back to
the >=3D solution that has the disadvantage of a probability to archive a f=
ile
when it is not really needed. =


My example from the man page


     echo > /tmp/snapstamp

     mount -r `fssnap -F ufs -o \
         backing-store=3D/var/tmp/EXPORT-NFS.snap /export/nfs` /mnt

     star -c -xdev -sparse -acl -link-dirs level=3D0 -wtardumps \
         f=3Darchive-name dumpdate=3D/tmp/snapstamp \


will also archive some files twice although not needed because  /tmp/snapst=
amp is
older than the snapshot itself.



J=F6rg

-- =

 EMail:[email protected] (home) J=F6rg Schilling D-13353 Be=
rlin
       [email protected]                (uni)  =

       [email protected]     (work) Blog: http://schily.blogspo=
t.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/sch=
ily