On Wed, May 05, 2004 at 11:34:29PM -0700, Jos Backus wrote:
> On Tue, May 04, 2004 at 08:14:22PM -0400, Chris Shoemaker wrote:
> > Just so I'm on the right page, AFAICT, batch mode doesn't work _at all_.
>
> If that's the case, it could be that the batch mode code needs to be updated
> to work w
At 04:50 PM 5/6/04 -0700, Wayne Davison wrote:
>You fell victim to one of the classic blunders! The most famous of
>which is, "Never get involved in a land war in Asia." But only slightly
>less well known is this: "Never exclude '*', when death is on the line!"
>Ha ha ha ha ha! Ha ha ha ha! [Cl
On Thu, May 06, 2004 at 01:20:34PM -0500, Michael C. Davis wrote:
> I've narrowed it down to a test script for a representative case
> which, again, should be working but isn't.
You fell victim to one of the classic blunders! The most famous of
which is, "Never get involved in a land war in Asia.
We use rsync to update an nfs server. After an update, we noticed that
a large number of clients didn't see the updated data.
It took me a while to be able to reliably reproduce this problem, but it
happens on old and new versions of rysnc. It also happens across all
the platforms we use here (s
On Thu, May 06, 2004 at 09:11:15AM -0700, Wayne Davison wrote:
> On Wed, May 05, 2004 at 11:34:29PM -0700, Jos Backus wrote:
> > On Tue, May 04, 2004 at 08:14:22PM -0400, Chris Shoemaker wrote:
> > > Just so I'm on the right page, AFAICT, batch mode doesn't work _at all_.
> >
> > If that's the c
On Wed, May 05, 2004 at 10:02:41AM +0200, Paul Slootman wrote:
> If that's the root cause of the problem, skipping the IPV6 socket when
> that call fails should suffice.
I've decided against using this change as I think it would prevent some
older Linux (any other?) systems from accepting IPv6 con
Hi, I'm using rsync to move the contents of one drive to another as part of
upgrading from an old Linux installation to a newer one. I have a script
which uses includes and excludes to select what to keep and what to throw
away, but for some reason my include rule isn't triggering when I think it
The rsync jobs take several hours to run and I check up on them from time to
time. The new progress features (110, 10% of 1100) are especially nice and I
don't want to lose them.
I can definitely script my way around this one but it's also possible to
solve it nicely within rsync.
Adam
- Ori
How about not using --progress when it's running from cron? ... unless
you're tailing the logfile, which should also work fine as-is.
If you need to process the logs otherwise later, feed it to "sed
's/^H.*^H///'" to dump the display crap... or is it "^M" instead of "^H"?
Those aren't literals.
Hi. I use rsync to suck down a large amount of data every night using a cron job that
logs to a file. If you run rsync --progress and redirect to a log file you end up with
the progress for each file piled up onto a single line. \r is generally ignored by
editors and viewers. That leads to my qu
On Wed, May 05, 2004 at 11:34:29PM -0700, Jos Backus wrote:
> On Tue, May 04, 2004 at 08:14:22PM -0400, Chris Shoemaker wrote:
> > Just so I'm on the right page, AFAICT, batch mode doesn't work _at all_.
>
> If that's the case, it could be that the batch mode code needs to be updated
> to work w
escape your @. I don't remember the details, but I know it got chewed up
by something in a past application.
Tim Conway
Unix System Administration
Contractor - IBM Global Services
desk:3032734776
[EMAIL PROTECTED]
Hi everybody -
I'm trying to write a Perl wrapper for some rsync tasks that n
On Wed, 2004-05-05 19:00:28 -0800, Web Hosting Network <[EMAIL PROTECTED]>
wrote in message <[EMAIL PROTECTED]>:
[snip]
So you want [EMAIL PROTECTED] to rsync machine_1:/some/path to
[EMAIL PROTECTED] in a path machine_2:/some/other/path ? This should be
done via ssh, right? Easy, that.
- On mac
13 matches
Mail list logo