On Thu, 7 Feb 2002, Martin Pool wrote:
> A general-purpose RSYNC_OPTS variable would be more tasteful. I think
> popt makes supporting this fairly straightforward.
That's a nice idea. One area we'll want to be careful of is how the two
options interact.
For instance, we want to support old scr
Many thanks Dave!
I very much appreciate you taking the time to answer ALL my questions!
It was very instructive and helpful to me!
I have to say, two days ago, I never eared of rsync and today, I honestly
can't say how useful it is to me!
I guess someone doesn't know how much they miss someth
On 6 Feb 2002, Jack McKinney <[EMAIL PROTECTED]> wrote:
> > #!/bin/sh
> > eval `ssh-agent`
> > ssh-add
> > rsync foo bar
> > rsync qux zump
> > ..
> > kill $SSH_AGENT_PID
>
> As I indicated, I do not want to use ssh-agent.
For religious reasons?
--
Martin
The newer zlib-1.1.3 patch still has the problem.
According to Dave Dykstra:
> I was able to reproduce this between a Solaris 2.7 and 2.8 machine with and
> without ssh, although I don't have any time to debug it today. Can
> somebody try applying Jos Backus latest zlib 1.1.3 upgrade patch to se
On 6 Feb 2002, Wayne Davison <[EMAIL PROTECTED]> wrote:
> Cool. I like that one as well. Here's an implementation. This patch
> adds the configure option --with(out)-blocking-io and defines a new
> variable that gets put into config.h: DEFAULT_BLOCKING_IO.
OK, that's good. Thanks.
> The c
Dave,
I tried the snapshot... I get an error (after a ./configure;make).
gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c main.c -o main.o
main.c: In function `do_cmd':
main.c:184: `RSYNC_RSH' undeclared (first use in this function)
I added the #define to config.h and it compiled ok with a lot of
I was able to reproduce this between a Solaris 2.7 and 2.8 machine with and
without ssh, although I don't have any time to debug it today. Can
somebody try applying Jos Backus latest zlib 1.1.3 upgrade patch to see
if that helps?
- Dave
On Fri, Feb 01, 2002 at 02:01:03PM -0800, Stuart Anderson
On Wed, 6 Feb 2002, Dave Dykstra wrote:
> Of the proposed alternatives, I like this latter the best, changing
> --non-blocking-io to --no-blocking-io.
Cool. I like that one as well. Here's an implementation. This patch
adds the configure option --with(out)-blocking-io and defines a new
variabl
Looks like a fix for that went into 2.5.0. See revision 1.87 at
http://cvs.samba.org/cgi-bin/cvsweb/rsync/io.c
Tim & David, what version are you running?
2.5.2 has some serious problems, Eric. Try the latest development
snapshot at
rsync://rsync.samba.org/ftp/unpacked/rsync/
or
ft
Big Brother tells me that David Bolen wrote:
>
> Since it's an easy experiment - why "suspect" - did you try this? It
> should take virtually no time for the second (sans the initial
> checksum computation and transmission, which to be fair for large
> files and small block sizes can be quite si
On Wed, Feb 06, 2002 at 02:57:29PM -0500, Daniel Ouellet wrote:
> Dave Dykstra wrote:
> > JD Paul's patch which I previously referred to will give you what
> > you want.
>
> So, this patch would apply only when the :: is in use correct? That's what I
> understand.
Yes.
> > ":" syntax uses rsh (
On Wed, Feb 06, 2002 at 01:09:22PM -0500, Alberto Accomazzi wrote:
> Subject: Re: [path] & module options with SSH
>
> The discussion about syntax for remote file specification and the exchange
> between Martin and Wayne about configure options for rsh make me wonder if
> we should push some alt
Joseph,
check out the header file errcode.h in the rsync distribution.
That file and the structure found in log.c map the system exit codes to
the error messages you refer to, so the best way to programmatically
catch errors is simply to check the exit status returned by rsync.
-- Alberto
In
Probably Mike needs to use "read only = false" in his rsyncd.conf.
The default is "read only = true".
- Dave Dykstra
On Wed, Feb 06, 2002 at 02:16:55PM -0700, [EMAIL PROTECTED] wrote:
> Well, Mike. I'd guess it's a permission problem. Either on the
> destination itself or teh module defined i
Jack McKinney [[EMAIL PROTECTED]] writes:
> If I add 512 bytes at the begining of the file, then I would expect
> it. If I only add 14 bytes, then I don't think rsync will detect this,
> as it would require it to compute checksums start at EVERY byte instead
> of 512 byte checksums at offset
On Wed, Feb 06, 2002 at 11:55:29AM -0800, Jos Backus wrote:
> Here's the latest version of the batch mode cleanup patch.
Because I've been testing with Jos on that patch I went ahead and submitted
it to CVS.
- Dave
Well, Mike. I'd guess it's a permission problem. Either on the
destination itself or teh module defined in rsyncd.conf. Let's
concentrate on that second one. It's documented that by default, if you
do not specify a uid for a module (in rsyncd.conf), it will use -2
(usually corresponds to "
rsync -a /opt/config/. DevlServ:/opt/config
(see rsync.1)
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 'print pack(,
19061,29556,828
On Wed, Feb 06, 2002 at 02:14:23PM -0600, Jack McKinney wrote:
...
> If I add 512 bytes at the begining of the file, then I would expect
> it. If I only add 14 bytes, then I don't think rsync will detect this,
> as it would require it to compute checksums start at EVERY byte instead
> of 512
Is there a good place to get information about the list of all possible
output and error messages rsync generates? Or should I just muck around the
source code (which I haven't looked at yet) and find them?
I am doing something where I would like to parse rsync's output using Perl
into a set of
I'm updating to version 2.5.2 on a Solaris 2.7 (and 2.6) system.
The rsync process seems to run but finishes with the following:
wrote 91830 bytes read 4589600 bytes 105200.67 bytes/sec
total size is 127959731 speedup is 27.33
rsync error: error in file IO (code 11) at main.c(883)
I've tried
Big Brother tells me that Martin Pool wrote:
>
> With your commands, all messages will end up on both machines, which
> is fine to start with. But if you delete a message it will presumably
> keep on being copied back from the other machine. I don't know a good
> way for rsync to distinguish be
I want to rsync my home directory from interd1 to interp1. interd1 is
the server, so I enter:
rsync -vraz --delete ./ interp1::test
rsync: building file list ...
rsync: 6 files to consider.
delete_one: unlinek .rhosts: Permission denied
./
.profile
rsync: failed to open ".sh_history", continuin
Big Brother tells me that Martin Pool wrote:
> On 5 Feb 2002, Jack McKinney <[EMAIL PROTECTED]> wrote:
> >
> > Yes. blocks are 512 bytes long. If I add a 14 byte header on a message
> > near the beginning, then there are no identical blocks.
>
> In this case there are identical blocks sta
>
> On Wed, Feb 06, 2002 at 12:04:49PM -0500, Daniel Ouellet wrote:
> > So, I guess this is the answer to my question as to why the
> config wasn't
> > limiting the users.
> >
> > Great, thanks for that answer, but this still leave me with how
> can I limit
> > access to specific portion of the fi
Here's the latest version of the batch mode cleanup patch.
Index: batch.c
===
RCS file: /cvsroot/rsync/batch.c,v
retrieving revision 1.12
diff -u -r1.12 batch.c
--- batch.c 24 Jan 2002 08:09:46 - 1.12
+++ batch.c 6 F
Make that 2 of us who need to specify a large timeout.
I have found that I have to set the timeout to a large value (1) to
get the rsyncs to run successfully. Leaving it at the default seemed to
cause timeout/hang problems. Of course I still running a 2.4.6dev
version. I had troubles with 2.
Please can someone provide me with the exact syntax for using the rsh protocol. I am trying to copy files in a directory named /opt/config/ on server DevlServ to the same directory on server ApplServ1.
I have tried the following without much success:
rsync --rsh= cp /opt/config/on DevlServ:/
The discussion about syntax for remote file specification and the exchange
between Martin and Wayne about configure options for rsh make me wonder if
we should push some alternative syntax for specifying the transport protocol
to be used by rsync.
I, for one, always stick to the rsync://host/m
When i was getting these, I traced the process and its children (solaris:
truss -f). I found that one of the spawned threads was experiencing an io
timeout while the filelist was building. I had set no timeout, but it did
it at 60 seconds every time. I found that this corresponded to a
SELE
On Tue, Feb 05, 2002 at 11:28:54AM -0500, David Birnbaum wrote:
> I suspected that might be the case...now...how to determine the "real"
> problem? Does rsync log it somewhere? lsof shows that STDERR/STDOUT are
> going to /dev/null, so I hope it's not writing it there. Nothing
> informative in
On Wed, Feb 06, 2002 at 12:04:49PM -0500, Daniel Ouellet wrote:
> So, I guess this is the answer to my question as to why the config wasn't
> limiting the users.
>
> Great, thanks for that answer, but this still leave me with how can I limit
> access to specific portion of the file system as I pu
So, I guess this is the answer to my question as to why the config wasn't
limiting the users.
Great, thanks for that answer, but this still leave me with how can I limit
access to specific portion of the file system as I put in my email to make
sure the users only access what I would like them to
On Tue, Feb 05, 2002 at 09:38:04PM -0800, Wayne Davison wrote:
> On Wed, 6 Feb 2002, Martin Pool wrote:
> > OK, I agree --with-rsh should go in, but I think putting magic
> > characters into it is needlessly confusing. I would feel much better
> > about a separate configure option to set the defa
Nitin Agarwal <[EMAIL PROTECTED]> wrote:
> Dear Mr. Rusty,
> Thanks for the reply. The problem was sorted out by changing the uid option in
> rsyncd.conf file to root.
> We are facing two more problem now
> 1) while transferring the files, sometimes the transfer breaks in between and gives
> u
Several people have come up with fixes for that, and I'm not sure
which one is the best. Here's mine:
--- rsync.h.O Mon Jan 28 08:57:17 2002
+++ rsync.h Mon Jan 28 08:57:31 2002
@@ -303,8 +303,8 @@
* cope with platforms on which this is an unsigned int or even a
* struct. Later.
*/
Sorry, but that advice is wrong. Daniel's using the single colon so his
rsyncd.conf is being ignored. Ross needs JD Paul's patch which hasn't bee
integrated yet:
http://lists.samba.org/pipermail/rsync/2001-December/005488.html
- Dave
On Tue, Feb 05, 2002 at 11:58:55PM -0500, Daniel Ouellet
rsync --daemon and ssh do not currently work together at all. If you use
the syntax "hostname::module", rsync ignores the '-e ssh'. It sounds like
you are not using the double-colon syntax so rsyncd.conf is ignored.
Someone has posted a patch that enable the two to work together but it
hasn't ye
I've not seen that one before, but I tried to trace it in the source code.
A -1 from main.c line 842 means that start_client() returned a -1 which
means that start_socket_client returned -1 and there are several things
that can cause that. Mostly they seem to be if the server doesn't do its
part
On Tue, Feb 05, 2002 at 09:17:16AM -0500, Jim Ogilvie wrote:
> We've used rsync with an old ssh for a couple of years with no problems.
> Now trying to switch to openssh 3.0.2p1 so we can use protocol 2. Rsync
> makes
> the connection via ssh and does it's work. The problem is after rsync runs
>
On Wed, 6 Feb 2002, Martin Pool wrote:
> OK, I agree --with-rsh should go in, but I think putting magic
> characters into it is needlessly confusing. I would feel much better
> about a separate configure option to set the default O_NONBLOCK mode.
The complicating factor then becomes: how does th
On Tue, Feb 05, 2002 at 12:31:02PM -0800, Jennifer Lu wrote:
> I have compiled the new version 2.5.2 rsync in our servers,
> then ran rsync last night, there were some files not copied
> to destination server, both source and destination servers are
> running 2.5.2, I got the following error mes
Dear Sir,
We encountered one more error while running 'rsync' on our data. The
error is :
"Erroring writing 4092 bytes - exiting"
Kindly let us know the reason and solution for the same.
Thanks & Regards
Nitin Agarwal
Dear Mr. Martin,
We encountered one more error while running 'rsync' on our data. The
error is :
"Erroring writing 4092 bytes - exiting"
Kindly let us know the reason and solution for the same.
Thanks & Regards
Nitin Agarwal
On 4 Feb 2002, Jack McKinney <[EMAIL PROTECTED]> wrote:
> Well, I read my email on my laptop, and it is sometimes necessary to
> login to a central server to read my email (firewall issues). What I do is
> to peridocally sync with the central server (which we'll call "server") by:
>
> rsyn
On 5 Feb 2002, Jack McKinney <[EMAIL PROTECTED]> wrote:
> Big Brother tells me that Dave Dykstra wrote:
> > On Mon, Feb 04, 2002 at 11:58:04AM -0600, Jack McKinney wrote:
> > > If I change the status on the first message in the box (reply to it, delete
> > > it), then the ENTIRE mailbox is re-cop
Sure you can. Unless you are looking for a log that I don't know about.
All my server only have ssh and not only the log is written to a file on the
/var/log/rsyncd.log, but I did set it up to email me a copy of the transfer
activity.
My crontab have:
15 * * * * /usr/l
47 matches
Mail list logo
