Clifford Banes

And for what it's worth, putting just sh or bash in that field doesn't throw an error, but neither does it have any effect on expanding variables. I feel like I should mention, if it isn't already very obvious, that I'm new to Linux and not a programmer. I'm coming from Windows, and my goal is to set up Linux in such a way that I can deal with it with the minimum possible command-line work in the future. I'm starting to feel like I was spoiled by SyncBack, which presents a very robust set of capabilities...

Thank you for the quick response, Piero! Can this prepending be done in the Grsync app, or does it need to be through the command line? I tried putting sh -c in the "Extra options > Execute this command before rsync" field, and I got this error: ** Launching BEFORE command: sh -c Error launching command! I also tried bash -c, to the same effect. If it needs to be through the command line, then it's redundant and I'm back to square one in that regard.

I'm trying to use Grsync on Linux Mint Debian Edition 7 to backup/sync between several drives. I've encountered a major roadblock in the form of environment variables; I want to be able to use the same sessions for multiple users and locations, but when I put those variables in Source and Destination paths (e.g., "/home/$USER/" or "home/%USER%/"), Grsync gives me errors like "change_dir "/home/$USER" failed: No such file or directory". (For the record, I'm using $USER for this example because it's...