similar to: Tru64 Unix patch for rsync 2.5.6.

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

This causes a compile error on Solaris. Fix: Index: socket.c =================================================================== RCS file: /cvsroot/rsync/socket.c,v retrieving revision 1.73 diff -u -r1.73 socket.c --- socket.c 25 Jan 2002 02:13:05 -0000 1.73 +++ socket.c 11 Feb 2002 20:04:33 -0000 @@ -590,7 +590,7 @@ if ((listener = socket(PF_INET, SOCK_STREAM, 0)) == -1) goto failed;

Tru64 UNIX has getaddrinfo but not by that name. Including <netdb.h> #defines getaddrinfo to ogetaddrinfo or ngetaddrinfo which exists in /usr/shlib/libc.so. So, AC_CHECK_FUNC(getaddrinfo) isn't enough to test for getaddrinfo. Best to AC_TRY_LINK so the #define takes effect. -- albert chin (china@thewrittenword.com) -- snip snip --- configure.in.orig Thu Jan 3 19:03:54 2002 +++

Hi everyone Following are a number of build-system cleanup patches. Some of them are prep-work for a possible upcoming automake/gnulib introduction. Best regards, Tiziano

We're still seeing sporadic failures of 'nbdkit nbd tls=', and I'm still trying to come up with a root cause fix (it may involve smarter use of gnutls_bye() in libnbd). In the meantime, here's what we know: when the hang/failure happens, the 'nbdkit nbd tls=' client process is stuck in a poll() waiting to see EOF from the server, while the 'nbdkit example1'

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

Where qemu-img 4.0 used to say 'virtual size: 100M', the 4.1 release now says 'virtual size: 100 MiB'. Similarly, '5.0G' turned into '5 GiB'. But rather than worry about potential future changes to the human-readable output, we can just use --output=json (at which point we no longer even have to force qemu-img to the C locale). It might be slightly more robust to

I'd very much like to get a stable 2.5 release out so that people can upgrade their production machines with confidence and so that distributors can freeze it. I know some people are still running 2.4.6 (+backports) for understandable reasons, but it would be good to give them the option to upgrade and avoid the hang bug. After this we can perhaps move on to 2.6 and be a bit more liberal in

--- configure.ac | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/configure.ac b/configure.ac index 2d638fc..58d0843 100644 --- a/configure.ac +++ b/configure.ac @@ -17,6 +17,10 @@ LDFLAGS=${LDFLAGS-""} AC_CANONICAL_HOST +dnl define the directory for replacement function since AC_LIBOBJ does not +dnl officially support subdirs and fails with

It may be useful to test whether the client's use of NBD_CMD_FLAG_NO_HOLE makes a difference; do this by adding a mode to --filter=nozero to force a non-trimming zero write. Signed-off-by: Eric Blake <eblake@redhat.com> --- filters/nozero/nbdkit-nozero-filter.pod | 19 +++++++---- filters/nozero/nozero.c | 45 ++++++++++++++++++++----- tests/test-nozero.sh

Where qemu-img 4.0 used to say 'virtual size: 100M', the 4.1 release now says 'virtual size: 100 MiB'. Similarly, '5.0G' turned into '5 GiB'. Update expected test output to tolerate either version of qemu. Signed-off-by: Eric Blake <eblake@redhat.com> --- I already know I want to send a v2; on IRC, Rich pointed out that 'qemu-img info --output=json'

Could someone with HEADER.ad in arpa/nameser.h please test the attached patch (against current) to see it it's detected. None of my platforms have the ad member. config.h will end up with "#define HAVE_HEADER_AD". -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net -------------- next part -------------- --- openssh/configure.ac.old 2003-09-08 06:33:33.000000000

UnixWare (not sure when, 7? 7.1?) introduces a new sockaddr_in structure that splits the 16 bit family entity into an 8-bit length and an 8-bit familiy memember: (from in.h): struct sockaddr_in { #ifdef __NEW_SOCKADDR__ sa_len_t sin_len; /* 8-bit structure length */ #endif sa_family_t sin_family; /* 8/16-bit address family (AF_INET) */ in_port_t sin_port; /* 16-bit port

With new-enough libnbd and our new dynamic-export mode, we can grab the export list from the server for replay to the client. Signed-off-by: Eric Blake <eblake@redhat.com> --- plugins/nbd/nbdkit-nbd-plugin.pod | 7 ++ tests/Makefile.am | 2 + plugins/nbd/nbd.c | 53 ++++++++++ tests/test-nbd-dynamic-content.sh | 2 +- tests/test-nbd-dynamic-list.sh

On Thu, Mar 26, 2020 at 02:34:41PM -0500, Eric Blake wrote: > We're still seeing sporadic failures of 'nbdkit nbd tls=', and I'm > still trying to come up with a root cause fix (it may involve smarter > use of gnutls_bye() in libnbd). In the meantime, here's what we know: > when the hang/failure happens, the 'nbdkit nbd tls=' client process is > stuck in

Another series on top of my exportname filter, marking off another todo bullet point. With this, you can now use the NBD plugin as a transparent passthrough of all export names served by the remote server in both directions (list advertisement server to client, and export name from client to server). Eric Blake (3): nbd: Implement .default_export, .export_description nbd: Add

Although RAW sockets can be used when specifying the source address of packets (defeating one of the aspects of the jail) some people may find it usefull to use utilities like ping(8) or traceroute(8) from inside jails. Enclosed is a patch I have written which gives you the option of allowing prison-root to create raw sockets inside the prison, so

Greetings, here is the output of the 'configure' step and the compile step (using the Compaq cc compiler that comes with Tru64 V5.1A. The configure reported success and most of the compile steps cam through error/warning free except for the one that stumbled. Can someone help me out here? I am willing to provide a binary for Tru64 V5.1A if we can swat this bug. We depend greatly on Rsync

https://bugzilla.mindrot.org/show_bug.cgi?id=2086 Bug ID: 2086 Summary: passwd struct does not have pw_gecos member on Android Classification: Unclassified Product: Portable OpenSSH Version: 6.2p1 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 Component: ssh

Enhance the testsuite to ensure we don't regress with recent changes to stdin/out handling. This adds: - test-single-sh.sh: prove that 'nbdkit -s sh script' is viable - test-stdio.sh: create plugin that checks stdin/out match /dev/null, then run it with -s, --run, -f Signed-off-by: Eric Blake <eblake@redhat.com> --- tests/Makefile.am | 23 ++++++