On Mon, Sep 11, 2006 at 01:31:00PM +0200, [EMAIL PROTECTED] wrote:
rsync: read error: Connection reset by peer (104)
This means the socket closed. Does rsync even get started on the remote
system? That would be the first thing to investigate. If it is getting
run, does the remote process
13143 bytes/s
totale size is 33936000 speed up 738.23
rsync error: unexplainded error (code 255) at main.c (1298) [generator
= 2.6.8]
Has anyone get this error message at the end of the session using ssl
and not during the data transfert...
It seems be working but I dont like this unexplained
Title: cwrsync strange path in error message
Dear Patricia:
First off, my apologies ahead of time for bothering you.
I am attempting to locate a Patricia Palumbo. She worked in Doylestown, Pa., as a court officer in the '60s. She would now be somewhere in her 70s. She was a very close
Since upgrading to
2.6.8 with the tag 3 patch, Ive been consistently getting an error using
rsync. We have about 100 servers using the client to a central backup
server and the issue is repeatable on the servers having the problem. About
10 of the servers are having the problem. The error
Good planIll test that now
and post my results.
From: Tevfik Karagülle
[mailto:[EMAIL PROTECTED]
Sent: Monday, August 07, 2006 3:36
PM
To: 'Rob Bosch';
rsync@lists.samba.org
Subject: RE: Invalid File Index
error
cwRsync version 2.0.8
usesnewer versions of cygwin (1.5.20
:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Rob BoschSent: Monday, August 07, 2006 11:12 PMTo:
rsync@lists.samba.orgSubject: Invalid File Index
error
Since upgrading
to 2.6.8 with the tag 3 patch, Ive been consistently getting an error using
rsync. We have about
Testing with an updated version of cygwin
(1.5.21) proved to resolve the problem. Thanks Tev!!!
Rob
From: Tevfik Karagülle
[mailto:[EMAIL PROTECTED]
Sent: Monday, August 07, 2006 3:36
PM
To: 'Rob Bosch';
rsync@lists.samba.org
Subject: RE: Invalid File Index
error
Time for an cwrsync upgrade :-)
From: Rob Bosch [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 08, 2006 12:36 AMTo: 'Tevfik
Karagülle'; rsync@lists.samba.orgSubject: RE: Invalid File Index
error
Testing with an
updated version of cygwin (1.5.21) proved to resolve
that anymore because that's what's
causing the problem in the first place...
Ideas?
-Erik
-Original Message-
From: Matt McCutchen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 02, 2006 5:54 PM
To: Erik Jacobs
Cc: rsync
Subject: Re: code 12 error when specifying files
On 8/2/06, Erik
On Thu 03 Aug 2006, Erik Jacobs wrote:
That works brilliantly, but I think I'm still doing something wrong.
rsync --exclude=* --include=.* -Lputzogv [EMAIL PROTECTED]::folder
/home/user/folder
result:
client: nothing to do: perhaps you need to specify some filenames or the
to be looking for...
For giggles I also tried re-specifying .* on the source, but that just
generated a code 12 error again...
argh.
-Erik
-Original Message-
From: Paul Slootman [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 03, 2006 8:29 AM
To: rsync@lists.samba.org; Matt McCutchen
On Thu, 3 Aug 2006, Erik Jacobs wrote:
Paul,
Almost all permutations of trailing slashes and no trailing slashes seem to
produce the same results...
I have to agree, I see the same behavior when using rsyncd transport
instead of ssh transport (as Erik is): trailing slashes seem to be
On Thu 03 Aug 2006, nathan r. hruby wrote:
I have to agree, I see the same behavior when using rsyncd transport
instead of ssh transport (as Erik is): trailing slashes seem to be
ignored, and instead of directory contents, you get the directory name.
From the manpage:
Note also that
be
willing to help me sort out the error messages I will undoubtedly receive :)
-Erik
-Original Message-
From: Paul Slootman [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 03, 2006 8:58 AM
To: rsync@lists.samba.org
Subject: Re: code 12 error when specifying files
On Thu 03 Aug 2006, nathan
BTW, I see no difference when using an rsync daemon or an ssh
connection, with the given problem:
remote# mkdir /tmp/test; cd /tmp/test; touch a b c .a .b .c
remote# ls -la
total 0
drwxr-xr-x 2 root root 57 Aug 3 15:06 .
drwxrwxrwt 3 root root 80 Aug 3 15:05 ..
-rw-r--r-- 1 root root 0 Aug
On Thu, 3 Aug 2006, Paul Slootman wrote:
On Thu 03 Aug 2006, nathan r. hruby wrote:
I have to agree, I see the same behavior when using rsyncd transport
instead of ssh transport (as Erik is): trailing slashes seem to be
ignored, and instead of directory contents, you get the directory name.
On Thu, 3 Aug 2006, nathan r. hruby wrote:
For example, for module x with path set to /home, tying to sync the
contents of server::home/user1/public_html/ yields me the directory
public_html, the the files within it.
s/::home/::x/
Someday I'll learn to type like a big person :)
-n
--
On Thu 03 Aug 2006, nathan r. hruby wrote:
From the manpage:
Note also that host and module references don't require a trailing
slash to copy the contents of the default directory.
So in this case the trailing slash wouldn't make a difference.
In my case I'm not grabbing the
On Thu, 3 Aug 2006, Paul Slootman wrote:
On Thu 03 Aug 2006, nathan r. hruby wrote:
From the manpage:
Note also that host and module references don't require a trailing
slash to copy the contents of the default directory.
So in this case the trailing slash wouldn't make a
On Thu 03 Aug 2006, nathan r. hruby wrote:
It's not what I'm seeing:
Hurm. What OS are you running this on?
Hint: check my email address :-)
After upgrading my local/receiver rsync to 2.6.8 I get this:
local# rsync remote::users/grp012/12/nhruby/public_html/
drwxr-xr-x 416
to include?
-Erik
-Original Message-
From: nathan r. hruby [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 03, 2006 9:55 AM
To: rsync@lists.samba.org
Subject: Re: code 12 error when specifying files
On Thu, 3 Aug 2006, Paul Slootman wrote:
On Thu 03 Aug 2006, nathan r. hruby wrote:
From
On Thu, 3 Aug 2006, Paul Slootman wrote:
On Thu 03 Aug 2006, nathan r. hruby wrote:
It's not what I'm seeing:
Hurm. What OS are you running this on?
Hint: check my email address :-)
Heh. Just checking :)
After upgrading my local/receiver rsync to 2.6.8 I get this:
local# rsync
: code 12 error when specifying files
On Thu 03 Aug 2006, nathan r. hruby wrote:
It's not what I'm seeing:
Hurm. What OS are you running this on?
Hint: check my email address :-)
After upgrading my local/receiver rsync to 2.6.8 I get this:
local# rsync remote::users/grp012/12/nhruby
On Wed, Aug 02, 2006 at 02:30:29PM -0400, Erik Jacobs wrote:
It works and lists fine. But if I choose a wildcard which contains a LOT of
files: rsync [EMAIL PROTECTED]::filefolder/.7.*
I get error in rsync protocol data stream (code 12)
Older rsync versions had a limit of 1000 filenames
On Thu, Aug 03, 2006 at 08:16:54AM -0400, Erik Jacobs wrote:
If I add the recursive option, it works, but I don't want to recurse
-- I only want to look at the files in this folder...
On a modern rsync, you specify -d instead of -r to copy directories by
name, or the immediate contents of a
On Thu, Aug 03, 2006 at 03:12:40PM +0200, Paul Slootman wrote:
Note that the trailing slash *is* needed on the ssh connection, see
without:
local# rsync --exclude='*' --include='.*' remote:/tmp/test
Password:
(nothing)
That's because you excluded the directory test, which is the first
On Thu, Aug 03, 2006 at 10:22:57AM -0400, Erik Jacobs wrote:
is there any reason why telling rsync what files you want it to
INCLUDE doesn't seem to tell it what files to include?
Without -r or -d, rsync completely skips directories (just like it skips
symlinks without -l). Just because a
Hi Wayne,I am getting the unexpected tag 3 error quite often when pushing using 2.6.8CVS on cygwin /WinXP to 2.6.8CVS on Linux over SSH (no daemon).The CVS version is pre tag-3.patch that you had posted.
I can compile with this patch on both sides (using cygwin on the client).However from
On Fri, Jul 21, 2006 at 12:22:24PM +0200, Julian Pace Ross wrote:
However from the previous mails it is not clear what is causing this and
whether the patch is required on the server, client or both.
It is the receiving side that causes the tag-3 error (the generator,
to be specific). So
On Thu, Jul 13, 2006 at 01:10:11PM -0700, Brett Hamilton wrote:
I confirmed that CAN_HARDLINK_SPECIAL was already commented out in
config.h, and I'm wondering if rsync should still be producing these
errors?
The code that produces the cited error is in the function
try_dests_non
https://bugzilla.samba.org/show_bug.cgi?id=3945
Summary: add arbitrary error reporting (with --error, perhaps)
Product: rsync
Version: 2.6.8
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority
Thanks Wayne. Indeed, it looks like my Mac cannot hard link device files.
I confirmed that CAN_HARDLINK_SPECIAL was already commented out in
config.h, and I'm wondering if rsync should still be producing these
errors? Also, I do in fact want to backup the device files in my
snapshots. Makes
On Fri, Jul 07, 2006 at 02:43:27PM -0700, Brett Hamilton wrote:
rsync: failed to hard-link /Volumes/backups/vanguard/backup.0/dev/agpgart
with dev/agpgart: Invalid argument (22)
The message Invalid argument is from your OS, and it looks like it is
being generated when trying to hard-link a
Dear Rsync,
I am seeing the following rsync error messages and I am wondering if it is
a sign of trouble, expected behavior, or a bug:
rsync: failed to hard-link /Volumes/backups/vanguard/backup.0/dev/agpgart
with dev/agpgart: Invalid argument (22)
rsync: failed to hard-link /Volumes/backups
Wayne,
Frank Fegert wrote:
Wayne,
thanks for your prompt response!
[self-inflicted pain snipped]
thanks for your help, but never mind! As usual, the problem
was sitting in front of the keyboard, between the headphones
;-)
For security reasons i use a wrapper script on the sending
machine,
On Sat, Jun 24, 2006 at 03:03:10PM +0200, Frank Fegert wrote:
i'm having a rather strange problem with rsync (v2.6.8). Rsync is run to
synchronize
two identical, rather old Solaris 2.6 servers.
I have heard of some problems with some Solaris versions of ssh, so it
may help to install openssh.
Wayne,
thanks for your prompt response!
Wayne Davison wrote:
On Sat, Jun 24, 2006 at 03:03:10PM +0200, Frank Fegert wrote:
i'm having a rather strange problem with rsync (v2.6.8). Rsync is run to
synchronize
two identical, rather old Solaris 2.6 servers.
I have heard of some problems with
Hi,
I have a problem with rsync, where the process stops with the message
inflate (token) returned -5
rsync error: error in rsync protocol data stream (code 12) at
token.c(478) [receiver=2.6.8]
rsync: writefd_unbuffered failed to write 4092 bytes [generator]: Broken
pipe (32)
rsync error: error
On Mon, May 22, 2006 at 05:21:47PM +0200, Morten W. Petersen wrote:
inflate (token) returned -5
This is the pertinent error. It indicates that there was a problem in
the zlib (compression) code. I assume that the file you're updating
already existing on the receiving side, correct? One way
This is the pertinent error. It indicates that there was a problem in
the zlib (compression) code. I assume that the file you're updating
already existing on the receiving side, correct? One way that should
avoid the problem in the compress code would be to drop the -z option.
Another way
))
+ if (send_msg((enum msgcode)code, buf, len))
return;
if (am_daemon) {
/* TODO: can we send the error to the user somehow? */
--- old/proto.h 2006-04-22 08:38:34 -0700
+++ new/proto.h 2006-05-18 10:45:31 -0700
@@ -104,7 +104,7 @@ void
Can anyone shed some light on this error we are getting or know of a way to find out more info? Thanks in advance for any help ... we are puzzled.Our server is Linux, rsync version 2.6.7 running in daemon mode
Our clients are windows; using cwrsync version 2.6.7Our method of transport is opening
On Wed, May 10, 2006 at 02:35:47PM +, Doug Lochart wrote:
Can anyone shed some light on this error we are getting or know of a
way to find out more info?
As explained on the issues and debugging page of the rsync website, a
closed connection tells us nothing about what has happened to cause
Ok we got the client log a minute ago and it also had a similar reset message, here is a snippetrsync: writefd_unbuffered failed to write 4 bytes: phase unknown[sender]: Connection reset by peer (104)
rsync: read error: Connection reset by peer (104)rsync error: error in rsync protocol data stream
On Wed, May 03, 2006 at 11:58:07AM +1000, Anthony Sadler wrote:
Notice /etc/localtime not being able to open?
That happens because you're using use chroot = yes. When rsync is
running inside a chroot jail, it cannot access files that exist outside
the rsync module's path.
Rsync attempts to
backups not working :P
Anthony Sadler
Far Edge Technology
w: (02) 8425 1400
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Davison
Sent: Wednesday, 3 May 2006 16:15
To: Anthony Sadler
Cc: rsync@lists.samba.org
Subject: Re: Rsync error on client end
transfer
the symbolic link verbatim or report an error and not
do the transfer at all. Changing the destination silently
is not what anyone would expect.
Thanks,
Gary Aviv
This e-mail and any attachments are confidential and may also be legally privileged and/or copyright material of Intec
On Tue, May 02, 2006 at 09:13:47AM -0400, Gary Aviv wrote:
In fact, even if the link is invalid it should be transfered.
The desire is to make a daemon that is running without chroot work as
closely as possible to a daemon that is running with chroot. So, what
we definitely need to avoid is
to prevent people doing mean things to our
servers :P)
For a long time rsync has worked, occasionly barfing due to lack of harddrive
space or for other external reasons. When we upgraded to version 2.6.8 however,
things started to die.
Here is a typical error we get
On Wed, May 03, 2006 at 11:58:07AM +1000, Anthony Sadler wrote:
unexpected tag 3 [sender]
My analysis shows that some deferred messages (which are those that
arrive in the generator when the generator is already trying to flush a
partial message down the socket) are not being handled by rwrite()
On Sat, Apr 29, 2006 at 01:48:28PM -0400, Gary Aviv wrote:
However, at the destination the .. is missing. for example
the link ../python/compile_plan.py becomes python/compile_plan.py
at the destination.
Is your daemon running without chroot? I just did a test, and rsync's
symlink sanitizing
it in error, please delete it immediately and notify the sender by e-mail. In such a case, reading, reproducing, printing or further dissemination of this e-mail or its contents is strictly prohibited and may be unlawful.
Intec Telecom Systems PLC does not represent or warrant that an attachment
I'm getting the following error when I'm trying to do just `./configure;
make` with the latest versions of rsync (both 2.6.7 and 2.6.8pre1):
gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c lib/compat.c -o lib/compat.o
lib/compat.c:171: error: conflicting types for `inet_aton'
/usr/include/arpa
DS I'm getting the following error when I'm trying to do just `./configure;
DS make` with the latest versions of rsync (both 2.6.7 and 2.6.8pre1):
DS gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c lib/compat.c -o lib/compat.o
DS lib/compat.c:171: error: conflicting types for `inet_aton'
DS /usr
On Thu, Apr 13, 2006 at 07:56:01PM +0900, Denis Solovyov wrote:
Sorry for the alarm, but I never collided with such behaviour before,
it was not obvious since all other software complied well all the time.
Thanks for the report anyway, as I discovered two things: (1) the code
for replacing a
:/rsync/BOMA
comment = BOMA backup area
read >
use chroot = no
timeout = 3600
transfer
logging = yes
It runs fine till the half of the operation, then
hangs up with the
following errors.
rsync error: error in socket IO (code 10) at io.c(1941)
rsync error: error in socket
https://bugzilla.samba.org/show_bug.cgi?id=3633
Summary: rsync files-from using rsync daemon fails w/ error code
12
Product: rsync
Version: 2.6.0
Platform: Other
OS/Version: Linux
Status: NEW
Severity
https://bugzilla.samba.org/show_bug.cgi?id=3633
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Wed, 22 Mar 2006, David Bear [EMAIL PROTECTED] wrote:
I am trying to use the syntax:
rsync -av -e ssh -l ssh-user [EMAIL PROTECTED]::module /dest
found at http://rsync.samba.org/ftp/rsync/rsync.html
There is an rsync daemon running on rhost.asu.edu and that has a
module named home.
so far)
[receiver]
rsync error: error in rsync protocol data stream (code 12) at
io.c(434)
There is an rsync daemon running on rhost.asu.edu and that has a
module named home. This is a file server box with only two interactive
logins allow, both administrative, so there is no rsync username
'+ %m/%d/%Y'`"
backups
Here is the cron
message that is sent out...
Read from remote hostsource_host: Connection reset by peer
rsync: connection unexpectedly closed (1879176 bytes received so
far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at
io.c(
On Mon, Mar 13, 2006 at 03:29:51PM -0500, Doug Lochart wrote:
1) Unix has as a limit 256 for the length of a file name. Does this
limit also apply to a fully qualified path?
It's MS Window that has the extremely short filename limit, and thus the
cygwin environment that cannot handle a long
On Tue, Mar 14, 2006 at 09:24:58AM -0500, Srinivas Kotapally wrote:
Read from remote host source_host: Connection reset by peer
This might be a connection-closing problem totally outside of rsync's
control. See the Issues and Debugging page for how you can do some
detective work to find out for
I have looked through the archives for this error and found some instance of it but no solutions. I have an idea for a workaround but I would like to get some clarification.1) Unix has as a limit 256 for the length of a file name. Does this limit also apply to a fully qualified path?
2) The path
https://bugzilla.samba.org/show_bug.cgi?id=3430
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
Hi,
Most of the rsync users love to have web interface or GUI list to rsync resources list.It is very useful and nice to have this.
http://www.debianhelp.co.uk/rsyncweb.htm
Hope who is responsible for this they will add this one
Thanks
On 05/01/06, John Van Essen [EMAIL PROTECTED] wrote:
On
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #7 from [EMAIL PROTECTED] 2006-01-21 09:16 MST ---
AFAIK, other tools that have a don't-traverse-file-systems option (find, du,
..) in the unix world ignore the mount point (as it logically belongs to the
fs you don't want
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #8 from [EMAIL PROTECTED] 2006-01-21 13:35 MST ---
Created an attachment (id=1705)
-- (https://bugzilla.samba.org/attachment.cgi?id=1705action=view)
Suggested changes to man page for --one-file-system
Wayne seems to have
https://bugzilla.samba.org/show_bug.cgi?id=3430
Summary: Error with ACL-patch and -x on mountpoint
Product: rsync
Version: 2.6.6
Platform: Other
OS/Version: FreeBSD
Status: NEW
Severity: minor
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #1 from [EMAIL PROTECTED] 2006-01-20 10:06 MST ---
The issue is that, when rsync detects that a directory is on another
filesystem, it sends the directory itself but skips the contents. See
send_directory in flist.c: it
to mount their own filesystem at that point.
The right fix is to eliminate this ACL error altogether: rsync should never
complain about a source item not having ACL info; it should just copy the item
without ACL info. (This is one of the things that must be fixed before the ACL
patch can make
filesystem.
The right fix is to eliminate this ACL error altogether: rsync should never
complain about a source item not having ACL info; it should just copy the item
without ACL info. (This is one of the things that must be fixed before the
ACL
patch can make it into the released version
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #4 from [EMAIL PROTECTED] 2006-01-20 13:02 MST ---
I know of no way to find the attributes of the underlying mount-point directory
when the mount is present. And leaving out the mount-point dir is not an
improvement in my
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #5 from [EMAIL PROTECTED] 2006-01-20 13:43 MST ---
(In reply to comment #4)
We could make this user-selectable by letting the user repeat the -x option to
choose to eliminate the mount-point dirs from the transfer.
In
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #6 from [EMAIL PROTECTED] 2006-01-20 15:03 MST ---
Created an attachment (id=1704)
-- (https://bugzilla.samba.org/attachment.cgi?id=1704action=view)
Makes -x -x exclude mount points themselves
This patch should do it.
On Jan 12, 2006, at 6:28 PM, Sean Peisert wrote:
Any advice on how to resolve this?
File a bug report with Apple.
They have modified the version of rsync that ships with OS X 10.4.x,
so they are the people who can ( should? ) fix it. FYI - There have
been problems with their version of
being used. In that case, the
file size being synced is 4MB. With the 4MB file i never got this
error.
network speeds probably now run from 300 baud to 10gigabit.
Any rule of thumb makes a bunch of assumptions about what is
"reasonable"
Outside those boundaries, the rule
Hi Tony,
rsync -aI --stats --copy-links
--temp-dir=/tmp/ --timeout=55 srcIp::srcPath/srcFile
destPath/destFile
I
think I'd try it WITHOUT the
l
of -al
--copy-links
--temp-dir=/tmp/
May i know why is it you would try it without "a"
option in "aI". What difference would it make ?
On Sun, Jan 08, 2006 at 12:38:51PM +0530, Vijay Ram.C wrote:
Let me also make a not that i am using a old version of rsync
..version 2.4 series. This is actually being used in the product..due
to the less space the binary takes to execute..
How big is your file list? If it is large, the
Hi all,
I am having a problem while sycing file. An error
is given as follows:
"io timeout after 55 second - exiting".
I have found this problem being posted in the mailing
list previously. But after reading those mails,
i understood that this problem occured only for file
Hi,
I have followed this link to configure rsync with ssh.I did all the suggested things on remote machine.When i try to run rsync from source machine i am getting following error
Error
protocol version mismatch -- is your shell clean?(see the rsync man page for an explanation)rsync error
On Thu, 5 Jan 2006, gg gg234 [EMAIL PROTECTED] wrote:
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
So... Did you look at the man page? Searching for clean brings
you to the DIAGNOSTICS section, which explains what the problem is
and how to
On Thu, Jan 05, 2006 at 04:28:51PM +1100, Buggy Code wrote:
Secrets:
test:password
You need to specify the user:password in the secrets file, not the
module:password. In your copy command you are telling rsync to
authorize itself using username sophos, but no password for that
username exists.
Wayne Davison wrote:
On Thu, Jan 05, 2006 at 04:28:51PM +1100, Buggy Code wrote:
Secrets:
test:password
You need to specify the user:password in the secrets file, not the
module:password. In your copy command you are telling rsync to
authorize itself using username sophos, but no password
On Thu, 5 Jan 2006, gg gg234 [EMAIL PROTECTED] wrote:
Hi John,
Thanks for your reply
I have check that and i try to run ssh 172.29.5.130 /bin/true out.dat
and i got the out.dat file with only text inside is Rejected
If rsync is seeing that Rejected that explains the error
, not all file where.. I found that all files had in fact been move
and assumed that the secrets file on the XP end caused this error.
Once I managed to find a user:group combination on the XP box that
appeared to be accepted by the rsync client, I know receive the
following error:
C:\c:\cygwin\bin
Hello Wayne,
On Wed, 28 Dec 2005 10:16:19 -0800 Wayne Davison [EMAIL PROTECTED] wrote:
On Wed, Dec 21, 2005 at 09:30:05AM -0500, Yuan, Zhiyong (Exchange) wrote:
readlink
directioty_1/directioty_2/directioty_3/A_very_long_File_name_omitted_here:
File or path name too long
The OS has a
On Thu, Dec 22, 2005 at 04:52:21PM -0800, Jason C. Leach wrote:
@ERROR: chdir failed
This is the important message from the daemon (which caused the
connection to close). This most likely means that the path specified
for the module you accessed is incorrect (the daemon's log file will
mention
On Tue, Dec 20, 2005 at 11:39:06AM -0500, Yuan, Zhiyong (Exchange) wrote:
checking for C compiler default output file name... configure: error: C
compiler cannot create executables
Perhaps you don't have a C compiler installed on your system?
..wayne..
--
To unsubscribe or change options
On Wed, Dec 21, 2005 at 09:30:05AM -0500, Yuan, Zhiyong (Exchange) wrote:
readlink
directioty_1/directioty_2/directioty_3/A_very_long_File_name_omitted_here:
File or path name too long
The OS has a maximum size that they will allow for the path+filename to
be specified. If a filename
Hi,
I'm trying to read some rsync error messages. I don't understand what
is the part from the local process, and what is a message from the
remote server.
Some start with 'rsync:' and others start with 'rsync error:', but
that is about it. Here is the output from a CRON process (so it has a
few
Hi,
rsync throws out the following error message.
building file list ...
readlink
directioty_1/directioty_2/directioty_3/A_very_long_File_name_omitted_here: File
or path name too long
Could anybody please give me some clue how to resolve this ?
Thanks bunch
Hi,
I am trying to install rsync on Solaris. While doing ./configure from the
downloaded, I got the following error message.
configure: Configuring rsync 2.6.6
checking build system type... sparc-sun-solaris2.8
checking host system type... sparc-sun-solaris2.8
checking target system type
On Tue, Dec 13, 2005 at 04:13:19AM -0800, Vijaya Krishna P.B. wrote:
Running rsync 2.6.6.version 29, getting following erorr
rsync: Failed to exec ssh: no such file or directory (2)
rsync error: error in IPC code (code14) at pipe.c(83)
rsync: connection unexpectedly closed (0 bytes
On Tue, Dec 13, 2005 at 11:57:42AM -0500, Dan Pritts wrote:
If you want to use the new rsync with rsh, you can just add -e rsh to your
rsync command line and it should work like the old version. There's
probably a compile time option for this too.
Yes, there's a configure-time option, but
\ /etc \
[EMAIL PROTECTED]:/home/backup/thismachine/
I am getting the following error
ssh: connect to hostx.x.x.x port 22: No route to hostrsync: connection unexpectedly closed (0 bytes received so far) [sender]rsync error: error in rsync protocol data stream (code 12) at io.c(420)
this is related
thanks for your reply.I have tried that also but still getting the same error
On 09/12/05, Paul Slootman [EMAIL PROTECTED] wrote:
On Fri 09 Dec 2005, gg gg234 wrote: ssh: connect to host x.x.x.x port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [sender
unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(165)
Doesn't rsync handle ftp://?
Regards
Marten
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart
On Fri, 2005-12-02 18:25:37 +0100, Marten Lehmann [EMAIL PROTECTED] wrote:
from a server where neither a rsync daemon nor ssh is running I'm trying
to backup the whole data with ftp. So my idea was to call rsync like this:
rsync -v -a 'ftp://1.2.3.4/' my_folder
Do you really expect a
so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(165)
Doesn't rsync handle ftp://?
Regards
Marten
__
Renovamos el Correo Yahoo!
Nuevos servicios, más seguridad
http://correo.yahoo.es
--
To unsubscribe
701 - 800 of 1491 matches
Mail list logo
