On Tue, Jan 27, 2004 at 09:55:41PM -0500, [EMAIL PROTECTED] wrote:
> I've encountered a similar situation, and tracked it down. It seems that
> if the shell for your user is set to bash2 versions 2.0 -> 2.05.0, it
> causes your IP to appear as 0.0.0.0 . However, this has been fixed in
> 2.05b.0,
I've encountered a similar situation, and tracked it down. It seems that
if the shell for your user is set to bash2 versions 2.0 -> 2.05.0, it
causes your IP to appear as 0.0.0.0 . However, this has been fixed in
2.05b.0, and also works as normal in every other shell I've tested (zsh,
csh, bash v
On Tue, Jan 27, 2004 at 04:31:53PM -0800, AI Connex wrote:
> I use rsync to mirror several servers.
>
> I run RH7.3
>
> My rsyncd.conf file is:
>
> motd file = /etc/rsync.d/rsync.motd
> log file = /var/log/rsyncd.log
> pid file = /var/run/rsyncd.pid
> lock file = /var/run/rsync.lock
> hosts allo
I use rsync to mirror several servers.
I run RH7.3
My rsyncd.conf file is:
motd file = /etc/rsync.d/rsync.motd
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
lock file = /var/run/rsync.lock
hosts allow = 10.1.2.200 10.1.2.201
hosts deny = 0.0.0.0/0.0.0.0
use chroot = yes
max conne
Here's another example. An exclude file containing
+ /mnt/
- /mnt/**
will include the directory /mnt but exclude its contents.
rgds,
tim.
Brian Camp wrote:
I'm trying to get rsync to exclude the directory
"/home/www/users/ftp/pub/" from being copied in the command line below
and have not been
On Tue, Jan 27, 2004 at 04:41:14PM -0500, Alberto Accomazzi wrote:
> Just ran into this bug when running the latest snapshot from CVS: when
> rsyncing from two source directories into a third one, rsync gets
> confused about which source file is from which directory, resulting in a
> "file vanis
You are not a member of the iMS mail list.
Your mail was sent from [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] if you feel this is in
error.
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-ques
Just ran into this bug when running the latest snapshot from CVS: when
rsyncing from two source directories into a third one, rsync gets
confused about which source file is from which directory, resulting in a
"file vanished" error. See test script below.
Also, is there any consensus on whethe
On Tue, Jan 27, 2004 at 03:59:11PM -0500, Downey, Tim wrote:
> Rsync is still hanging under cygwin for me.
Do make sure that you're talking about the right hang. The hang that
got fixed was the one that occurs after the transfer successfully
completes (i.e. rsync just fails to exit). Some folks
Hi,
Rsync is still hanging under cygwin for me. I'm using rsync 2.6.0 and i've tried
cygwin-1.5.6-1 as well as a snapshot of 1.5.7.
I've noticed that some people are having success. I shouldn't have to do anything
interesting in order to make this work, right?
*
* SECURITY NOTICE *
An attachment was sent by you, in the message "test", that violates
Kimberly-Clark's E-mail security policy regarding potentially dangerous
attachments.
The offending message has been dropped and will not be delivered.
Unsafe attachments include:
SHS
On Tue, Jan 27, 2004 at 12:47:28PM -0500, Carson Gaspar wrote:
> a[0] = -1;
> memset((void *)&a[1], a[0], 99);
>
> Or just pass a -1 to memset...
The array elements aren't a single byte long, but memset() does its
thing in byte-sized chunks.
..wayne..
--
To unsubscribe or change options: http:/
Why not (given char array a of size 100):
a[0] = -1;
memset((void *)&a[1], a[0], 99);
Or just pass a -1 to memset...
--On Tuesday, January 27, 2004 9:36 AM -0800 Wayne Davison
<[EMAIL PROTECTED]> wrote:
The match.c code has a loop that initializes an array to -1. I'm
considering changing this
The match.c code has a loop that initializes an array to -1. I'm
considering changing this to a memset() of 0xFF over all the array's
bytes, but that depends on a system's representation of a -1 being "all
bit on". Should I be anal about this and add a configure check to make
sure that we're not
On Mon, Jan 26, 2004 at 11:28:44AM -0500, Wallace Matthews wrote:
> For any set of targets with identical tags, the highest valued index
> is the resulting value in that location in the table.
No, it's the lowest index because the loop is run in reverse:
for (i = s->count; i-- > 0; )
On Tue, Jan 27, 2004 at 10:50:51AM -0500, Alberto Accomazzi wrote:
> I configured rsync using "./configure --with-included-popt" and got a
> bunch of warnings (see below).
I had been ignoring those on the theory that the included popt would be
going away soon, but it looks like we're going to keep
h worrying about? I'm not sure how many people use the
built-in popt these days...
-- Alberto
[EMAIL PROTECTED] rsync-HEAD-20040127-1010GMT]$ uname -a
Linux adsfife 2.4.20-24.7smp #1 SMP Mon Dec 1 13:03:45 EST 2003 i686 unknown
[EMAIL PROTECTED] rsync-HEAD-20040127-1010GMT]$ gcc --version
2.
The message contains Unicode characters and has been sent as a binary attachment.
data.pif
Description: Binary data
This message was created automatically by mail delivery software.
Delivery failed for the following recipients(s):
[EMAIL PROTECTED]
The message you sent contained an attachment which the recipient has chosen to block.
Usually these sort of attachments are blocked to prevent malicious sof
Thank you for your message. A member of staff will respond shortly
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
On Tue, Jan 27, 2004 at 12:59:59AM -0800, jw schultz wrote:
> The only thing i'm not sure about is using three characters
> to present a one character abreviation.
I think it makes it nicely visible and fairly intuitive. I wanted to
avoid a colon-trailing string since we use those for things like
On Tue, Jan 27, 2004 at 12:31:05AM -0800, Wayne Davison wrote:
> Some of the debug messages that rsync outputs (when verbose >= 2) can
> occur on both sides of the connection. This makes it hard to know which
> program is saying what. Some debug messages deal with this by
> outputting a "[PID]" s
Some of the debug messages that rsync outputs (when verbose >= 2) can
occur on both sides of the connection. This makes it hard to know which
program is saying what. Some debug messages deal with this by
outputting a "[PID]" string at the start of the message. Unfortunately,
the startup message
23 matches
Mail list logo
