samba-bugs | 1 Sep 17:56 2015
Picon

[Bug 11481] New: --ignore-errors must be a separate option

https://bugzilla.samba.org/show_bug.cgi?id=11481

            Bug ID: 11481
           Summary: --ignore-errors  must be a separate option
           Product: rsync
           Version: 3.1.2
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: muralidharn2003 <at> yahoo.co.in
        QA Contact: rsync-qa <at> samba.org

--ignore-errors must be a separate option since we can use this option even
when --delete is not specified. Used to ignore various errors. Man page has to
be updated to indicate the same.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

--

-- 
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

(Continue reading)

L. A. Walsh | 1 Sep 10:47 2015

Switch to AIO instead of IO/parallize fs scan...

I was thinking about [Bug 3099]... in that while it's easy to get a 2-3x 
speed
for the average app using parallel scans, the upper and lower bounds on that
speed increase could be <1x in a worst case (very unlikely, but with 
primitive
or constrained (in a container or VM) HW, the chances are raised.

Better, with less std. deviation, I believe, might be to move I/O calls 
to all being
AIO -- It seems that would allow them to be completed at the OS's 
discretion
which, in the idea case would be minimal wasted disk-head.  The 
advantage in
AIO, being that OS can coalesce calls more at its leisure, vs. an upper 
level
app algorithm, that might divide up the work fairly, but not know how much
each underlying request costs in terms of wasted head movement.

Is that already in there, in the works, or do you think it would avoid worst
case division of file scanning based on FS-hierarchical structure vs. 
underlying
disk layout?

--

-- 
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

samba-bugs | 30 Aug 23:35 2015
Picon

[Bug 11474] New: Retry delay for lost connection

https://bugzilla.samba.org/show_bug.cgi?id=11474

            Bug ID: 11474
           Summary: Retry delay for lost connection
           Product: rsync
           Version: 3.1.2
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: samba <at> haravikk.com
        QA Contact: rsync-qa <at> samba.org

Currently when a connection is lost, rsync will abort the rest of the transfer,
forcing it to be started from the beginning once again. Since rsync is pretty
much designed around transferring only changed files this isn't usually a big
deal, however with very large (in size or quantity) transfers, or transfers
over slower connections, resuming can be a very slow process; a backup that
might take four hours and gets interrupted, could take two or three hours to
actually resume as it runs through previously transferred files necessarily.

What I would like to propose is that a new option be added that will cause
rsync to wait instead of failing when a connection is lost, and instead try to
re-establish the connection at periodic intervals until that time limit is
reached. If the connection is re-established then the transfer will resume
where it left off, thus skipping any previous files.

(Continue reading)

Grzegorz Borowiak | 22 Aug 00:12 2015
Picon

I would like to add features to rsync: tags and saving local modifications

Hello!

My name is Grzegorz Borowiak and I am a programmer.
I work for a company which uses rsync internally, to distribute our
continuously changing development environment.
The environment weighs several gigabytes and consists of over 100000
files, most of them binary, so VCS-es like git and subversion are not
an option, but rsync performs very efficiently.

However, I would like to add some features, which we need, and they
are generic enough to be useful for someone else, so I would like to
add them in a way which would allow them to be contributed.

Feature 1: tags

Our environment is large, but modularised, i.e. every file in it
belongs to some module. Not every user needs not every module, so the
download by rsync is parametrised by checking or unchecking the
modules. However, currently this is implemented as filters, which
include or exclude some files by their path or, in some cases, by
substrings in file names.

To make modularisation more straightforward, and not limited by
necessity of differentiation between files by path or name, I propose
to introduce concept of tags. Every file could be tagged with some
string as an xattr (for example, user.rsync.tag=TAG), and in
downloading rsync invocation you could specify a parameter
--tag=TAG. This option could be specified more than once. rsync,
once invoked in such way, would affect:
- all files without tag at all
(Continue reading)

samba-bugs | 18 Aug 18:36 2015
Picon

[Bug 11456] New: Allow configuration of MAX_GID_LIST

https://bugzilla.samba.org/show_bug.cgi?id=11456

            Bug ID: 11456
           Summary: Allow configuration of MAX_GID_LIST
           Product: rsync
           Version: 3.1.2
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: jheiss <at> aput.net
        QA Contact: rsync-qa <at> samba.org

MAX_GID_LIST is a constant in clientserver.c with a value of 32.  I have users
who are in more than 32 groups, resulting in
want_all_groups->getallgroups->getgrouplist failing.  I'll just change the
constant in my local build for now, but a way to configure the limit would be
nice.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

--

-- 
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
(Continue reading)

@lbutlr | 17 Aug 08:13 2015

Error with paths with ()'s

I was trying to process a bunch of folders to sync them to another drive and ran across an error I haven’t
seen before. Normally I do this sync via a mounted file system, but this time I tried to do it over ssh:

find . -type f -atime -1 -exec rsync -aP {} 10.0.0.11:/Volumes/Drive5/{} \;
bash: -c: line 0: syntax error near unexpected token `('
bash: -c: line 0: `rsync --server -logDtpre.iLsfx --log-format=X --partial . /Volumes/Drive5/./Taxes
(2012)/W2 (2012).pdf'
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.1]

If I mount Drive5 and run the same command, it works fine.

Put "/Volumes/Drive5/{}” in quotes doesn’t help.

Ideas?

-- 
Why can't you be in a good mood? How hard is it to decide to be in a
good mood and be in a good mood once in a while?"

--

-- 
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

leonv12 | 14 Aug 04:54 2015

Rsync verbose flags=404 meaning

I have a situation where rsync keeps deleting some entire directories and
recopying all the data in those folders.  I have tried all the usual stuff
such as modify window to no avail.  I have set the verbosity to -vvv.  The
output shows the following example

[Receiver] i=130 3 cygdrive/d/2014-01-27 3033 E. 1st/ mode=040700 len=4096
gid=(1001) flags=404
[Receiver] i=131 4 cygdrive/d/2014-01-27 3033 E. 1st/100 Fillmore.JPG
mode=0100700 len=3605635 gid=(1001) flags=400

I am trying to figure out the meaning of the mode, len, gid, and *especially
flags*.  Where can I find the meaning of these?

Thanks in advance,
Leon

--
View this message in context: http://samba.2283325.n4.nabble.com/Rsync-verbose-flags-404-meaning-tp4689806.html
Sent from the Samba - rsync mailing list archive at Nabble.com.

--

-- 
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

Wayne Davison | 9 Aug 00:12 2015
Picon

Rsync 3.1.2pre1 released

I have just made rsync 3.1.2pre1 available for testing.  This is a bug-fix release that fixes a few important issues and makes a some minor improvements.
 
Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports.

To see a summary of the changes since 3.1.1, visit this link:
 

You can download the source tar file and its signature from here:


The patches directory is now in a separate tar file (for those that want one or more of the patches):


See the rsync website for other download methods, including diffs, etc.:


..wayne..

--

-- 
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
Fyodorov "Bga" Alexander | 1 Aug 13:21 2015
Picon

unnecessary /proc requirement in 3.1.1

Hi. Thanks for good program.

I'm quite paranoid guy and dont beleave when some program offer me "use chroot = yes". Instead i jail program manually.
I was at 3.0.9 and all was fine. Manual chroot only requires files dir, config and personal tmp. 3.1.1 now also want whole /proc only for /proc/self/fd/X instead just fd number. Whole /proc is  serious security risk for me. Why?

starce log
lstat64("tt", {st_mode=S_IFDIR|S_ISGID|0755, st_size=4096, ...}) = 0
fstatat64(AT_FDCWD, "tt", {st_mode=S_IFDIR|S_ISGID|0755, st_size=4096, ...}, AT
_SYMLINK_NOFOLLOW) = 0
openat(AT_FDCWD, "tt", O_RDONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC|O_PATH) = 2
fstatat64(AT_FDCWD, "/proc/self/fd/2", 0x5bafe7f0, 0) = -1 ENOENT (No such file
 or directory)
close(2)                                = 0
getpid()                                = 1395
sendto(0, "<28>Aug  1 00:35:51 rsyncd[1395]"..., 117, 0, NULL, 0) = -1 ENOTCONN
 (Socket not connected)
connect(0, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 12) = -1 ENOENT (No such
file or directory)
select(4, [1], [3], [1], {60, 0})       = 1 (out [3], left {59, 999915})
write(3, "V\0\0\10rsync: failed to set permiss"..., 361) = 361



--
Alexander.
--

-- 
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
samba-bugs | 1 Aug 04:28 2015
Picon

[Bug 11423] New: rsync 3.1.x is creating empty backup directories

https://bugzilla.samba.org/show_bug.cgi?id=11423

            Bug ID: 11423
           Summary: rsync 3.1.x is creating empty backup directories
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: major
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: adsh <at> univ.kiev.ua
        QA Contact: rsync-qa <at> samba.org

Running the command

$ rsync -a --delete --backup --backup-dir=../old source/ dest/

with version 3.1.0 gives the output

Created backup_dir ../old/

even when no files are copied to the backup directory. I usually add the
current time to the backup directory name, which means I end up with many empty
directories. With version 3.0.9 of rsync, a backup directory was only created
if needed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

--

-- 
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

samba-bugs | 31 Jul 22:16 2015
Picon

[Bug 11422] New: Feature request: add support for Linux libcap[-ng]

https://bugzilla.samba.org/show_bug.cgi?id=11422

            Bug ID: 11422
           Summary: Feature request: add support for Linux libcap[-ng]
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: rsync <at> sanitarium.net
        QA Contact: rsync-qa <at> samba.org

Linux has added a concept called file capabilities.  This allows certain
binaries to perform specific privileged functions without requiring SUID root.

Example:
# getcap /bin/ping
/bin/ping = cap_net_raw+ep

Rsync should be able to (optionally of course) copy these attributes as it can
copy xattrs and ACLs.  They should also be storable via --fake-super on
non-Linux systems.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

--

-- 
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


Gmane