samba-bugs | 4 Jul 09:57 2015
Picon

[Bug 11383] New: rsync_panic_handler may execute incomplete command

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

            Bug ID: 11383
           Summary: rsync_panic_handler may execute incomplete command
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: brant <at> gurganus.name
        QA Contact: rsync-qa <at> samba.org

The rsync_panic_handler currently defined at line 1490 of main.c writes into a
fixed size cmd_buf at line 1492 a non-controlled value returned ultimately in
get_panic_action() using snprintf at line 1495. The combined values destined
for cmd_buf by way of snprintf may be greater than the 300 character buffer.
This is not checked. Consequently, a command may attempt to execute that was
not intended.

To address this specific issue, if the snprintf function returns a value
greater than or equal to the size of cmd_buf, cmd_buf either needs enlarged or
some informative action should occur. It should not take the current path of
executing an incomplete command. The glibc manual suggests calling asprintf
instead of snprintf to dynamically allocate sufficient space for cmd_buf though
dynamic memory allocation is a possible failure point which may not be the best
for this code path for signal handling.
(Continue reading)

samba-bugs | 4 Jul 06:38 2015
Picon

[Bug 11382] New: elapsed time calculation does not account for time function possibly returning -1

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

            Bug ID: 11382
           Summary: elapsed time calculation does not account for time
                    function possibly returning -1
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: brant <at> gurganus.name
        QA Contact: rsync-qa <at> samba.org

starttime currently initialized on line 1529 of main.c and endtime currently
initialized on line 222 of main.c, both of which are used on line 344 are used
in a manner that does not handle that time(NULL) can return -1.

Out of curiosity, I did try reading through the glibc source code for that
function to find it currently does return -1, and at the glibc level, that's
all that the time function does unless appropriate bridging to a kernel is
implemented. I did not take the time to try looking at other libc
implementations or to see under what conditions the linux kernel might return
-1.

As I only see one usage on line 344, if one of those two values comes back as
-1 for some reason, perhaps that information line should be ommitted or
(Continue reading)

samba-bugs | 2 Jul 20:00 2015
Picon

[Bug 11378] New: Please add a '--line-buffered' option to rsync to make logging/output more friendly with pipes/syslog/CI systems/etc.

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

            Bug ID: 11378
           Summary: Please add a '--line-buffered' option to rsync to make
                    logging/output more friendly with pipes/syslog/CI
                    systems/etc.
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: nneul <at> neulinger.org
        QA Contact: rsync-qa <at> samba.org

Created attachment 11225
  --> https://bugzilla.samba.org/attachment.cgi?id=11225&action=edit
patch to implement --line-buffered option

Behavior change with --line-buffered would be primarily to --progress - which
would output a newline after percentage update instead of just a
carriage-return.

During a normal operation with smaller files you'd never notice the difference,
but with large files (say recurrent sync of ISO images or similar) - you'd get
a MUCH more usable output trace in the build system and logs instead of it all
being merged onto one "line" of output.
(Continue reading)

Dirk van Deun | 30 Jun 10:32 2015
Picon

cut-off time for rsync ?

Hi,

I used to rsync a /home with thousands of home directories every
night, although only a hundred or so would be used on a typical day,
and many of them have not been used for ages.  This became too large a
burden on the poor old destination server, so I switched to a script
that uses "find -ctime -7" on the source to select recently used homes
first, and then rsyncs only those.  (A week being a more than good
enough safety margin in case something goes wrong occasionally.)

Is there a smarter way to do this, using rsync only ?  I would like to
use rsync with a cut-off time, saying "if a file is older than this,
don't even bother checking it on the destination server (and the same
for directories -- but without ending a recursive traversal)".  Now
I am traversing some directories twice on the source server to lighten
the burden on the destination server (first find, then rsync).

Best,

Dirk van Deun
-- 
Ceterum censeo Redmond delendum
--

-- 
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 | 28 Jun 07:25 2015
Picon

[Bug 11369] New: obsoleted autoconf macros

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

            Bug ID: 11369
           Summary: obsoleted autoconf macros
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: trivial
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: brant <at> gurganus.name
        QA Contact: rsync-qa <at> samba.org

There are a few autoconf macros in use deemed obsolete upstream with straight
forward alternatives. The autoscan tool can correct most of them, but there are
two that take a little bit of code analysis.

Most items are replacing AC_TRY_COMPILE with AC_COMPILE_IFELSE.

Of those taking a bit more code analysis, there is the assessment by the
autoconf developers that sufficient time has passed that you can assume the
signal return type. In other words, it's my understanding that instead of
having it return RETSIGTYPE and having autoconf determine the type, it can just
be void and remove the check. The defined token seems to only occur in rsync.c
and main.c.

The second item is AC_C_LONG_DOUBLE which is replaced by AC_TYPE_LONG_DOUBLE
(Continue reading)

john espiro | 26 Jun 03:43 2015
Picon

Sync files-from with delete

I have a local directory that I am trying to sync with a remote directory.  That's fine, but there's a lot of
data that is out of sync so I decided to make a local copy of the difference to then bring to the remote location.

So I ran a dry-run between the two to generate a list of files in listOfFiles.txt

Then I ran rsync from local to localBackup.

rsync -av --files-from=/tmp/listOfFiles.txt /var/MyData/ /USB/Backup/


Now, while this is happening, I am still rsycning between my local and my remote.  So I re-generate the
listOfFiles.txt, which contains less things to copy than before.... I'd like to delete anything in
/USB/Backup that is not in the listOfFiles.txt

TLDR: I want to make a local backup of the differences between local and remote and sync them to a separate
local drive.

Thanks...
--

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

Bob of Donelson Trophy | 25 Jun 14:11 2015
Picon

add rsync -A -X to Backuppc "RsyncArgs" get 'Got fatal error during xfer (fileListReceive failed)'

Backuppc uses rsync (do not know what rsync version but Backuppc is latest version, so assuming 'very' current rsync version is included) and I am trying to add acl and attr file permissions to rsync in "RsyncArgs" and "RsyncRestoreArgs" and have discovered that their addition is not that easy.

Backuppc uses "RsyncArgs" and "RsyncRestoreArgs" to create the rsync 'string' of commands to "backup" files. By adding the "-A" and "-X" to the "RsyncArgs" list. When backups are run the log files contains: "Got fatal error during xfer (fileListReceive failed)". Removing the "-A" and the "-X" allows the backup to proceed without errors. Is there another 'switch' that needs to be added to allow the "-A" and "-X" to function without error? Anyone familiar with including acl and attr file permissions during rsync backup (and restore.)?

 

--

 

Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com "Everyone deserves an award!!"
--

-- 
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 | 17 Jun 14:35 2015
Picon

[Bug 11338] New: Rsync Crash - Segmentation fault

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

            Bug ID: 11338
           Summary: Rsync Crash - Segmentation fault
           Product: rsync
           Version: 3.1.1
          Hardware: x64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: bsc.chauhan <at> gmail.com
        QA Contact: rsync-qa <at> samba.org

Created attachment 11170
  --> https://bugzilla.samba.org/attachment.cgi?id=11170&action=edit
Core file generated at crash

Dear Team,

We are facing a crash in rsync on one of our production servers. We have
updated rsync to the latest version 3.1.1 but still crash is observed. Below
call stack is generated by the crash:
(gdb)
#0  0x0000003ad7e25433 in __gconv_transform_ascii_internal () from
/lib64/libc.so.6
#1  0x0000003ad7e20264 in __gconv () from /lib64/libc.so.6
#2  0x0000003ad7e1f83c in iconv () from /lib64/libc.so.6
#3  0x000000000040d252 in iconvbufs ()
#4  0x0000000000423bce in rwrite ()
#5  0x0000000000423505 in rprintf ()
#6  0x000000000042b911 in whine_about_eof ()
#7  0x000000000042f5e2 in read_buf ()
#8  0x000000000042fde1 in read_int ()
#9  0x000000000043055d in setup_protocol ()
#10 0x000000000041ffb8 in client_run ()
#11 0x00000000004209c6 in main ()

Please let us know if any additional information is needed for debugging.

Regards,
Balveer Singh

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

Guangmu Zhu | 16 Jun 08:38 2015
Picon

Strange problem with rsync and expect

Version: 3.0.6

OS: CentOS 6.6

I met a strange problem when using rsync with expect. I wrote a script backing up using rsync and expect. However when I run the script twice for two different files at same time,  the two files on destination path would be deleted automatically before the files closed. The output of inotify_wait was like:
./ MODIFY .redo02.log.dOlbek
./ DELETE .redo02.log.dOlbek
./ CLOSE_WRITE,CLOSE .redo02.log.dOlbek
I didn't use any --del options and tried --ignore-errors --max-delete=0, but they didn't work. The problem happened only when two processes were running at same time.  Here is my script:
#!/usr/bin/expect

log_user 0

set env(LANG) en_US.UTF-8

set user        "[lindex $argv 0]"
set bwlimit     "[lindex $argv 1]"
set timeout     "[lindex $argv 2]"
set src_path    "[lindex $argv 3]"
set dest_ip     "[lindex $argv 4]"
set dest_path   "[lindex $argv 5]"
set passwd      "[lindex $argv 6]"

spawn rsync -artqz4 -e "ssh -p 22 -o StrictHostKeyChecking=no -l $user" \
            --bwlimit=$bwlimit --timeout=$timeout "$src_path" "$dest_ip:$dest_path"

expect {
    "Connection refused" {exit 1}
    "Name or service not known" {exit 2}
    "Permission denied*" {exit 3}
    "continue connecting" {send "yes\r"; exp_continue}
    "password:" {send "$passwd\r"; exp_continue}
}

exit
May I did something wrong? Thanks in advance.

Guangmu Zhu

--

-- 
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
ray vantassle | 16 Jun 00:27 2015
Picon

rsync very slow with large include/exclude file list

I have a sensor collector system (very low-powered slow ARM cpu), and another system which daily pulls the data files from it for processing.  There are about 1000 new files each day.  As part of the processing it decides that certain of the files are of no interest, and adds them to an exclude file, which is used in future rsyncs.  No files are ever deleted from the source system, just the receiver system.  All done in cron jobs at night.

After about 18 months, there are about 350,000 files and the exclude list has about 72,000 filenames.  I recently ran the pulling script manually and thought the system must have died.
Rsync took almost 3 hours.  Trying to narrow down the problem, I removed the "--exclude-file=" option from the rsync command -- and it took only 16 minutes -- including the time to transfer the 72,000 files that are of no interest.
 (con't)

--

-- 
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
Indu Thakur | 10 Jun 04:23 2015
Picon

Rsync and NFS ver 4 ACLs

Hi
 I am trying to rsync over data from one NFS 4 vol to another on a different NetApp. We have ZFS style ACLs on the source.
I used the -A option but it fails to copy ACLs. The OS is Solaris 10.

Is this supported
--

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