On Wed, Mar 05, 2003 at 06:12:50PM +1100, Christopher Vance wrote:
> Suppose I have a particular version of a largish compressed archive,
> most likely a .tgz or .tbz2, and that a remote machine has a newer,
> and only slightly different, version of the same archive, where most
> of the content has
Tom Freeman wrote:
Hi folks,
I am running rsync via a perl script run in a cronjob.
my $message = `/usr/bin/rsync --rsh=/usr/local/openssh/bin/ssh -avu
$directory $destination`;
I want to be able to write this data
to a log file, so that if things don't work, I can find out what's wrong.
Is this a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 5 Mar 2003 18:12, Christopher Vance wrote:
> If rsync were to do its file stat and content comparisons on the
> uncompressed copy of both archives, might this not result in less
> network traffic (sending only the small changes) than just looki
Suppose I have a particular version of a largish compressed archive,
most likely a .tgz or .tbz2, and that a remote machine has a newer,
and only slightly different, version of the same archive, where most
of the content hasn't actually changed much. I might attempt to obtain
a copy of the newer a
>> i think stdout as
>> rsync -avvP MCI/ MCI2 --stats --delete 1>1.txt
>> doesn't give me the 6c6c on the command line nor in the 1.txt
>>
>> rsync -avvP MCI/ MCI2 --stats --delete 2>1.txt
>> leaves an empty 1.txt.
>
> If that is the right syntax for your shell (it is for bash)
> then it isn't comi
>> i think stdout as
>> rsync -avvP MCI/ MCI2 --stats --delete 1>1.txt
>> doesn't give me the 6c6c on the command line nor in the 1.txt
>>
>> rsync -avvP MCI/ MCI2 --stats --delete 2>1.txt
>> leaves an empty 1.txt.
>
> If that is the right syntax for your shell (it is for bash)
> then it isn't comi
On Tue, Mar 04, 2003 at 03:59:07PM +0100, Philipp W. wrote:
> > However RH7.3 would i think have a very old version of
> > rsync. I'd start by upgrading. Certainly there isn't much
> > value of anyone spelunking the current code to fix a problem
> > that might already be fixed.
>
> it was 2.5.4,
on systems that has separate IPv4/v6 socket layer (i.e. IPv4 packet
does not get routed to AF_INET6 socket) rsync --daemon would accept
IPv6 sessions only. open_socket_in() tries to deal with the
situation, but it was not enough. here's the patch.
(it is r
It may be helpful to capture STDERR with STDOUT.
my $message = `/usr/bin/rsync --rsh=/usr/local/openssh/bin/ssh -avu
$directory $destination 2>&1`;
See: http://perldoc.com/perl5.8.0/pod/perlop.html#%60STRING%60
At 05:47 PM 3/4/2003 +, you wrote:
Hi folks,
I am running rsync via a perl scri
Tom Freeman wrote:
> Hi folks,
> I am running rsync via a perl script run in a cronjob.
>
> Here's the command i'm running
>
> my $message = `/usr/bin/rsync --rsh=/usr/local/openssh/bin/ssh -avu
> $directory $destination`;
>
> At the moment when I run the script it writes all output to the
> scr
Hi folks,
I am running rsync via a perl script run in a cronjob.
Here's the command i'm running
my $message = `/usr/bin/rsync --rsh=/usr/local/openssh/bin/ssh -avu
$directory $destination`;
At the moment when I run the script it writes all output to the screen. I
want to be able to write this da
Oliver Braun <[EMAIL PROTECTED]> wrote:
> we had problems on FreeBSD-current. Attached is a patch we use on
> FreeBSD-current.
This patch is also applicable to OpenBSD and most likely NetBSD.
--
Christian "naddy" Weisgerber [EMAIL PROTECTED]
--
To unsubscribe or change
> However RH7.3 would i think have a very old version of
> rsync. I'd start by upgrading. Certainly there isn't much
> value of anyone spelunking the current code to fix a problem
> that might already be fixed.
it was 2.5.4, now i compiled 2.5.6
with the same issues...
> You didn't say if this
Sending direct to me what should be going to the list is a
sure way to get a low priority in my queue.
On Mon, Mar 03, 2003 at 03:02:47PM +0100, Philipp W. wrote:
> > Very strange. My first thought was a bad terminal settting
> > and oddly enough u8 (user string 8) could do that but i
> > can't s
Hi,
we had problems on FreeBSD-current. Attached is a patch we use on
FreeBSD-current. Find below the quote of the author of the patch. Maybe
it is possible to incorporate this patch into the next release of
rsync.
From [EMAIL PROTECTED]:
"It seems the daemon mode of rsync depends on an IPv4-m
15 matches
Mail list logo
