rsync - May 2008 - Ignore Owner and group at destination

Hi All,

We are using rsync version 2.6.3  protocol version 28.

Is there a way we could transfer files and force rsync not to look for the
same user:group as host on the destination?


Thanks in Advance
-- 
View this message in context:
http://www.nabble.com/Ignore-Owner-and-group-at-destination-tp17279218p17279218.html
Sent from the Samba - rsync mailing list archive at Nabble.com.
-------------- next part --------------
HTML attachment scrubbed and removed

On Fri, 2008-05-16 at 09:43 -0700, Meeaz wrote:
> Is there a way we could transfer files and force rsync not to look for
> the same user:group as host on the destination?
If you mean you want destination files to take on the user/group of the
receiving rsync process instead of the source user/group, then simply
omit the -og options, or subtract them from -a by passing --no-o --no-g
after the -a.

Matt

Hi,
I am using ssh for file transfer. Passphrase-less exchange has been set up
between 2 different UNIX users (i.e at host and remote). Once I give the
options that you advised, it gives a syntax error as below:-

rsync -arv --no-o --no-g --files-from=./ff /app/domains/abcref
rxplx005:/var/log/Test_log/TEST
rsync: --no-o: unknown option
rsync error: syntax or usage error (code 1) at main.c(1084)

Pls advise





Matt McCutchen-7 wrote:
> 
> On Fri, 2008-05-16 at 09:43 -0700, Meeaz wrote:
>> Is there a way we could transfer files and force rsync not to look for
>> the same user:group as host on the destination?
> 
> If you mean you want destination files to take on the user/group of the
> receiving rsync process instead of the source user/group, then simply
> omit the -og options, or subtract them from -a by passing --no-o --no-g
> after the -a.
> 
> Matt
> 
> -- 
> Please use reply-all for most replies to avoid omitting the mailing list.
> To unsubscribe or change options:
> https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
> 
> 
-- 
View this message in context:
http://www.nabble.com/Ignore-Owner-and-group-at-destination-tp17279218p17279894.html
Sent from the Samba - rsync mailing list archive at Nabble.com.
-------------- next part --------------
HTML attachment scrubbed and removed

At 2008-05-16 19:15+0200 Meeaz wrote:
> Once I give the options that you advised, it gives a syntax error  
> as below:-
> rsync -arv --no-o --no-g --files-from=./ff /app/domains/abcref
> rxplx005:/var/log/Test_log/TEST rsync: --no-o: unknown option rsync  
> error:
> syntax or usage error (code 1) at main.c(1084) Pls advise
Have you looked at the man pages (man rsync)? You are using version  
2.6.3,
and the manual will tell you that the --no-o and --no-g options are not
available (they were added at a later version).

The manual will also tell you that the -a option is equivalent to - 
rlptgoD .

So you should try the other option that Matt has already suggested:

At 2008-05-16 18:50+0200 Matt McCutchen wrote:
> If you mean you want destination files to take on the user/group of  
> the
> receiving rsync process instead of the source user/group, then simply
> omit the -og options
So instead of subtracting the owner/group options from -a by using -a
--no-o --no-g , you could just leave out the -o and -g options and  
use -rlptD
(instead of -rlptgoD ). (This also means the -r in the -arv you  
listed is not
necessary because it is already included in -a .)

So try: rsync -rlptDv --files-from=...

Since version 2.6.3 is already quite old, you could consider updating  
rsync
(on both machines) to a newer version (currently 3.0.2), if you can  
do that.
This will let you use --no-o and --no-g , but, more importantly, give  
you
several other advantages such as improved speed.

-Moritz

On Fri, 2008-05-16 at 20:01 +0200, hh.eu@gmx.de wrote:
> Have you looked at the man pages (man rsync)? You are using version  
> 2.6.3,
> and the manual will tell you that the --no-o and --no-g options are not
> available (they were added at a later version).
Moritz is right.  I forgot that the --no-o and --no-g options were not
added until 2.6.7 (see OLDNEWS).  Sorry.

Matt