Re: If ssh port is not 22, how does rsync specify this in command line?
cyclops When use rsync with ssh mode, how to specify the port ssh use with command line? I use a command that includes this: rsync ... -e 'ssh -p 1234' ... (replace the dots with your own rsync options) Hope that helps, -Cam -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Strange behaviour rsync pull from sun to ppc linux, Integer overflow - attempted 64 bit offset
Wayne I made a patch from CVS with your changes and repeated the test, which passed. Thanks again for the first-class support :) -Cam -- [EMAIL PROTECTED] -- -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Strange behaviour rsync pull from sun to ppc linux, Integer overflow - attempted 64 bit offset
Hi,
I am running rsync on an embedded linux (ppc) like this:
rsync -avvv sun::file-system/ /rsyncexperiment
Where sun is a solaris machine that has rsync:
rsync version 2.5.7 protocol version 26
Copyright (C) 1996-2002 by Andrew Tridgell and others
http://rsync.samba.org/
Capabilities: 64-bit files, socketpairs, hard links, symlinks,
batchfiles, no IPv6, 64-bit system inums, 64-bit internal inums
The ppc machine has rsync, the same version but there is a warning:
rsync version 2.5.7 protocol version 26
Copyright (C) 1996-2002 by Andrew Tridgell and others
http://rsync.samba.org/
Capabilities: 64-bit files, no socketpairs, hard links, symlinks,
batchfiles,
IPv6, 64-bit system inums, 64-bit internal inums
WARNING: no 64-bit integers on this platform!
I have read the comment in rsync.h about suns and non 64 bit machines
(maybe I haven't fully absorbed the meaning of it). I have files on the
sun including devices but I'm not concerned about truncation when they
are transferred to the embedded linux.
The 'strange behaviour' is that the transfer completes and the sender
seems to send a -1 (as seen in main.c)
if (remote_version = 24) {
/* send a final goodbye message */
write_int(f_out, -1);
}
The reader reads this and gives an error:
[...]
recv_generator(var/spool/cron/crontabs,1866)
recv_generator(var/spool/repackage,1867)
recv_generator(var/state,1868)
recv_generator(var/tmp,1869)
recv_generator(var/ucd-snmp,1870)
recv_files finished
Integer overflow - attempted 64 bit offset
rsync error: requested action not supported (code 4) at ../io.c(381)
_exit_cleanup(code=4, file=../io.c, line=381): about to call exit(4)
rsync: connection unexpectedly closed (35060 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at ../io.c(165)
_exit_cleanup(code=12, file=../io.c, line=165): about to call exit(12)
If I initiate the transfer from the sun, it completes successfully.
So, is this a bug or expected behaviour?
-Cam
PS, in case it makes a difference, on the sun rsync is configured to run
from inetd, and on the embedded machine it is run in daemon mode by hand.
--
[EMAIL PROTECTED] --
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: IPv6 literal addresses on command line
--- cam [EMAIL PROTECTED] wrote: Hello all, Just to get some er, 'closure' on this, if you will (spot the thinly disguised, desperate repost)... To summarise: no-one is currently using rsync over IPv6 on linux. Not so. I got a response from someone happily using rsync on debian. Since they were using it in an environment where IPv6 DNS was set up, I went ahead and configured bind for my test network, only to find rsync still failing: [EMAIL PROTECTED] host -t doodah.ipv6.ournet.co.uk doodah.ipv6.ournet.co.uk has address 3ffe:501:420:120::2 [EMAIL PROTECTED] rsync -Cav -6 doodah:home/cam/dev/pcapture . doodah: Unknown host rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) I can packet-trace DNS requests for an A record (rather than a quad-A) arriving at my nameserver. AFAICT, on linux the rsync configure scripts look for the libinet6 library distributed with the USAGI IPv6 kernel patches - although frankly I am out of my depth here when it comes to analysing the Makefiles. Since I am developing against a vanilla 2.4.22 kernel, I suspect that this is what is breaking the name resolution - rsync is compiling with IPv6 support but is referencing the wrong name resolution calls. This probably isn't unreasonable since most people interested in IPv6 will be using USAGI - in our case we are developing against a mobile IPv6 implementation which is not currently patched with USAGI. I further assume that debian has the libinet6 library (at least in the case of the guy who wrote to me) and that a different mechanism is used on BSD to detect the presence of the KAME stack. I am not sufficiently competent (currently...) to be able to tell whether I can use USAGI's install-includes target to simply provide libinet6 or whether this will break my normal libraries. Much of the above is conjecture and I would be delighted to hear any comments or insights. cam __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: IPv6 literal addresses on command line
--- Paul Slootman [EMAIL PROTECTED] wrote: On Thu 27 Nov 2003, cam wrote: [EMAIL PROTECTED] host -t doodah.ipv6.ournet.co.uk doodah.ipv6.ournet.co.uk has address 3ffe:501:420:120::2 [EMAIL PROTECTED] rsync -Cav -6 doodah:home/cam/dev/pcapture . doodah: Unknown host Of course, here you're doing two different things: with and without a fully qualified name. Indeed. The packet trace indicates that the A record query is for the FQDN - I should have mentioned this. Using the FQDN in the command doesn't help. While dig requires the FQDN, all other apps that I've tested (ftp, ssh, ping6 etc) don't require it - assuming the appropriate search clause in /etc/resolv.conf That guy would be me... I'm well aware that it was you you that responded Paul.. you may remember that I accidentally replied offlist. I was just respecting your privacy. I'm Debian's rsync maintainer, so all Debian users (well, testing users at least) are also in the happy situation that their rsync supports IPv6. In the configure output, there's this line: checking ipv6 stack type... linux-glibc This implies to me that the standard glibc supports IPv6. I have no libinet6 or such on my system. rsync is linked with -lresolv, if that helps any... It might. I wonder if debian has included more of the USAGI patches that aren't applied to the 'vanilla' kernel from kernel.org? Various comments in the rsync TODO file suggest that different systems/distros handle address resolution differently: The KAME IPv6 patch is nice in theory but has proved a bit of a nightmare in practice. The basic idea of their patch is that rsync is rewritten to use the new getaddrinfo()/getnameinfo() interface, rather than gethostbyname()/gethostbyaddr() as in rsync 2.4.6. Systems that don't have the new interface are handled by providing our own implementation in lib/, which is selectively linked in. The problem with this is that it is really hard to get right on platforms that have a half-working implementation, so redefining these functions clashes with system headers, and leaving them out breaks. This affects at least OSF/1, RedHat 5, and Cobalt, which are moderately improtant.(sic) I assume that a similar situation holds for USAGI since, to my knowledge, the KAME patch doesn't apply to RedHats of any version number, being a patch for *BSD... Thanks for the response. I shall summarise any resolution to this that I find but for the moment I am looking into IPv6-4 translation. cam __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: IPv6 literal addresses on command line
--- Paul Slootman [EMAIL PROTECTED] wrote: On Thu 27 Nov 2003, cam wrote: I wonder if debian has included more of the USAGI patches that aren't applied to the 'vanilla' kernel from kernel.org? Various comments in the rsync TODO The kernel isn't the issue. When compiling a C program, nothing about the kernel is used. In fact, I use a vanilla 2.4.22 kernel, downloaded from a kernel.org mirror; i.e. not a Debian-supplied kernel. The issue is what kernel headers are used when building the glibc environment. Now I'm not that familiar with glibc, but my understanding is that glibc for linux takes certain kernel headers, and integrates that into the /usr/include tree. Whether or not you can build an IPv6-capable program is dependent on your glibc, rather than your kernel. OK - thanks for the pointer. This stuff is by no means clear to me yet. breaks. This affects at least OSF/1, RedHat 5, and Cobalt, which are moderately improtant.(sic) Ummm Isn't redhat 5 pretty ancient? I mean, a quick search indicates that RH 5 was around in 1998... OSF/1 development stopped in 1994 AFAIK (http://en2.wikipedia.org/wiki/OSF/1). No sane person would still be running those, I would hope. Sorry if I didn't make it clearer that this is a quote from the rsync TODO doc that came out of CVS! I quite agree and perhaps this tell us something about the level of maintenance of the docs! (Of course, my opinion is that everyone should use Debian (even on their Cobalt or Alpha), but I'm biased :-) I would be pretty tempted... but we are caught in a situation of having a fairly strict development platform. FreeBSD works pretty well too. Whatever the situation with regard to libraries, RedHat doesn't support rsync over IPv6 out of the box AFAICT. Perhaps with USAGI applied and then libinet6 installed. Cheers, cam __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
IPv6 literal addresses on command line
Hello all, Just to get some er, 'closure' on this, if you will (spot the thinly disguised, desperate repost)... To summarise: no-one is currently using rsync over IPv6 on linux. I superficially applied a patch suggested by a list member and while this fixed the problem of correctly parsing the IPv6 literal address, linux was still unable to find the host and appeared, unlike BSD, to ignore the /etc/hosts file. Several items are mentioned in the TODO file with regard to these issues so I suppose that, short of myself or someone else finding the time to engross themselves in the rsync code, this is the way it shall remain. Cheers, cam __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
IPv6 literal addresses on command line
Hello all, Can anyone give me a hint on how to specify an IPv6 address in an rsync address literal - the colon character is already used to seperate the host name from the remote directory AFAICT... I get, e.g. rsync -Cavb 3ffe:502:420:120::2:/home/cam/dev/proj 3ffe: Unknown host rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) Found some discussion of patches regarding IPv6 address-matching from about July so I went for the most recent CVS snapshot I could find (although to be honest and with only a superficial reading of the posts, the patches seemed to be related to matching addresses in some of the config files): rsync version 2.5.6cvs protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others http://rsync.samba.org/ Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 64-bit system inums, 64-bit internal inums Sorry if I'm missing something screamingly obvious and very grateful for any pointers... BTW, I find that setting up name lookups for our small IPv6 test network in /etc/hosts works fine in FreeBSD but not linux... a seperate problem I suppose. cheers, cam __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
