Hi,
I am doing the testing over this. As soon as the error will repeat, I
will send u a
snapshot of the same, and the command i used that time.
Right now, we are facing another problem, it is showing the following
error:
"send_files failed to open dir1/dir2/dir3/abcde.eps : permission denied"
I am trying to sync a tree, as follows:
/top
|-dir1
| |-data
|
|-newdir
| |-data
|
|-etc,etc
I need to pull just the 'data' directories, then push back
everything BUT the data directories.
I tried this:
rsync --include "*/" --include "data/" --exclude "*"
but it just includes
I am having a lot of troubles setting up an rsync daemon that works
properly. I've inspected the Faq-o-matic and as much of the past
archives as I can stand, but I can't seem to get any of the solutions
suggested there to work.
I'm having two problems.
First, I can't get password authenticatio
I have not had any problems when running 2.3.2 as a server,,, I updated
today and this is my error output. THe client is running rsync 2.5.2 on
FreeBSD 3.4 stable and the server is currently running rsync 2.5.2 on
FreeBSD 4.4 stable Any suggestions?
rsync: open connection using /usr/local/bin/
On Mon, Jan 28, 2002 at 11:05:38AM -0600, Dave Dykstra wrote:
> I'm the one who put in that wording because I think I didn't completely
> understand what it did at the time. I just changed the wording to
>
> This option tells rsync to delete directories when
> non-dire
On Mon, Jan 28, 2002 at 09:54:35AM -0500, David Birnbaum wrote:
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c main.c -o main.o
> main.c: In function `client_run':
> main.c:529: warning: `flist' might be used uninitialized in this function
Fixed by change the initialization to
str
Like i said, I think it's a kind of a safety. Going down entire directory
trees that don't exist on the master can wipe out a whole lot of data,
perhaps unintentionally. I suspect that close to 100% of people using
--delete pair it with --force. Without -force, it will not replace a
directo
ssh get's used by default when I don't specify otherwise.
I'm using rsync version 2.5.2 protocol version 26
on FreeBSD on both machines, currently.
Any ideas? I tried implicitly using --rsh=/usr/bin/ssh which doesn't work
either.
Somtimes I get this error:
send_files failed to open upd: Perm
On Sun, Jan 27, 2002 at 01:45:10PM -0500, [EMAIL PROTECTED] wrote:
>3 100%0.00kB/s0:00:00
> wrote 30496 bytes read 327051 bytes 14593.76 bytes/sec
> total size is 419896352 speedup is 1174.38
> Write failed flushing stdout buffer.
> write stdout: Broken pipe
>
> time /usr/l
On Mon, Jan 28, 2002 at 06:47:31AM -0800, [EMAIL PROTECTED] wrote:
> There you go - the symlink versus the populated directory. It's kind of a
> safety. To bypass it, add "--force".
> --force
> This options tells rsync to delete directories even if
> they are not empt
On Mon, Jan 28, 2002 at 06:47:31AM -0800, [EMAIL PROTECTED] wrote:
| There you go - the symlink versus the populated directory. It's kind of a
| safety. To bypass it, add "--force".
| --force
| This options tells rsync to delete directories even if
| they are not emp
Backing out the below change and changing the "unsigned int64" to just "int64"
removes compilation errors such as this:
rsync.h:339: warning: no semicolon at end of struct or union
rsync.h:339: parse error before `inode'
rsync.h:341: parse error before `dev'
on Linux kernel 2.2.19, I
Hi list,
I've a problem with rsync.
Server and client are running red hat 6.2.
I've got a server running rsync 2.4.6 as a daemon ( rsync --daemon )
For security i use IP checking.
( NB perhaps it's not the better way to do what i want )
I try 2.4.6 on the server and on my client.
on the client
Folks,
Just downloaded 2.5.2 to play with...builds with a raft of warnings, and
the symlink test fails. Transcript below for anyone with the knowledge
and energy to repair.
This is done with gcc-3.0.3.
David.
-
BUILD:
corona 2.5.2 7 $ make
gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I.
Here's an example.
dest = directory tree full of files all interdependent. a change in one
without the corresponding change in another makes the whole tree invalid.
If you just rsync the directory changes over, the tree is invalid from the
first change is started until the last one is done.
To
On Fri, Jan 25, 2002 at 11:52:19AM -0500, [EMAIL PROTECTED] wrote:
> Hi,
> Could anyone explain to me why I'm getting the following error messages
> during rsync -a operation? Thanks.
>
> error 1:
> Integer overflow - attempted 64 bit offset
> rsync error: requested action not supported (code 4)
There you go - the symlink versus the populated directory. It's kind of a
safety. To bypass it, add "--force".
--force
This options tells rsync to delete directories even if
they are not empty. This applies to both the --delete
option and to cases where rsy
On Mon, Jan 28, 2002 at 11:14:59AM +, pod wrote:
| > "PH" == Phil Howard <[EMAIL PROTECTED]> writes:
|
| PH> This problem has persisted for as long as I've used rsync. When
| PH> the --delete option is used, not all files are deleted from the
| PH> target, even though said f
I'm translating rsync.1, and i'm having some problems with the
--compare-dest option description, actually i dont understand the part
which describes the usefulness of this option, it says :
This is useful for doing transfers to a new destination while leaving
existing files intact, and the
> "PH" == Phil Howard <[EMAIL PROTECTED]> writes:
PH> This problem has persisted for as long as I've used rsync. When
PH> the --delete option is used, not all files are deleted from the
PH> target, even though said files are not present in the source. The
PH> particular case
20 matches
Mail list logo
