Hi everybody,
is it possible, to use the bwlimit - options when running rsync from
console / crontab ( not as deamon ).
Greetings
Sven
**
Diese Email wurde auf Viren geprueft.
Martin left off some context that might confuse some list readers. I
had inquired about how to sign the pre-release tarball. I signed
2.5.6pre1 with my personal key, but Martin suggested there be a team key.
On Thu, Jan 16, 2003 at 10:42:53AM +1100, Martin Pool wrote:
> [replied to list]
>
> T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I suppose if you wanted a hack, that would work. I was really looking
at something that could be used on a per module basis in rsyncd.conf or
on the command line. A commercial rsync competitor, TeamSite
OpenDeploy, has a file mode and a dir mode opti
Hi Wayne,
I ran a simple test of your patch at
http://www.clari.net/~wayne/rsync-files-from.patch
and it worked fine for me. The performance was just about the
same as for my --source-list patch.
Thanks,
Andy
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
I think the below patch is the cause of the failure of the Irix 6.5 type
on build.samba.org, because it is complaining about line 73 of the
Makefile which at least on my Linux machine is
rsync$(EXEEXT): $(OBJS)
It might be easiest for somebody who has an Irix machine that they can
use to debug
Thanks for the reminder. I checked in the second version.
- Dave
On Wed, Oct 09, 2002 at 12:45:03PM +0300, Sviatoslav Sviridov wrote:
> On Wed, 9 Oct 2002 10:03:33 +0200 (CEST)
> Ruediger Oertel <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > we ran into a little problem with rsync-2.5.5.
> >
>
On Wed, Jan 15, 2003 at 02:24:10PM -0800, jw schultz wrote:
> On Wed, Jan 15, 2003 at 10:27:31AM -0600, Dave Dykstra wrote:
> > In my research into this I also found that 2-1/2 years ago somebody
> > posted a patch that included a fix for this buried in it, and that I
> > had promised to integrate
On Wed, Jan 15, 2003 at 02:49:08PM -0800, jw schultz wrote:
> On Wed, Jan 15, 2003 at 10:03:33AM -0800, Wayne Davison wrote:
> > On Tue, Jan 14, 2003 at 07:57:48PM -0800, jw schultz wrote:
> > > with the -r or -a options does this [recurse] on
> > > directories in the --files-from list?
> >
> > Ye
In that case it looks like you want the proposed --chmod option discussed at
http://lists.samba.org/pipermail/rsync/2002-March/006477.html
and
http://lists.samba.org/pipermail/rsync/2003-January/009298.html
Once it is a command line option it could easily be made into a
per-module option
I am guessing that since the error is on the first instance of
the use of
foo$(VAR): foo.o
construct, that the Irix makefile parser doesn't know how to
deal with this line. Obviously they don't use GNU make
So here is a patch to Makefile.in that simplifies the use of
variables. This o
On Thu, Jan 16, 2003 at 02:52:38PM -0600, Dave Dykstra wrote:
> Also, if the transfer is being sent from the remote side, the file names
> are all getting sent over to the remote side first for --files-from and
> then sent back as part of the normal protocol, right? I had hoped we'd
> be able to a
On Mon, 13 Jan 2003, Dave Dykstra wrote:
> I don't understand enough how that syntax works in order to be able
> to write an explanation for people. Could you please try to write
> something up based on the current version checked in to CVS?
Here's a patch for the manpage:
http://biot.c
The patch from 2-1/2 years ago for changing copy-unsafe-links to follow
unsafe links on the destination side also included essentially this patch.
When I looked at it, however, I asked why in the world is unsafe_symlink()
doing strdup() in the first place. I think you could get rid of the
calls to
Dave Dykstra on Thu 16/01 14:33 -0600:
> The patch from 2-1/2 years ago for changing copy-unsafe-links to follow
> unsafe links on the destination side also included essentially this patch.
just to be clear, without using copy-unsafe-links, rsync still copies
absolute symlinks which point out of t
On Thu, Jan 16, 2003 at 03:44:44PM -0500, Scott Mcdermott wrote:
> Dave Dykstra on Thu 16/01 14:33 -0600:
> > The patch from 2-1/2 years ago for changing copy-unsafe-links to follow
> > unsafe links on the destination side also included essentially this patch.
>
> just to be clear, without using c
Dave Dykstra on Thu 16/01 14:57 -0600:
> > > The patch from 2-1/2 years ago for changing copy-unsafe-links to
> > > follow unsafe links on the destination side also included
> > > essentially this patch.
> >
> > just to be clear, without using copy-unsafe-links, rsync still
> > copies absolute sym
> On Wed, Jan 15, 2003 at 02:49:08PM -0800, jw schultz wrote:
> > You seem to see the files-from as a way of replacing command-line
> > args where i see it as a way of replacing the tree scan.
I actually think of it as both, since I also consider the command-line
as a way of replacing the tree sca
On Thu, Jan 16, 2003 at 05:07:13PM -0800, Wayne Davison wrote:
> > On Wed, Jan 15, 2003 at 02:49:08PM -0800, jw schultz wrote:
> > > You seem to see the files-from as a way of replacing command-line
> > > args where i see it as a way of replacing the tree scan.
>
> I actually think of it as both,
Hello,
I'm sorry to reply to my own message, but this is a bit of pressing and
disturbing issue. Perhaps I am missing an existing resource on the subject?
Please advise. Thank you,
Hans
--- Hans Zaunere <[EMAIL PROTECTED]> wrote:
>
> I have rsync-2.5.5 humming along on FreeBSD 4.7-STABLE w
On Wed, Jan 15, 2003 at 08:30:35PM -0800, Hans Zaunere wrote:
>
> I have rsync-2.5.5 humming along on FreeBSD 4.7-STABLE with no apparent
> problems. However, I notice when some clients connect to sync, I get this in
> /var/log/messages
>
> rsyncd[42843]: /etc/pwd.db: No such file or directory
>
The patch below supercedes my patch dated 14 Jan 2003. The new version
fixes serious problems due to memory reallocation/freeing of lists and is
also more efficient. The scheme has been simplified to store excluded
patterns in .rsync only (a "+ " pattern prefix may be used to force inclusion).
Not
On Thu, Jan 16, 2003 at 07:06:05PM -0800, jw schultz wrote:
> [...] and that entries therein are not flattened like they would be on
> the command-line (sans -R).
But they *are* flattened exactly like on the command-line, at least in
my current patch they are. That's what -R is for -- telling rsy
On Thu, Jan 16, 2003 at 02:33:26PM -0600, Dave Dykstra wrote:
> I think you could get rid of the calls to strdup() and the new local
> variables and possibly do a couple casts inside the function instead.
You wouldn't want to carve up the const strings with strtok() (which
adds nulls to the string
Sorry, another mistake on my part -- I didn't realize the strtok side
effect. It doesn't look to me like your new code looks at the last
component of the path like the old one might have. It would probably
be a good idea to put tests ending in "/..", for example "foo/../.."
and "foo/..", into tes
On Thu, Jan 16, 2003 at 04:08:01PM -0500, Scott Mcdermott wrote:
> Dave Dykstra on Thu 16/01 14:57 -0600:
> > > > The patch from 2-1/2 years ago for changing copy-unsafe-links to
> > > > follow unsafe links on the destination side also included
> > > > essentially this patch.
> > >
> > > just to b
On Thu, Jan 16, 2003 at 08:25:32PM -0600, Dave Dykstra wrote:
> It doesn't look to me like your new code looks at the last
> component of the path like the old one might have.
Right. I thought to myself as I was re-writing the function that that
wouldn't be possible (to end with ".."), but I coul
26 matches
Mail list logo
