Mistakes in removing deleted files at remote targets

[allter]

Hello!

I first knew about osync several days ago. I started to use it since v.1.1RC and noticed that my files are not deleted and synced back next syncs. I found where the problem is and fixed it today. I didn't know that you were working on #53 touching the same place until I tried to rebase my work against master. But now I finished it and I'd like to share it. I'll send a pull request when I figure how. :)

[allter]

The pull request is: #55

[deajan]

Since your PR has been merged into 1.2-dev, I've backported the fixes to v1.1-maint branch.
Feel free to test them.

[allter]

Seems like deletion is now working in master. Thank you for reviewing and backporting! I have also one more fix on my other computer which is related to saving of remotely soft-deleted files. Also when I looked into code it seemed that the SOFT_DELETE=no setting was not propagated to the code executed at a remote (i.e. always soft deletion).

[deajan]

Updated both branches with remote soft deletion propagation. Thanks.
Btw, master branch is pretty unstable to use right now, prefer v1.1-maint.
I've merged your PR so you could keep "property" of the commits, but osync.sh is rebuilt from dev/n_osync.sh which has most of your fixes ported, but not the extensive logging part as --verbose already deals with it.
I'm happy if you have other fixes, let me know.

[allter]

I looked at my other computer copy and noticed that you probably already fixed it yourself in master. It was needed to remove 1 in the following line to actually backup files in a root of osync`ed directory.
$COMMAND_SUDO mv -f "$REPLICA_DIR$files" "$REPLICA_DIR$DELETE_DIR"1

I haven't tested v1.1-maint yet.

[deajan]

Yep, found that nasty typo a couple of days ago. Thanks :)