Re: getaddrinfo: Host not found problem

[EMAIL PROTECTED] writes: > As I understand it, "::" is used like "." is in IPv4. They are similar, but "::" can mean much more to IPv6 addresses than "." can to IPv4 addresses. For more information about this, please consult the following RFC: RFC 1924, _A Compact Representation of IPv6 Addr

Re: SPAM on List...

jw schultz <[EMAIL PROTECTED]> writes: > Hmm. Sounds like an ideal candidate for DoS. FWIW, I've used the mentioned setting on all my mailinglists and never had a problem. I know of other large mailinglists that have done the same and I have never heard of an DoS attacks on them. Erik. -- To

rsync 2.5.5 and exit 1 hard to explain.

Hi. I can't figure out why my rsync is exiting with exit code 1. I can't see any errors in the logs, and the last thing it says before quitting is: wrote 62157392 bytes read 12552 bytes 157591.75 bytes/sec total size is 2016803293 speedup is 32.44 _exit_cleanup(code=0, file=main.c, line

Re: rsync 2.5.5 segmentation fault on Linux x86.

[EMAIL PROTECTED] writes: > Erik: One more thing to try: redirect in /dev/null to the rsync > command. At one time, at least, its behaviour was different based on > the nature of its STDIN. Make sure STDERR and STDIN are redirected > somewhere, too... either a file or null. All our output are r

Re: rsync 2.5.5 segmentation fault on Linux x86.

Paul Haas <[EMAIL PROTECTED]> writes: > Then I run it once interactively and once through cron and compare stuff. > > Usually it's pretty obvious which environment variable is the problem. I also noticed in the logs that rsync exists with "exit code 12": Oct 1 01:31:59 backup-server inetd[1

Re: rsync 2.5.5 segmentation fault on Linux x86.

Paul Haas <[EMAIL PROTECTED]> writes: > This isn't specific to rsync. I must be missing something. The fact that rsync segfaults isn't specific to rsync? We run tens of thousands of cronjobs a week and none of them have so far segfaulted. However, since I can't make it segfault on the comma

rsync 2.5.5 segmentation fault on Linux x86.

piled from source with gcc 2.96 on RedHat Linux 7.2. Thanks for any pointers, Erik Enge. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Update to Current Issues; http://rsync.samba.org/issues.html

stream (code 12) at io.c(150) Aha! Adding "read only = false" fixed it. rsync 2.5.5 did not report this as a read only problem, 2.5.6 did. If many people are having this problem, perhaps it would be advisable to update the current issues. Erik Enge Software Engineer Professional R

Re: rsync: connection unexpectedly closed; reverse lookups?

Dave Dykstra <[EMAIL PROTECTED]> writes: > There were a lot of bugs in rsync 2.4.6 in those areas; upgrade to > 2.5.5 first. Thanks, Dave! That solved all my problems. I guess I should've upgraded before I sent the first email. I've learned my lesson. Erik. -- To unsubscribe or change optio

rsync: connection unexpectedly closed; reverse lookups?

box2. My question is this, then: is this why I cannot rsync box1 and box2? And if so, is there any way I can tell rsync to not try to do that? System configuration: RedHat 7.2, rsync version 2.4.6 protocol version 24 on Linux 2.4.18 x86. Thanks for any replies, Erik Enge. -- To unsubscribe or