similar to: rsync 2.5.1 server - strange logs

hi there :) the code in util.c seems to have some bugs w/regard to compilation on 64-bit machines. in this case, the hardware is an Alpha running redhat 4.2 with pam turned off in the makefile. i get a whole series of errors, all of which say "passing arg 'n' of 'function' from incompatible pointer type. in util.c, checked out of the main branch the day before yesterday,

>Submitter-Id: current-users >Originator: Alex Vasylenko >Organization: >Confidential: no >Synopsis: [patch] net/rsync: problems in client name lookup code >Severity: non-critical >Priority: low >Category: ports >Class: sw-bug >Release: FreeBSD 4.8-RELEASE-p16 i386 >Environment: System: FreeBSD 4.8-RELEASE-p16 >Description: rsync does reverse name

I had to apply the following patch to the clientname.c check_name() function before I could successfully use "hosts allow" in rsyncd.conf. Without the patch I kept getting "rsync: forward name lookup for ... failed: Host not found" errors. These errors were produced by the rsync daemon, and putting in a debugging statement revealed that the port_buf being used had a large

https://bugzilla.samba.org/show_bug.cgi?id=8355 Summary: Use pointer after freeaddrinfo() Product: rsync Version: 3.0.8 Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: andrey at zonov.org

I''m spacing - how do I unravel a protent struct pointer? require ''win32/api'' include Win32 getprotobyname = API.new(''getprotobyname'', ''P'', ''P'', ''ws2_32'') ptr = getprotobyname.call(''tcp'') puts "Name: " + # ??? puts "Aliases: " + # ??? puts "Number: "

Hi, I have written a C code which would let me connect to the Asterisk Manager Interface. The code compiles successfully but on running the code I get unauthorized login shown in the Asterisk command line console. Here is my C code: #include<stdio.h> #include<netdb.h> #include<unistd.h> #include<string.h> #include<arpa/inet.h> #include<sys/types.h>

On Sat, Jan 7, 2017 at 2:30 PM, Peter Moody <mindrot at hda3.com> wrote: > so I spent a bit of time looking at this and it seems like the only > way to go, at least if I want to keep it in ssh_connect_direct(), is > to use pthreads. further, it seems like getting that accepted is > something of a long shot: Sorry, pthreads is a non-starter. I would have thought that using

Hi All, We have clients which dynamic IPs which we have setup with <host>.dyndns.org addresses. We have added these to the rsync.conf 'hosts allow=" but they are being denied access.. Is there anyway around this? Matt

I was wondering what everyone's thoughts were on a simpler way to exclude addresses from having listeners on them. I know a lot of people have multiple subnets, especially larger corporations. Some networks are non-route-able, and therefor unsuitable for use with SSH, aside from communication between other servers on the same subnet. Given that we may want to exclude those non-route-able

The vsock_diag.ko module already has a test suite but the core AF_VSOCK functionality has no tests. This patch series adds several test cases that exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept, half-closed connections, simultaneous connections). Stefan: Do you think we should have a single application or is better to split it in single tests (e.g.

The vsock_diag.ko module already has a test suite but the core AF_VSOCK functionality has no tests. This patch series adds several test cases that exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept, half-closed connections, simultaneous connections). The v1 of this series was originally sent by Stefan. v3: - Patch 6: * check the byte received in the recv_byte() * use

Hi, I have recently upgraded our web proxy to CentOS 5.6. Before the upgrade, squid was running fine. Since the upgrade, sometimes, squid crashes: > [root at stargate ~]# service squid status > squid dead but pid file exists Looking at log files, I think it could be related to logrotate stuff, > -rw-r----- 1 squid squid 42713088 May 3 04:02 store.log > -rw-r----- 1 squid squid

If bind() fails we _always_ should close socket. I sent this patch while ago to djm but I still don't see this fix in openssh_cvs. diff -urN openssh-2.3.0p1.org/sshd.c openssh-2.3.0p1/sshd.c --- openssh-2.3.0p1.org/sshd.c Sat Jan 6 19:54:11 2001 +++ openssh-2.3.0p1/sshd.c Sat Jan 6 19:55:48 2001 @@ -782,10 +782,10 @@ debug("Bind to port %s on %s.", strport, ntop); /*

On Tue, Nov 05, 2002 at 08:37:00AM -0800, Martin Pool wrote: > On 10 Oct 2002, "Green, Paul" <Paul.Green@stratus.com> wrote: > > No new CVS messages have appeared on the rsync-cvs archives since August > > 30th. This seems rather odd-- perhaps a daemon stopped working? If there > > has truly been no activity since that date, I apologize for > >

G'day. I'm having a great time trying to get a whole heap of XP workstations (from what I understand, they've been hotfixed+windows updated+whatever else a few days ago) to authenticate against Samba running on a FreeBSD 4.5-STABLE box. Basically, I add user accounts, machine accounts (with both "pw" and "smbpasswd"), then I can get the XP machines to successfully

I've just compiled 2.5.6 release on Tru64 V5.0A (configure detects alphaev67-dec-osf5.0, gcc release is a 3.1.1). rsync fails using rsync://<hostname>/ syntax. > lct@goliath(32) [rsync-2.5.6]$ ./rsync rsync://stitch/ > rsync: getaddrinfo: stitch 873: servname not supported for ai_socktype > rsync error: error in socket IO (code 10) at clientserver.c(83) Is there anyone else

The last versions of rsync fail to compile on Tru64 Unix (alpha), because of a typo in configure.in. The problem is that the code in configure check for sockaddr.sa_len, while the code uses sockaddr.sin_len. This patch fixes the problem. Please include it in the next version of rsync. diff -ur src-2.6.0/configure.in src-2.6.0-local/configure.in --- src-2.6.0-local/configure.in

Hi Orion, no, I still have this problem. I delay working on it as I the latest updates have not been installed on the server and on the client. I'll work again on this problem as soon as possible. Thanks Charles for your detailed information on how to track this problem. I'll check all these metrics. I have several clients for this nfs server and the problem seems only to occur from the

The attached patch adds a new 'ConnectTimeout' option (man page updated in patch) to avoid wasting time when the target host is down. I needed that because I was using rsync/rdist over ssh for massive files update and the default connect() took too long for my purpose. The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX on Linux, Solaris and HP-UX without

Hi all, I have a strange problem with qemu img disks allocated in a nfs share on a CentOS 6.4 host. Every time when I try to start a vm this error appears: char device redirected to /dev/pts/1 qemu-kvm: -drive file=/data/vmachines/win2k12adsrv/win2k12vol01.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: could not open disk image /data/vmachines/win2k12adsrv/win2k12vol01.img: