Hi *,
Thanks to you all for the response. And sorry If I've wasted your time.
I found the reason for this not working.
Now I've added the line..
strict modes = false
in to my rsyncd.conf file. Now it works.
Once again thanks, and to Mr. Martin, The passwd is intended for testing
only
Hi,
bash$ rsync -a [EMAIL PROTECTED]::test test
Password:
@ERROR: auth failed on module test
I did try this command, But the result is same as you can see above..
Any other suggestion?..
Thanks,
_Saran_
On Mon, 25 Jun 2001, Tim Potter wrote:
J.Saravanan writes:
When I try to transfer
On Fri, Jun 22, 2001 at 05:26:52PM -0700, Wayne Davison wrote:
On Fri, 22 Jun 2001, Dave Dykstra wrote:
The default value of the non-blocking IO is not
affected by this change -- instead rsync only sets non-blocking IO by
default if the RSYNC_RSH value is rsh or (if remsh is around)
On 25 Jun 2001, Tim Potter [EMAIL PROTECTED] wrote:
J.Saravanan writes:
Thanks to you all for the response. And sorry If I've wasted your time.
I found the reason for this not working.
Now I've added the line..
strict modes = false
in to my rsyncd.conf file. Now it
For those of you who haven't been on the rsync mailing list long, you may
be wondering about who maintains what parts of rsync. The history is that
rsync was primarily written by Andrew Tridge Tridgell, and that a couple
years ago he asked for somebody else to maintain it while he finished his
I saw this, which seems like a bug. The only difference between
check_rsync and rsync aliases is that the former uses dry run.
greenwood$ check_rsync_greenwood_2_anorien | less
building file list ... done
.cvsrc
.emacs
wrote 33842 bytes read 28 bytes 1575.35 bytes/sec
total size is 14437856
On Mon, 25 Jun 2001, Dave Dykstra wrote:
On Fri, Jun 22, 2001 at 05:26:52PM -0700, Wayne Davison wrote:
I think a better method would be for rsync to have a default blocking
setting for the default remote shell (perhaps configurable along with
what the remote shell is), and then let the
I am doing a poor man cluster using rsync to synchronize content of 2
servers each of which has its own directly attached storage. Since it is a
cluster (load balancer on top of these 2 servers), new additions as well as
deletions might appear on any of the 2 servers.
Newly added files are
I do this sort of thing between my home and work machines, but only one
system changes at a time, and I do a sync in the appropriate direction at
the end of each session.
I think what you want may not be possible, since rsync doesn't maintain
any database about the files it handles and deleted
I was wondering if the protocol should be updated to avoid ever
assuming that an EOF on the socket was OK. The only case I know of
where this allowed is when we're listing modules from an rsync server.
If we modified the protocol to have the daemon rsync send an EOF token
(such as @RSYND: EOF)
Does it matter what order the options/switches are placed? I ask
because I did an initial rsync of data from a NetApp to a SAN box using
the following:
rsync -avz --exclude=.snapshot /mail-data/ /mnt
The .snapshot directory is only useful to Ontap in this instance so I
did not want it
In general Britton is correct. The only thing that might help Ivan is the
-u option, which works strictly on file modification time. He didn't
mention having discovered it.
- Dave Dykstra
On Mon, Jun 25, 2001 at 12:01:00PM -0800, Britton wrote:
I do this sort of thing between my home and
Thank you, Britton and Dave.
I do use -qaHzu options, but that does not seem to be enough because file
needs to be present on both servers for this to work. If I went through
trouble of catching up any activity on the file system and trigger update on
remote host, I would be as happy as Britton
Jeff
Ordering of switches is important, but only for the --include* --exclude*
switches. For your sample command there should be no difference.
We also use NetApp filers and exclude .snapshot, the same way you have. It
works fine... The
--delete command won't help here as it will delete
So, if I understand you correctly, it should work fine (with
improvements) like this:
rsync --exclude=.snapshot --delete -avW /mail-data/ /mnt
Is this correct?
Thanks.
~JK
Wilson, Mark - MST wrote:
Jeff
Ordering of switches is important, but only for the --include* --exclude*
Leave out the --delete. It will delete everything on the destination that is
not present on the source, except for .snapshot -if present. If you want to
play with --delete use the -n option as well. This will tell you what rsync
is going to do without actually doing anything.
Suggest you try
On 25 Jun 2001, Britton [EMAIL PROTECTED] wrote:
I saw this, which seems like a bug. The only difference between
check_rsync and rsync aliases is that the former uses dry run.
Can you please show us what the alias actually expand to? Reading
your mind at this distance is difficult. ;-)
--
(Thanks for the nice summary.)
I'm pretty open to other people becoming co-maintainers. I think it
would be good to follow the standard open source procedure of giving
access once people have submitted a few good patches to establish
credibility. The final decision is tridge's I think, but it
Wayne,
I've applied your simple nohang patch. The longer nohang patch I'm not
nearly as confident of. It goes back to a method used in early
versions of rsync where it uses a buffer that can grow indefinately.
Just some history on this. The earliest versions of rsync had no
buffer, then when I
19 matches
Mail list logo
