Displaying 20 results from an estimated 300 matches similar to: "Redirect --stats to STDERR."
2004 Sep 03
1
more filelist --stats
The attached diff causes rsync to show how much time it spends
on building and sending its filelist. I'd appreciate if you
could consider this change for inclusion in a future release.
-------------- next part --------------
diff -ru rsync-2.6.3pre1/flist.c rsync-2.6.3pre1+tykhe/flist.c
--- rsync-2.6.3pre1/flist.c 2004-08-12 14:20:07.000000000 -0400
+++ rsync-2.6.3pre1+tykhe/flist.c
2002 May 16
1
[patch] suggestions for -v option
The attached patch makes two changes to the behavior of the -v option:
1) The initial "building file list ... done" and the last two lines
with transfer statistics are moved to verbose level 2, which means
that you have to specify -vv to see them. When I use -v, I only want
to see which files are being updated.
Perhaps the statistics could be controlled by a separate option,
2007 Aug 01
0
[PATCH] prevent negative "time left" values with --progress when file grows
[ see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415648 ]
When a source file grows during transfer, rsync may show negative time
values such as 0:-1:-34. The following patch replaces then negative
times with ??:??:?? in such cases (as IMHO it's not worth the bother of
getting the filesize again etc. in such cases, but showing garbage info
is wrong as well).
Paul Slootman
Index:
2002 Jul 31
1
rsync: omit summary with a single -v
It would be nice if there were a flag which would have rsync behave
like a single -v but which would skip the two line summary info. I do
a lot of cron-based transfers and I want to see what gets transferred
if anything does, but I'd like it to be entirely silent otherwise.
Here is a patch which makes a single -v behave this way. -vv causes it
to include the extra info.
diff -r -X
2006 Dec 10
1
Rsync 2.6.9 Develops Conflict Between --stats, I think --delete-after and Local Filesystem Replication
Hi all,
Well, yeah, that's it, really. :-) Try it. Works consistently, on Doze
and Linux here ...
# rsync -vvrlHSPtiypogD --stats --numeric-ids --delete-after --force --
partial-dir=.partial /tmp/ /var/tmp/
[...show stats...]
unknown message 4:1 [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(307)
[generator=2.6.9]
rsync: connection unexpectedly closed (26
2006 May 13
2
using -v and -q together
seems the behavior of rsync has changed when dealing with output and using
both -v and -q at the same time ... for example:
$ mkdir test1
$ touch test1/foo
$ rsync-2.6.0 -avq test1 test2
$ rm -r test2
$ rsync-2.6.8 -avq test1 test2
test1/
test1/fo
$ rm -r test2
$ rsync-cvs -avq test1 test2
building file list ... test1/
test1/fo
$ rm -r test2
the new output in 2.6.8 comes from the calls to
2004 Jan 13
3
Progress reporting: N more to check
A recent posting here got me thinking about having the --progress
output tell the user about how many files were left to go in the
transfer. I submit the attached patch which outputs an extra suffix
onto the progress line at the end of each file's transfer (so it
only appears once per file, not on every status update). The output
would look like this:
[...]
flist.c
35671 100%
2016 Dec 25
1
System freeze if mount cifs share with option "hard", and samba server is not available
I know "hard" means command will hang if network is broken. But it seems that's not actuate. It's CPU that will hang.
Affected scope:
I tested it against CentOS 5/6/7, it can be reproduced on all the systems. the debug logs below are captured from CentOS 7 (cifs.ko v2.05)
How to reproduce this problem?
1. mount a cifs share with option "hard"
2. stop samba
2008 Jun 09
4
DO NOT REPLY [Bug 5529] New: Use commas in displayed numbers
https://bugzilla.samba.org/show_bug.cgi?id=5529
Summary: Use commas in displayed numbers
Product: rsync
Version: 3.0.2
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: Dave@Yost.com
QAContact:
2008 Feb 16
1
DO NOT REPLY [Bug 5265] New: Daemon logging files not actually received with --only-write-batch
https://bugzilla.samba.org/show_bug.cgi?id=5265
Summary: Daemon logging files not actually received with --only-
write-batch
Product: rsync
Version: 3.0.0
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2003 Apr 08
2
[Patch] Require extra --stats to emit heap statistics
Since the heap statistics were added, I have viewed thousands of rsync
reports (with --verbose and --stats), and not once have I had a need
for them. So for me, they're just noise.
Here is a 3-part patch to v2.5.6 that treats --stats in a similar
fashion to --verbose in that additional --stats will get you more
statistics. For this initial case, there's only one additional level
of
2001 Aug 06
1
merge rsync+ into rsync (was Re: rsync-2.4.7 NEWS file)
> Just curious: what about the rsync+ patch?
Thanks for the reminder.
I've just committed Jos's rsync+ patch onto the
"branch_mbp_rsyncplus_merge" branch. If it works OK and nobody
screams I will move it across onto the main tree tomorrow or
Wednesday.
I see the patch doesn't add documentation about the new options to the
man page, so we should fix that in the future.
2004 Feb 06
4
memory reduction
As those of you who watch CVS will be aware Wayne has been
making progress in reducing memory requirements of rsync.
Much of what he has done has been the product of discussions
between he and myself that started a month ago with John Van
Essen.
Most recently Wayne has changed how the file_struct and its
associated data are allocated, eliminating the string areas.
Most of these changes have been
2009 Oct 30
3
crontab won't work
Hi,
I have a strange problem here. I have two servers, one dedicated
webserver, and a local backup server.
On the webserver I have this :
[root at 12569hpv163154:~] # crontab -l
00 22 * * * /usr/local/bin/sauvegarde-pmbccps.sh
This launches a backup script every day at 22:00, and it works as expected.
Now here's what I have on the local backup server :
[root at grossebertha:~] # crontab
2000 Jul 20
2
Client frequent disconnection + strange logs
Hello,
Although I've been using samba for years at my customers
office, I recently moved one on a HP E60 server running
RedHat 6.2.
The samba version is 2.0.6, untouched from the distribution.
They use a (weird) accounting software built on the top of
FoxPro, requiring a *huge* amount of open files. I accordingly
raised the values for files-nr and inode-nr and the stats seem
ok.
They have
2018 Jun 25
2
Postfix, system notifications and local servers
Hi,
I have CentOS 7 running on half a dozen public servers. For some stuff
like automatic updates using yum-cron, I have Postfix installed with a
relatively basic configuration. This allows me to send important
notifications to my mail address info at microlinux.fr. When there's a
batch of updates, I get one mail per machine, so I can check quickly if
everything went OK without having to
2011 Aug 01
1
[Gluster 3.2.1] Réplication issues on a two bricks volume
Hello,
I have installed GlusterFS one month ago, and replication have many issues :
First of all, our infrastructure, 2 storage array of 8Tb in replication
mode... We have our backups file on this arrays, so 6Tb of datas.
I want replicate datas on the second storrage array, so, i use this command
:
# gluster volume rebalance REP_SVG migrate-data start
And gluster start to replicate, in 2 weeks
2004 Jan 06
2
[patch] making rsync less verbose
Unless you suppress all output with the -q option, rsync will always
print an initial "building/receiving file list ... done" line. In my
opinion, this is a bit superfluous. When I want to see a progress
indication, I can use the --progress option. Another issue is the
3-line transfer speed and speedup factor report at the end. So every
rsync invocation produces at least four lines of
2008 Jul 18
2
Yet another rsync incremental thread
Hello all,
Since the rsync on Panther many things changed in my professional
life. This project is abandoned although it should work. But this you
already know. What's new? On my new job I have several servers to
administrate. Servers that aren't backed up (sic). So, there's why I'm
back to rsync.
The backup plan I would like:
1) Client side: PCs running rsync (or
2003 Jan 27
1
Owner and group
Hi all,
When i use rsync with on the server :
motd file = /etc/rsyncd.motd
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
lock file = /var/run/rsync.lock
[filieres]
path = /home2
comment = Repertoire de sauvegarde des filieres
read only = no
hosts allow = 172.18.1.246 # vador only
dont compress = *.gz *.jpg *.zip *.rpm *.tgz
note : the