Hello,
I'm planning to use rsync for backup a lot of nodes to one rsync server over
wan.
I'm aware of the fact that on big directory tree rsync will consume a lot of
memory
and some time even hang.
Do you have any estimation on how many rsync client can work with one server
at the same time ?
I c
After lots of testing, I believe that I have discovered my problem. I am
trying to use rsync to synchronise a Red Hat 7.2 Server and a RedHat 7.3
Server and they have different versions of rsync on them.
I set up 2 x Red Hat 7.3 machines, both running rsync-2.5.4-2 and they work
fine, transfer
Everything worked, files transferred fine however a -vvv reveals that
the process did not end clean. The error is not seen with -v or even
-vv. Any insight? rsync version 2.5.5 protocol version 26, running on
Solaris 8.
Write failed flushing stdout buffer.
write stdout: Broken pipe
rsync error:
Worked like a charm, thanks.
The --server --sender options left me a little confused. I understand
what they stand for but these options are not in the help and they don't
appear to be variables.
After seeing the actual rsync cmdline in the output file on the remote
(mach3) it matched up with wh
[This is a copy of the contents of Debian bug report #147842.]
Package: rsync
Version: 2.5.5-0.2
Severity: normal
Cause
-
- rsync forks a child which in turn forks a grandchild in
main.c:do_recv().
- Diagnostics written by the grandchild need to be read by the child
using read_error_fd(
> I have two machines, call then A and B. I'm using rsync on B to download
> from A (I'm running rsync in daemon mode on A from inetd.conf). The rsyncing
> on B works fine except for one problem: when I run rsync on B to do the
> downloading from A, I get permission denied for files on A that hav
Hi guys, I have a simple question regarding using rsync when one has
read-only files on the src machine. My situation is the following:
I have two machines, call then A and B. I'm using rsync on B to download
from A (I'm running rsync in daemon mode on A from inetd.conf). The rsyncing
on B works
You're dealing with an ssh issue there. anybody who can't ssh can't rsync
-e ssh. Maybe you could take the public keys from everybody you want to
use it, and put them into the account you want them to ssh into, in
authorized_keys, with the appropriate command restrictions.
Tim Conway
[EMAIL
Yes. don't tell rsync to preserve permissions. That means Don't use -p
(or -a, which implies -p).
Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e
> > If so, I am trying to find the best way to restrict rsync -e ssh on the
> > remote machine. Prepending the authorized_keys entry with
> > command='rsync ...' 1024... results in the 'Protocol mismatch - is your
> > shell clean?' error.
This brings up an interesting question. Does anyone use
2002-05-22-14:00:27 Brian D. Hamm:
> Is it true that when running rsync via ssh (i.e. rsync -e ssh ...)
> the rsyncd.conf file is not applicable [...]
Yup. Exactly right. When you're using ssh (or rsh, as far as rsync
is concerned they're interchangeable plug parts) the rsync client
you invoke fr
Hi
I am using rsync for backup on the disks of a Linux backup server.
Obviously the server could store more data it the data were
compressed. I read the "rsync -> tar" thread. Unfortunately, a
compressed file system for Linuthere does not seem to exist yet.
However, rsync can use compression fo
Is it true that when running rsync via ssh (i.e. rsync -e ssh ...) the
rsyncd.conf file is not applicable on the remote since rsync is launched
via the ssh exec call once connected rather than from rsyncd as in a
direct connect.
If so, I am trying to find the best way to restrict rsync -e ssh on
>2. bug report: errors in file transfer (Michael Lachmann)
Sorry!
It turns out that the problem is bad memory here on my box. And I tried to
blame rsync!
Michael
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tux
> "Dave" == Dave Dykstra <[EMAIL PROTECTED]> writes:
Dave> On Fri, May 17, 2002 at 01:42:31PM -0700, Wayne Davison
Dave> wrote:
>> On Fri, 17 May 2002, Allen, John L. wrote:
>> > In my humble opinion, this problem with rsync growing a huge
>> > memory footprint when large
Yes you should be concerned about this problem.
I suggest these things:
1. Try running without -z. Some versions of rsync (2.5.4?) had a libz
bug.
2. Better yet, upgrade both sides to 2.5.5 and retry.
3. Make sure your solaris box has the latest NFS patches.
eric
Michael Lachmann wrote:
>
I just took a look at the 2.5.5 codebase to see how easy it would be to
write a little driver script that downloads a big directory tree from an
rsync daemon the chunky way (get a list of a module's subdirectories and
do the transfer by subdirectory). The reason for doing this is obvious
when yo
At 08:37 PM 5/20/02, you wrote:
>Doing so requires an upfront scan of the entire destination tree, and
>for the client to hold all this information in memory.
[I accidently sent this to Martin instead of the list...]
I wonder if it would be useful to have a partner program that would index
the r
Hi!
I just encountered a serious problem with rsync.
I used rsync to copy a big directory between two computers. The source
machine was a sun, the destination was a linux box. The destination
directory did not exist before the copy started.
I used the following command to copy the directory over
Wernicke, Heino (CGS) wrote:
>Thank you!
>That helps a little. But the permissions on target machine
>will not be inherited from parent folder as I wanted.
>
Uhm... removing ntsec shouldn't touch permissions at all...
can't just you use "chmod -R 755 *" after rsyncing?
--
Lapo 'Raist' Luchini
[
>
>
>I want
>the permission from the target files to be inherited from there parent
>folders that already exists on target and have several permissions
>set.
>
>
You could just try to start the receiving rsync with an empty CYGWIN
environment (i.e. without CYGWIN=ntsec) so that security is not
21 matches
Mail list logo
