I've been reading through the man pages for rsync, yet I can't seem to find a way to provide
progress indication and/or current download speed for total and/or individual files...
Can this be done with rsync? Is it an implemented feature.
I thought -v or -vv would do the trick, but it doesn't...
On Mon 06 Dec 2004, Payal Rathod wrote:
This is the first time I have setup rsync.conf like,
[...]
Then from 192.168.10.10, I tried,
rsync -avz -e ssh [EMAIL PROTECTED]:/var/qmail/control/* .
and it worked. So far so good. But then again it worked from 192.168.10.11
Rsyncd.conf is only used
On Tue 07 Dec 2004, Dag Rune Sneeggen wrote:
I've been reading through the man pages for rsync, yet I can't seem to find
a way to provide progress indication and/or current download speed for
total and/or individual files...
How about --progress?
Paul Slootman
--
To unsubscribe or change
Hi,
This is the first time I have setup rsync.conf like,
max connections = 20
syslog facility = local3
read only = true
hosts allow = 192.168.10.10
[qmail-control]
comment = qmail-control
path = /var/qmail/control
read only = yes
list = yes
uid
On Tue, Dec 07, 2004 at 10:06:26AM +0100, Paul Slootman wrote:
You connect to the rsync daemon by using a command line like:
rsync -avz 192.168.10.1::qmail-control .
Of course, you will have to have started the daemon on 192.168.10.1
I am not able to get it running properly.
# ps aux|grep
--progress will show individuals.
There is no tracking of total progress,
nor any programmatically efficient way of providing such. If you
were really concerned, you could --dry-run first and sort of keep track
of where you were in the list during the actual run.
Tim Conway
Unix System
xinetd is the daemon. It will
spawn rsync processes as connections come to 872 (assuming that's the port
you associated with whatever you named that service). This is assuming,
of course, that xinetd has read the configuration since you made the change,
either by HUP, xinetd bounce, or system
On Mon, Dec 06, 2004 at 09:38:14AM -0800, Chuck Wolber wrote:
inflate (token) returned -5
You should be able to avoid this error by turning off the --compress
option. To figure out why it is occurring would require someone to
debug a failure case. If you can narrow it down to a particular set
Greetings and salutations, rsync users. I have a problem. I'm hoping that
someone out there could perhaps provide a hand.
I've been trying to transfer large amounts of data (lots of data, lots of
files) via rsync over an encrypted TCP tunnel, but I seem to be continually
getting hangs in the
