I get an error message when trying to decompress rsync-3.0.7pre1.tar.gz:
[ ~/Desktop ]$ tar -xzvf rsync-3.0.7pre1.tar.gz
tar: Unrecognized archive format: Inappropriate file type or format
tar: Error exit delayed from previous errors.
On Dec 21, 2009, at 10:10 PM, Wayne Davison wrote:
Rsync vers
henri wrote:
When launchd executed this command, it did not work. The system.log file reads
"Exited with exit code: 1".
Can you redirect the output to a file so it can tell you why it failed? e.g.
>file.out 2>&1
One common thing that prevents non-interactive sudo is this tty setting:
De
Rsync version 3.0.7pre1 is now available for release testing. This is
a bug-fix release.
Please test this new release and send email to the rsync mailing list
with any questions, comments, or bug reports.
To see a full summary of the changes since 3.0.6, visit this link:
http://rsync.samba.or
Hello,
I'm not sure if this is the right place to post but here goes. Is anyone aware
of a company/consultant that specialises or is an expert in corporate rsync
deployments? It's possible that we might want to engage the services of such as
person/company.
Regards
Tom
--
Please use reply-a
https://bugzilla.samba.org/show_bug.cgi?id=7004
Summary: Use posix_fadvise to free cached file contents when done
Product: rsync
Version: 3.0.6
Platform: All
OS/Version: Linux
Status: NEW
Severity: enhancement
Prior
On Mon, 2009-12-21 at 11:56 -0700, Rsync CVS commit messages wrote:
> Modified Files:
> FAQ.html
> Log Message:
> Mention the inflate issue that was recently fixed.
It's a little confusing to recommend people to upgrade to an rsync
version (3.0.7) that hasn't been released yet.
--
Matt
-
https://bugzilla.samba.org/show_bug.cgi?id=2294
way...@samba.org changed:
What|Removed |Added
CC||bugzilla.samba@zmi.at
--- Com
https://bugzilla.samba.org/show_bug.cgi?id=6996
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Tue, Dec 15, 2009 at 8:12 AM, thomas Anderson wrote:
> I have installed rsync from source but when i want to remove it
Check the Makefile to see where it is installing things, or just run
"make install" again to see what it put where. Typically you just
need to remove the executable (e.g. /u
On Sun, Dec 13, 2009 at 8:47 PM, Matt McCutchen wrote:
> But if the data block was exactly CHUNK_SIZE (32816), it would fill
> the output buffer with nothing remaining, and the next call to "inflate"
> would return Z_BUF_ERROR.
Thanks for tracking that down! I have fixed this issue in both the
3
On Mon, 2009-12-21 at 10:00 -0800, Wayne Davison wrote:
> Since the reason for things falling apart is that there was an error
> in the compress code, you should be able to avoid the hang (for now)
> by avoiding the -z option.
The compression error has been explained:
http://lists.samba.org/archi
On Mon, 2009-12-21 at 10:04 -0800, Wayne Davison wrote:
> Have you verified that rsync is actually stalled, and not simply
> sending incremental file-list information in between files? (e.g.
> strace rsync and see what it's doing.) You could try using
> --no-inc-recursive to see if doing all the
On Wed, Dec 9, 2009 at 10:08 PM, Max Arnold wrote:
> in my tests rsync often stalls
> for 3-5 minutes, while wget stalls only for several seconds and then
> continues download.
Have you verified that rsync is actually stalled, and not simply
sending incremental file-list information in between f
On Thu, Dec 10, 2009 at 11:58 PM, Dimitar Dimitrov
wrote:
> script as described in the troubleshooting procedures). The strace output is
> here
What this reveals is that the receiver is getting an inflate error,
sending the message to the generator, exiting, and then the generator
hangs reading
On Sat, Dec 19, 2009 at 9:37 PM, David Christensen
wrote:
> I'm having trouble with rsync invoked on Debian 5.0.3 pulling files from
> Windows XP SP3/ Cygwin 1.5.25.
If this is not a daemon connection, then it's probably the cygwin
pipe-hang bug. I have heard that a more modern cygwin (such as 1
On Thu, Dec 17, 2009 at 6:49 AM, Joel Peabody wrote:
> However, in looking at the output of one particular job it looks
> like it’s just putting out directories when it gets to a new one, and not
> the filename of everything it’s transferring.
No, that's pretty impossible. If you're losing outpu
https://bugzilla.samba.org/show_bug.cgi?id=6995
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Sun, Dec 20, 2009 at 11:03 PM, Robert Siemer
wrote:
> I thought the latter returns the subset of the current “global” file list
> of the receiver side
There is no such thing. Since rsync is duplicating the sender's
files, there is only a list of the sender's files in memory except for
some si
On Mon, Dec 21, 2009 at 8:27 AM, Aubert Thibaud wrote:
> 2009/12/21 15:50:43 [22219] unknown message 36:1587200 [generator]
That's an error from the generator complaining about the data coming
over the local pipe from the receiver. If that data is messed up,
things have to be in pretty bad shape
On Mon 21 Dec 2009, Aubert Thibaud wrote:
>
> Since our server migration from OES1 (rsync-3.0.2-2.1) to OES2
> (rsync-3.0.6-3.1), rsync backup do not work anymore.
> rsync error: error in rsync protocol data stream (code 12) at io.c(600)
> [sender=3.0.6]
> _exit_cleanup(code=12, file=io.c, line=
Hello,
Since our server migration from OES1 (rsync-3.0.2-2.1) to OES2
(rsync-3.0.6-3.1), rsync backup do not work anymore.
Here is some explanation :
With a full verbose mode on the source server :
rsync: writefd_unbuffered failed to write 631 bytes to socket [sender]:
Broken pipe (32)
rsync
21 matches
Mail list logo
