headers
samba-bugs | 1 Jun 2011 09:58
Picon
Favicon

[Bug 6183] rsync error file too large (27)

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

--- Comment #5 from Dal <dtamana2 <at> bloomberg.net> 2011-06-01 07:58:01 UTC ---
The issue happens intermittently. Most of the time large files are sync'd fine.
I have run rsync on the failed file several times now and it hasn't failed. Is
there any debugging I can put in place ?

----- Original Message -----
From: samba-bugs <at> samba.org
To: rsync-qa <at> samba.org
At:  5/28  6:14:11

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

Wayne Davison <wayned <at> samba.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEEDINFO

--- Comment #4 from Wayne Davison <wayned <at> samba.org> 2011-05-28 05:13:33 UTC
---
As mentioned, this is an issue with how rsync was compiled and/or linked.  If
it is compiled with large-file support in the OS libraries, then it supports
large files.  If the libraries don't support large files, or it was not
compiled knowing that it should support large files, then large files aren't
supported.

So, someone needs to figure out what AIX requires for proper compilation (e.g.
what support libraries are not installed, what options are not used, or
(Continue reading)

Permalink | Reply | 0 comments |
headers
samba-bugs | 1 Jun 2011 12:06
Picon
Favicon

[Bug 8198] New: rsync does not set TZ variable after chroot(), which confuses logging timestamps

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

           Summary: rsync does not set TZ variable after chroot(), which
                    confuses logging timestamps
           Product: rsync
           Version: 3.1.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
        AssignedTo: wayned <at> samba.org
        ReportedBy: jkaluza <at> redhat.com
         QAContact: rsync-qa <at> samba.org

Hi,
after chroot(), "current" timezone is changed in chrooted process which leads
to the following output in logs:

May 29 20:00:35 nec-em12 rsyncd[9770]: connect from localhost.localdomain
(127.0.0.1) 
May 29 20:00:35 nec-em12 rsyncd[9770]: rsync to my_data/ from
localhost.localdomain (127.0.0.1) 
May 30 00:00:35 nec-em12 rsyncd[9770]: receiving file list 
May 30 00:00:35 nec-em12 rsyncd[9770]: client/ 
May 30 00:00:35 nec-em12 rsyncd[9770]: client/data/

Proper time is 20:00:35.
(Continue reading)

Permalink | Reply | 6 comments |
headers
samba-bugs | 1 Jun 2011 12:07
Picon
Favicon

[Bug 8198] rsync does not set TZ variable after chroot(), which confuses logging timestamps

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

--- Comment #1 from Jan Kaluza <jkaluza <at> redhat.com> 2011-06-01 10:07:01 UTC ---
Created attachment 6508
  --> https://bugzilla.samba.org/attachment.cgi?id=6508
patch

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- 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
Permalink | Reply | 0 comments |
headers
Michael Tokarev | 1 Jun 2011 12:15
Picon

Re: [Bug 8198] New: rsync does not set TZ variable after chroot(), which confuses logging timestamps

01.06.2011 14:06, samba-bugs <at> samba.org пишет:
> https://bugzilla.samba.org/show_bug.cgi?id=8198
> 
>            Summary: rsync does not set TZ variable after chroot(), which
>                     confuses logging timestamps
>            Product: rsync
>            Version: 3.1.0
>           Platform: All
>         OS/Version: All
>             Status: NEW
>           Severity: normal
>           Priority: P5
>          Component: core
>         AssignedTo: wayned <at> samba.org
>         ReportedBy: jkaluza <at> redhat.com
>          QAContact: rsync-qa <at> samba.org
> 
> 
> Hi,
> after chroot(), "current" timezone is changed in chrooted process which leads
> to the following output in logs:

> Attached patch fixes this issue by caching current timezone and setting TZ
> variable after chroot() call.

tzset() call before chroot should be enough for that --
that's what has always been done in chroot programs
exactly for this purpose (tzset was broken in glibc
at least once, but that's details).
(Continue reading)

Permalink | Reply | 0 comments |
headers
samba-bugs | 1 Jun 2011 17:53
Picon
Favicon

[Bug 8201] New: rsync 3.0.8 destroys SELinux security context of symbolic links

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

           Summary: rsync 3.0.8 destroys SELinux security context of
                    symbolic links
           Product: rsync
           Version: 3.0.8
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
        AssignedTo: wayned <at> samba.org
        ReportedBy: martin.wilck <at> ts.fujitsu.com
         QAContact: rsync-qa <at> samba.org

Description of problem:
P2V conversion of a F14 installation: used rsync -aHAXx to duplicate file
systems from physical to virtual host.

Version-Release number of selected component (if applicable):
rsync-3.0.8-1.fc14.x86_64

How reproducible:
always

Steps to Reproduce:
Physical-2-Virtual conversion of a F14 installation: used rsync -aHAXx to
duplicate file systems from physical to virtual host.
(Continue reading)

Permalink | Reply | 12 comments |
headers
samba-bugs | 1 Jun 2011 19:53
Picon
Favicon

[Bug 8201] rsync 3.0.8 destroys SELinux security context of symbolic links

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

Frederick Grose <fgrose <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fgrose <at> gmail.com

--- Comment #1 from Frederick Grose <fgrose <at> gmail.com> 2011-06-01 17:53:01 UTC ---
confirmed
http://lists.samba.org/archive/rsync/2011-April/026263.html

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- 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
Permalink | Reply | 0 comments |
headers
Brian K. White | 1 Jun 2011 20:57
Favicon
Gravatar

Re: [Bug 8188] Mechanism for taking an rsync server down for maintenance

I like the built-in idea as I don't happen to use rsync via inetd/xinetd 
or any other on-demand starter.

It's not an actual problem for me, today, but that's no excuse to avoid 
doing the right thing once you recognize it.

-- 
bkw

On 5/31/2011 1:15 AM, samba-bugs <at> samba.org wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=8188
>
> --- Comment #1 from Wayne Davison<wayned <at> samba.org>  2011-05-31 05:15:51 UTC ---
> You could just setup something to echo a one-line message on the socket and
> disconnect.  If you're using xinetd, tweak the program to be anything that
> outputs a message to stdout.  To replace an rsync daemon, you may want to code
> up a C program or use a simple perl script, like this (and run it instead of
> the daemon):
>
> #!/usr/bin/perl
> use strict;
> use warnings;
> use Socket;
>
> my $PORT = 873;
>
> local *S;
> socket(S, PF_INET, SOCK_STREAM , getprotobyname('tcp'))
>      or die "couldn't open socket: $!\n";
> setsockopt(S, SOL_SOCKET, SO_REUSEADDR, 1);
(Continue reading)

Permalink | Reply | 7 comments |
headers
Matt McCutchen | 1 Jun 2011 21:26

Re: [Bug 8188] Mechanism for taking an rsync server down for maintenance

On Wed, 2011-06-01 at 14:57 -0400, Brian K. White wrote:
> I like the built-in idea as I don't happen to use rsync via inetd/xinetd 
> or any other on-demand starter.
> 
> It's not an actual problem for me, today, but that's no excuse to avoid 
> doing the right thing once you recognize it.

And "the right thing" for upstream rsync is in Wayne's sole discretion.
In my view, the perl script is a fine solution and what convenience
there may be in a built-in option does not merit the effort of
maintaining the feature as part of rsync.

-- 
Matt

--

-- 
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
Permalink | Reply | 6 comments |
headers
Brian K. White | 1 Jun 2011 23:08
Favicon
Gravatar

Re: [Bug 8188] Mechanism for taking an rsync server down for maintenance

On 6/1/2011 3:26 PM, Matt McCutchen wrote:
> On Wed, 2011-06-01 at 14:57 -0400, Brian K. White wrote:
>> I like the built-in idea as I don't happen to use rsync via inetd/xinetd
>> or any other on-demand starter.
>>
>> It's not an actual problem for me, today, but that's no excuse to avoid
>> doing the right thing once you recognize it.
>
> And "the right thing" for upstream rsync is in Wayne's sole discretion.
> In my view, the perl script is a fine solution and what convenience
> there may be in a built-in option does not merit the effort of
> maintaining the feature as part of rsync.
>

That is a work-around, not a solution. It's great in that, if you can 
meet it's requirements and live with it's deficiencies, it's something 
you can usually do right now without needing anyone else to fix or 
enhance anything. It's also great in that, probably most people _can_ 
meet the requirements and live with the deficiencies since they are not 
that much.

The work-around requires using (x)inetd, and there are many and various 
reasons, from mere admin flexibility, to performance, to security, for 
wanting to avoid all use of any inetd, and why rsync and many other 
servers offer the ability to handle their sessions themselves.

If the service aims to be usable stand-alone, which rsync clearly does, 
then imo this is just part of that. A nicity perhaps, not critical, but 
trivial to implement and maintain in comparison with things like 
child/session management which are definitely in there solely to support
(Continue reading)

Permalink | Reply | 5 comments |
headers
samba-bugs | 2 Jun 2011 06:34
Picon
Favicon

[Bug 8188] Mechanism for taking an rsync server down for maintenance

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

--- Comment #2 from Andrew Pollock <andrew-samba-bugzilla <at> andrew.net.au> 2011-06-02 04:34:54 UTC ---
Created attachment 6513
  --> https://bugzilla.samba.org/attachment.cgi?id=6513
Proof of concept patch

This is purely a proof of concept patch and not production-grade.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- 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
Permalink | Reply | 0 comments |

Gmane