In my new bash script, I'm doing what I think is a very simple rsync
command the way I'm used to doing it. I just do a lot of setup and
checking before I get to it.
When I run it, it gets very unhappy with me. It's probably something
very simple.
I need to build the rsync command in a string so
https://bugzilla.samba.org/show_bug.cgi?id=9594
Summary: Error transferring user and non-user xattr using
--fake-super under Linux
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Linux
Status: NEW
It seems to me that the | is interpreted literally. You need to escape it
like this in your command variable: \|
To make the logfile and source/destination paths "space proof" when you
store the command in a variable you add escaped " around the paths like
this: \"/path/to/logfile\".
You should al
On Fri 25 Jan 2013 00:08:52 NZDT +1300, Joe wrote:
> In my new bash script, I'm doing what I think is a very simple rsync
> command the way I'm used to doing it. I just do a lot of setup and
> checking before I get to it.
>
> When I run it, it gets very unhappy with me. It's probably something
I added eval and the backslash. No joy.
What does work, but shouldn't be necessary was using a subshell to force
rsync onto a lower parameter diet:
COMMAND="(rsync ${DRY_RUN} -avushi ${DELETE} --stats --progress
--log-file=${LOGFILE1} ${MOUNT_POINT[0]}/${DIRECTORY[0]}/
${MOUNT_POINT[1]}/${DIRECT
THANK YOU! That method of handling parameters is new to me. I have read
several bash programming books and it wasn't in there.
It does work *way* better than what I was doing.
More replies inline.
If anyone feels this is too off topic for this list, I'd be happy to
continue it a bit off list if
