similar to: [Apt-rpm] I: [PATCH] 0.5.4cnc9: rsync method support

Hello, It would be goog if attached patch will be included in upstream. This patch adds option --apt-support for rsync and with this option rsync will print some additiona information about file being transfered. No program logic changed. Having this option in rsync we can have apt with rsync method support. Begin forwarded message: Date: Fri, 31 Jan 2003 11:34:14 -0200 From: Gustavo Niemeyer

On Thu, Aug 28, 2003 at 12:51:16PM +0300, Sviatoslav Sviridov/Lintec Project wrote: > > Sorry for direct reply, but mail server at samba.org blocks my messages. Postmasters, Martin, For your consideration. > Begin forwarded message: > > Date: Thu, 28 Aug 2003 12:43:54 +0300 > From: Sviatoslav Sviridov/Lintec Project <svd@lintec.minsk.by> > To: rsync@lists.samba.org

Hi, we ran into a little problem with rsync-2.5.5. Setup: you run rsync-2.5.5 as normal rsync over ssh (ie. not connecting to a rsync server). If you start such a rsync but interrupt the pulling process with Ctrl-C, the process on the other side may start to allocate all memory on the remote machine. As fa as we have analyzed the problem, the remote rsync process wants to issue a error message

-----BEGIN PGP SIGNED MESSAGE----- I added the following code to log_exit(): void log_exit(int code, const char *file, int line) { static int error_count=0; if(error_count++ > 10) { abort(); } To force it to bail earlier instead of overflowing the stack. As you can see at frame #50, it is trying to log that the connection went away unexpectantly.

The second rsync-2.5.6 pre-release version is now available at: http://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre2.tar.gz ftp://rsync.samba.org/pub/rsync/preview/rsync-2.5.6pre2.tar.gz rsync://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre2.tar.gz There's also a corresponding '.sig' file that contains a gpg signature of the file; the public key is available on the

The first rsync-2.5.6 pre-release version is now available at: http://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre1.tar.gz ftp://rsync.samba.org/pub/rsync/preview/rsync-2.5.6pre1.tar.gz rsync://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre1.tar.gz There's also a corresponding '.sig' file that contains a gpg signature of the file; the public key is available on the

Our environment: samba4 (alpha12) running on centos 5.4. We are experimenting with Hyper-V 2008 R2 Failover Clustering, which requires Active Directory. We are trying to see if samba-4 will work as the AD server. We are trying to create 2 node failover cluster. Both nodes have joined the domain successfully (with samba-4 as the DC). But subsequent steps of creating the "Failover

Hi, I'm using rsync (version 2.5.5 protocol version 26) on RedHat Linux 8.0: rsync -ae ssh /tmp/junk/ otherhost:/tmp/junk If I interrupt rsync (^C), sometimes rsync on the other host dumps core or uses all (!) available memory and all CPU. gdb on a core file: $ gdb -q /usr/bin/rsync /tmp/core.4576 (no debugging symbols found)... Core was generated by `/usr/bin/rsync --server --sender

Ville Herva [mailto:vherva@niksula.hut.fi] wrote: > Of course, whether O_TEXT is defined or not does not > necessarily imply the availability of "t", but I > can't think of better alternative. Stratus VOS implements O_TEXT and O_BINARY but does not recognize "t". We have the options defined in ANS C and in POSIX. I'm at home and don't have my reference

I tend to be someone who automatically looks for trends, and the nice thing about having just one list is that it lets me know where people are having problems. Judging by the number of questions we get, one of the biggest challenges for inexperienced rsync users is knowing why a particular file is included or excluded. Way in the back of my mind I see a need for an option that, for every file

I'd like to suggest that this is now a great time to create two separate cvs branches for the rsync product. One, which I'll tentatively call 2_5, would hold the version of the code that has been released to the world as 2.5.6. The other, which I'll tentatively call head, would hold the development activity leading up to the next field release. I'm not bound to these names, but I

Patches welcome, eh, Paul? Upon further (belated) investigation, there are 2 affected places in receiver.c with this error message. Both call write_file(). And write_file is called only in those two places. So that is the appropriate location to patch. Especially since the obvious fix is to use the rewrite code already there for the sparse file writes.

On Fri, Jul 31, 2015 at 12:15 AM, Herbie Robinson <HerbieRobinson at verizon.net> wrote: > I have been quietly working on a port of LLVM to Stratus VOS. The OS is > always big endian (because customers need to migrate data to new hardware > quickly and can't afford to convert). This entails presenting a big endian > programming model no matter what the hardware does. We

Hello, we are migrating an Asterisk install from Trixbox/Asterisk 1.2 to Elastix 0.92 with asterisk-1.4.17 on CentOS 5. I need to migrate an funtion that consults a remote sybase database, using ODBC and freetds. On the new server I am able to connect to the database using isql without problems. When I try to connect from asterisk logs show: pbx.c: Function ODBC_SQL not registered Indeed I

http://bugzilla.mindrot.org/show_bug.cgi?id=978 Summary: The supplied realpath function mangles pathnames. Product: Portable OpenSSH Version: 3.9p1 Platform: Other OS/Version: other Status: NEW Severity: minor Priority: P3 Component: Miscellaneous AssignedTo: openssh-bugs at mindrot.org

That's true for block ciphers, but ChaCha20+poly1305 is a stream cipher. On Wed, 29 Mar 2023, Robinson, Herbie wrote: > > I?m hardly an expert on this, but if I remember correctly, the rekey rate > for good security is mostly dependent on the cipher block size.? I left my > reference books at home; so, I can?t come up with a reference for you, but I > would take Chris?

(I'm not subscribed; Mail-Followup-To set.) Contrary to the claim in the output of ./configure --help, $CPPFLAGS is in fact not influential. --- rsync-2.5.5/Makefile.in~ 2002-03-24 23:36:34.000000000 -0500 +++ rsync-2.5.5/Makefile.in 2002-11-12 17:52:04.000000000 -0500 @@ -9,6 +9,7 @@ LIBS=@LIBS@ CC=@CC@ CFLAGS=@CFLAGS@ +CPPFLAGS=@CPPFLAGS@ LDFLAGS=@LDFLAGS@

I have discovered that rsync 2.5.6 uses the mkstemp() routine wich do not have a 64bits version into the AIX libc. A very simple workaround to the big files writing rsync pb. is to not use this routine that create files w/ mkstemp() by modifying the "syscall.c" source file at line 154 as following : #if defined(HAVE_SECURE_MKSTEMP) && defined(HAVE_FCHMOD) become #if

Take 2... this version only adds code to discard the cache on Linux and uses the right name for the fadvise call. It''s a bit ugly - I basically just put #ifdef __linux__ around the fadvise calls - but I don''t have the ability to develop something suitable for Solaris... > Attached is a patch to unstable that stops save/restore/dump from > hosing > Dom0 when dealing

Rsync release 2.5.6 is now available at http://ftp.samba.org/ftp/rsync/rsync-2.5.6.tar.gz ftp://ftp.samba.org/pub/rsync/rsync-2.5.6.tar.gz rsync://ftp.samba.org/ftp/rsync/rsync-2.5.6.tar.gz There is a '.sig' file at corresponding URLs with a gpg signature; the public key is available on the pgp keyservers. NEWS for rsync version 2.5.6, aka the dwd-between-jobs release Changes