bobafetthotmail / par2drive Goto Github PK

# create test directory:
username@computer:~> mkdir ~/par2test/

# create empty file:
username@computer:~> touch ~/par2test/a
# create non-empty file:
username@computer:~> </dev/urandom head -c 10m >~/par2test/b

# run par2test in test directory
username@computer:~> cd ~/par2test/
username@computer:~/par2test> par2drive sync .
working on ./a
was modified, generating again the parity files
Skipping 0 byte file: /home/username/par2test/a
You must specify a list of files when creating.
Warning! error detected, terminating batch processing.

username@computer:~/par2test> ls .
a  b

As the above shows, any 0 byte files will prevent par2drive from working on any other file.

I think I fixed it for myself by changing line 147 from

to

if [[ -s "$file" && "$date_last_modified_parity" -lt "$date_last_modified_file" ]] ; then

but that uses the [[ ... ]] bashism, which I understand is not acceptable for what your script targets.

I'm sure a portable solution is simple, but I'm not aware of the best method. I didn't want to add an entirely new if statement just for that, so I gave up on trying.

For folders with many files, all the generated parity files tend to clutter up the source folder. It would be great if we could pass an optional folder path for saving all the parity files to. It would have an identical folder structure that mirrors the source path, but would only contain parity files.

Or do you have any other suggestions for preventing source folders from being crowded with parity files?