You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could there be an option to disable symlinks when running "create" with "-R" please?
I run par2 on a directory which has some critical files. Unfortunately this directory also has some symlinks, whose targets are elsewhere in the file system.
I did not realise par2 was following the symlinks. Sometime later, when I ran a verify, par2 showed some files needing repair.
I made the mistake of not checking exactly what files were reported as broken, and not properly worrying about why they would be broken, and blindly did a repair. It took me a while to realise this had ended up essentially reverting changes to those target files, which as I said were outside the directory I gave to "par2 create".
At the moment my workaround is to include the following in my script, but it would be nice if that were not needed.
find $@ -type l | tar --remove-files -T - -cvf save.symlinks
... run the "par2 c [...]" here...
tar -xvf save.symlinks && rm save.symlinks
The text was updated successfully, but these errors were encountered:
Hi,
Could there be an option to disable symlinks when running "create" with "-R" please?
I run par2 on a directory which has some critical files. Unfortunately this directory also has some symlinks, whose targets are elsewhere in the file system.
I did not realise par2 was following the symlinks. Sometime later, when I ran a verify, par2 showed some files needing repair.
I made the mistake of not checking exactly what files were reported as broken, and not properly worrying about why they would be broken, and blindly did a repair. It took me a while to realise this had ended up essentially reverting changes to those target files, which as I said were outside the directory I gave to "par2 create".
At the moment my workaround is to include the following in my script, but it would be nice if that were not needed.
The text was updated successfully, but these errors were encountered: