similar to: 2.6.2 patch for AIX

Displaying 20 results from an estimated 800 matches similar to: "2.6.2 patch for AIX"

2004 Aug 18
1
[PATCH] fix AIX compile
Hi. I needed to do this small change to rsync.h to get rsync 2.6.2 to compile on AIX. The problem is that the extra comma is illegal (someone forgot to add support for it) in C89, and the AIX compiler do not accept it. The compiler I'm using is not yet updated to support C99 where the comma was allowed to stay. Please apply this patch to the next version of rsync. diff -ur
2004 Jan 17
1
--delete-sent-files (AKA --move-files)
Yes, it's time once again to return to the subject of moving files. With the recent changes to the communications code between the receiver and the generator, there is now a non-clogging channel that we can use to signal the sender when a file has been successfully transferred, which allows us delete the original for all transferred files. I have in the past waffled on whether this feature
2006 Dec 10
1
Rsync 2.6.9 Develops Conflict Between --stats, I think --delete-after and Local Filesystem Replication
Hi all, Well, yeah, that's it, really. :-) Try it. Works consistently, on Doze and Linux here ... # rsync -vvrlHSPtiypogD --stats --numeric-ids --delete-after --force -- partial-dir=.partial /tmp/ /var/tmp/ [...show stats...] unknown message 4:1 [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(307) [generator=2.6.9] rsync: connection unexpectedly closed (26
2007 Jan 02
3
DO NOT REPLY [Bug 4320] New: Daemon should send stdout, stderr of {pre, post}-xfer command to client
https://bugzilla.samba.org/show_bug.cgi?id=4320 Summary: Daemon should send stdout, stderr of {pre,post}-xfer command to client Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org
2016 Jan 21
1
[Bug 11683] New: hang on select when send many files
https://bugzilla.samba.org/show_bug.cgi?id=11683 Bug ID: 11683 Summary: hang on select when send many files Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: tom916 at
2006 Sep 30
2
DO NOT REPLY [Bug 4139] New: Generator process (running as daemon) hangs after kill SIGINT.
https://bugzilla.samba.org/show_bug.cgi?id=4139 Summary: Generator process (running as daemon) hangs after kill SIGINT. Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org
2006 May 03
2
Rsync error on client end: unexpected tag 3 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(843) [sender]
Hi guys: First post for me on this list. THE PROBLEM =========== I have several linux servers (ranging from Redhat 7.3 to FC3) that use Rsync (version 2.6.8 and 2.6.7, read on for reasons) to backup their data. A typical rsync backup script looks like this: ------------------------------------------------------------------------------------------ #!/bin/sh RSYNC_PASSWORD=<PASSWORD> rsync
2009 May 20
0
[PATCHv2-RFC 2/2] qemu-kvm: use common code for assigned msix
For assigned devices, use common code to enable msi-x. We need a special "assigned" option as assigned devices lack a standard way to get vector usage. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/device-assignment.c | 329 ++++++++++++------------------------------------ hw/device-assignment.h | 7 +- hw/msix.c | 9 ++- hw/pci.h
2009 May 20
0
[PATCHv2-RFC 2/2] qemu-kvm: use common code for assigned msix
For assigned devices, use common code to enable msi-x. We need a special "assigned" option as assigned devices lack a standard way to get vector usage. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/device-assignment.c | 329 ++++++++++++------------------------------------ hw/device-assignment.h | 7 +- hw/msix.c | 9 ++- hw/pci.h
2009 May 11
0
[PATCH 2/2] qemu-kvm: use common code for assigned msix
For assigned devices, use common code to enable msi-x. Add "hack" option as assigned devices lack a standard way to get vector usage. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/device-assignment.c | 336 ++++++++++++------------------------------------ hw/device-assignment.h | 8 +- hw/msix.c | 11 ++- hw/pci.h | 4 + 4 files
2009 May 11
0
[PATCH 2/2] qemu-kvm: use common code for assigned msix
For assigned devices, use common code to enable msi-x. Add "hack" option as assigned devices lack a standard way to get vector usage. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/device-assignment.c | 336 ++++++++++++------------------------------------ hw/device-assignment.h | 8 +- hw/msix.c | 11 ++- hw/pci.h | 4 + 4 files
2009 May 03
0
Server option PrintLastLog does not work on AIX
Hi Apparently, the server option "PrintLastLog" does not work on AIX. The last login time is always displayed, disregarding the option. When browsing the code, I found out there are several functions in loginrec.c which solely handle the processing of the last login info (login_get_lastlog, getlast_entry). Since AIX does not provide such a function natively, the configure script sets
2009 May 03
10
[Bug 1595] New: Server option PrintLastLog does not work on AIX
https://bugzilla.mindrot.org/show_bug.cgi?id=1595 Summary: Server option PrintLastLog does not work on AIX Product: Portable OpenSSH Version: 5.2p1 Platform: PPC OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy:
2011 Dec 16
5
[Bug 8666] New: --debug=all9 fail
https://bugzilla.samba.org/show_bug.cgi?id=8666 Summary: --debug=all9 fail Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chris at onthe.net.au QAContact: rsync-qa at
2010 Apr 01
0
OpenSSH Coredump and "Bad packet length" errors seen on 5.10 sparc sun4v (Generic_125100-10)
Hi, OpenSSH coredump was seen on our customer's side causing ssh login slow and manual command not workable. We need help to identify the root cause. Thanks!! >> Background: 1) server info: # uname -a SunOS owtnmncccm0cnmo 5.10 Generic_125100-10 sun4v sparc SUNW,Netra-CP3060 bash-3.00# /usr/local/bin/ssh -v OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007 bash-3.00# cat
2006 Feb 13
1
rsync SIGSEGV signal handler in Cygwin.
Hello! I am using rsync compiled with Cygwin on windows. I must call rsync from the *.bat script (I don't want to use a bash on Windows) and I have noticed that in the case when program compiled by Cygwin crashes via segmentation fault and default SIGSEGV handler is called, then it terminates process with exit status 0 as I see it from my *.bat script. (But if I invoke a program from bash
2007 Oct 10
0
patch for rsync: provides "nice = N" option
Hi folks, This is a patch for rsync 2.6.9 - I'm not sure if this is the proper vehicle for submitting them. It's been working great for us for months, and I hope it's seen as offering useful utility in general. Steve (who is not a subscriber to this list) --- Stephen J Friedl | Security Consultant | UNIX Wizard | +1 714 544-6561 www.unixwiz.net | Tustin, Calif. USA |
2020 May 12
0
Segfault on read.socket with long message
Thanks for the report, but it is unlikely anyone would be able to help just based on this code fragment. We need a small and minimal but complete reproducible example. That example should not use any contributed packages (a contributed package may be corrupting memory, which may cause R to crash). It is easy to get a bugzilla account - please see https://www.r-project.org/bugs.html for more
2020 May 12
1
Segfault on read.socket with long message
Thanks for the link.? Somehow the information about how to join the bugzilla site was not available at bugzilla and buried in the CRAN web site instructions on reporting bugs (which pointed me at Bugzilla and not the page you showed me). The example is pretty minimal.? I left the tracing statements (flog.trace()) and the toJSON, fromJSON in as I thought they might provide some context for
2020 May 11
2
Segfault on read.socket with long message
I'm trying to implement a connection between two processes using a simple socket mechanism. The messages are rather long object stored as JSON. R is crashing with a segmentation fault when I try to read my test message (which is 5305 bytes long). I first send the length in bytes and then I send the actual message. Here is my R code: library(jsonlite) library(futile.logger)