Re: rsync through ssh - i get an error

2006-09-12 Thread rsync-mail-gateway



	

	hello,
1) ssh is the default protocol of rsync since 2.6.0, so if you are using a new version you should not have to worry about it.

2) check that you used the command as following:
rsync  -e ssh @:~/
that should do the trick (worked for me)
	


 m2f 

Sent using Mail2Forum (http://www.mail2forum.com). 

Read this topic online here:
http://forums.nasbackup.com/viewtopic.php?p=3837#3837

 m2f 
	

-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

cygwin rsync performance and bandwidth between two w2003 servers

2006-09-12 Thread Ulrich Jung
I have two Windows 2003 Standard Edition Server with 2x 3,0 GHz P4 and 4 
GB RAM.
On each server rsync runs as cygwin daemon (rsync version 2.6.6; 
protocol version 29).


The two servers are connected through a 2 MBit VPN link.
When I sync a single large file or a whole directory, rsync only uses 
50% of the available bandwidth.
When I do the same between windows and linux server, rsync takes the 
whole bandwidth.


Both windows and linux server have the same settings in rsyncd.conf.

Would be great if there is someone with any ideas how to solve this problem!

Thanks,
--
Sattler Media Press GmbH
Ulrich Jung
Kurt-Sattler-Straße 9 - 38315 Hornburg
Fon +49 5334 29 152
Fax +49 5334 29 344
mailto:[EMAIL PROTECTED]
http://wfw.de

--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: rsync through ssh - i get an error

2006-09-12 Thread rsync-mail-gateway



	

	i got the reply through mailing list and saw that not all came through...
so again:
1) ssh is the default protocol of rsync since 2.6.0, so if you are using a new version you should not have to worry about it.

2) check that you used the command as following:
rsync flags -e ssh local_dir [EMAIL PROTECTED]:~rsync_user/
that should do the trick (worked for me)
	


 m2f 

Sent using Mail2Forum (http://www.mail2forum.com). 

Read this topic online here:
http://forums.nasbackup.com/viewtopic.php?p=3838#3838

 m2f 
	

-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: rsyncing as root when root login is disabled?

2006-09-12 Thread Linus Hicks

Joe Ruby wrote:

I'm trying to do a simple rsync:

rsync -av [EMAIL PROTECTED]:/backup .

But a number of files in /backup are readable only by
root, and hence rsync gives these errors:

sync: send_files failed to open
/backup/etc/mail/virtusertable.db: Permission denied
(13)

Since root login is disabled, I can't simple do
'[EMAIL PROTECTED]'. I searched a bit and saw this:

rsync -av --rsync-path='sudo path'
[EMAIL PROTECTED]:/backup .

I tried it -- rsync asks for my password, but then
doesn't output anything after many minutes (after
which I kill it).

So, how can I rsync files from my remote server so all
the files are readable and the existing permissions
get preserved (e.g. not having to do 'chmod -R a+r
/backup'.


Perhaps what you have shown in your email is incomplete, but based on what you 
have written, you have replaced the remote rsync with sudo. Instead you need to 
invoke rsync using sudo by giving a command to sudo. You might be able to do 
that using the --rsync-path argument like --rsync-path='sudo path rsync', I 
have not tried it. Or you could write a wrapper. Google rsync wrapper.


--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: Exclude usage question

2006-09-12 Thread Paul Slootman
On Tue 12 Sep 2006, Heise, Robert wrote:

 Here is the verbose output while using --dry-run
 
  Processing
 ral-bea-01-l:/usr/bin/rsync--archive--compress--delete--dry-run
 --group--perms--stats--times--rsh=/usr/bin/ssh -o
 StrictHostKeyChecking=no--rsync-path=/usr/bin/rsync--verbose--excl
 ude='/freetds-0.61.2/*.sh'/usr/SD/stow/[EMAIL PROTECTED]:/usr/SD/sto
 w/

Where are all these quotes coming from? This makes it hard to read what
is actually being executed.

However, it looks like you're on system ral-bea-01-l and you're rsyncing
to ral-bea-01-l (i.e. the same system) ?!

 Status = $VAR1 = [building file list ... done\n,rsync[26414]
 (sender) heap statistics:\n,  arena: 135168   (bytes from
 sbrk)\n,  ordblks:5   (chunks not in use)\n,  smblks:
 1\n,  hblks:  0   (chunks from mmap)\n,  hblkhd:
 0   (bytes from mmap)\n,  usmblks:0\n,  fsmblks:
 40\n,  uordblks:   47248   (bytes used)\n,  fordblks:
 87920
 (bytes free)\n,  keepcost:   71400   (bytes in releasable
 chunk)\n,\n,Number of files: 57\n,Number of files transferred:
 0\n,Total file
 size: 10384954 bytes\n,Total transferred file size: 0
 bytes\n,Literal data: 0 bytes\n,Matched data: 0 bytes\n,File list
 size: 1054\n,Total bytes written: 1096\n,Total bytes read:
 20\n,\n,wrote 1096 bytes  read 20 bytes  744.00 bytes/sec\n,total
 size is 10384954  speedup is 9305.51\n];

Again, I don't know what you're doing that sprinkles all these quotes
everywhere, it really obfuscates stuff.

 I don't see anything glaringly obvious.

It looks like you need to double up on the verbose flag; use -vv


Paul Slootman
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Questions and comments regarding --remove-sent-files (Was: New delete option?)

2006-09-12 Thread Evan Harris


I've looked back through my mailing list archives, and seen a few messages 
touching on the same things I wanted to mention, but I figured it might be 
better to recap, since most of them were sent more than a year ago.


I have recently started using the --remove-sent-files option, and have 
noticed a couple of warts.  I'm using it to transfer (move really) gigabyte 
and larger sized files over a fairly slow connection (--bwlimit=10) and with 
keeping of partial files (--partial) to minimize transfer time in the event 
of connection problems.


Because the individual files may take a day or more each to transfer, rsync 
interruptions are not uncommon, and I've had several instances where the 
first run of a transfer aborted in the middle of the non-first file. 
Although rsync had successfully sent one or more files before losing the 
connection or being aborted, it doesn't appear to delete the files until a 
successful end of the whole rsync.  A later restart of the rsync sees that 
some of the files already exist on the destination and need no update, and 
those files get left on the sending side when they shouldn't.


So, I agree with the parent message that either --remove-sent-files should 
delete the files immediately after they are successfully sent, or a new 
option should be added (--move maybe?) that does it that way.


I saw a followup mailing list message from Wayne that suggested adding the 
-I option to cause the desired behavior, and that looks like it would be a 
good workaround.  Maybe all that is needed is to make a new --move option be 
an alias for --remove-sent-files and --ignore-times.  Would this be a fairly 
simple enhancement?


The other issue I wanted to touch on was also mentioned on the mailing list, 
and was how to guard against the possibility that files on the sending side 
might have been modified during the transfer (which for me sometimes takes a 
day or more), and for rsync to realize this and avoid deleting the file and 
losing those changes.  I know this one is a more difficult problem, but I 
just wanted to see if there might be an easy solution.


Wayne, thanks for all your work!

Evan


On Fri, 22 Apr 2005, Wayne Davison wrote:


[It appears I missed this message back in February -- ouch.]

On Sat, Feb 19, 2005 at 08:53:32PM -0500, Andrew Gideon wrote:

FWIW: In the manner I can envision using this, it makes more sense to
delete the source as long as the destination file is valid, whether
that file moved during this execution or not.  This provides a mv
function that's safe against a failure.


That is an interesting point.  The current option allows you to have
identical files that didn't get transferred, and thus don't get removed,
but that does mean that if the transfer gets interrupted it might do the
wrong thing with a file.

I'll contemplate what to do going forward since the --remove-sent-files
option was already released.  Perhaps a --remove-source-files option
should be added that works as you suggested.

..wayne..
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: Exclude usage question

2006-09-12 Thread Wayne Davison
On Tue, Sep 12, 2006 at 08:41:12AM -0400, Heise, Robert wrote:
 Here is the verbose output while using --dry-run

I don't see anywhere in that (extraordinarily hard to read) output where
it wanted to copy any excluded files.

..wayne..
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html