On Sun, Dec 02, 2001 at 04:14:15PM +1100, Martin Pool wrote:
On 27 Nov 2001, Dave Dykstra [EMAIL PROTECTED] wrote:
I can reproduce it, and I think you've stumbled on a significant bug. The
problem is that rsync always assumes stat variable st_rdev, which
contains both the major and minor
On Sun, Dec 02, 2001 at 09:31:25PM -0500, Mark Eichin wrote:
| Perhaps a trailing / instead of training /. is supposed to work. I do
| not remember why I didn't start using it, but I am sure I would have tried
|
| Quite possibly because you've been bitten by class cp/rcp; cp is not
|
On Mon, Dec 03, 2001 at 12:16:46AM +1100, Martin Pool wrote:
| Does anybody care about supporting non-English message locales in
| rsync? (Do all sysadmins speak English? :-) Would anybody contribute
| translations if we had the framework?
Based on the quality of security and non-open-relay
- Original Message -
From: Phil Howard [EMAIL PROTECTED]
I'd contribute Texan but I've only lived in Texas for about 8 years so
I really don't know all of the language here, yet :-)
--
-
| Phil Howard - KA9WGN |
Well, that's a bug, I'd reckon, but i want to point out that a config file
with only one line is invalid. you need to have at least a module and its
path defined. I wouldn't expect daemon mode to gracefully handle an
invalid config, though simply declaring that the file is invalid and
I always get that too. I just figured i'd screwed something up.
solaris 7
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
On Sun, Dec 02, 2001 at 11:52:08PM +1100, Martin Pool wrote:
I see rsync has this in rsync.h
#ifndef HAVE_LCHOWN
#define lchown chown
#endif
So on Linux lchown changes the ownership on a symlink, whereas chown
on a symlink will change the ownership of its target. man lchown says
rsync already has a memory-hogging issue. Imagine having it search your
entire directory tree, checksumming all files, storing and sending them
all, comparing both lists looking for matching date/time/checksums to
guess where you've moved files to. You'd be better off to use a wrapper
the
Does it bother anybody else that -v prints directories twice? It first
prints all affected directories and files in recursive order and then
prints new directories again. I can't recall noticing that rsync always
did that, but I don't think it's a very recent change.
The directory is being
On Mon, Dec 03, 2001 at 12:15:41AM +1100, Martin Pool wrote:
Subject: Re: --no-detach option?
I'm starting to think we need to not show all the options in the
default --help output. I think perhaps the default should be to show
the commonly-used options (-avz, --include, : vs ::) and then
I have a question regarding how rsync changes ownership when syncing two
areas. Currently, I have this situation:
I have two areas over a WAN, we are trying to mirror from one site to
another. One site is not controlled by us and has different unix
groups.
When we copy one to the other, we
On Mon, Dec 03, 2001 at 01:21:29PM -0800, Sri Ramkrishna wrote:
I have a question regarding how rsync changes ownership when syncing two
areas. Currently, I have this situation:
I have two areas over a WAN, we are trying to mirror from one site to
another. One site is not controlled by us
On Mon, Dec 03, 2001 at 04:05:12PM -0600, Dave Dykstra wrote:
On Mon, Dec 03, 2001 at 01:21:29PM -0800, Sri Ramkrishna wrote:
I have a question regarding how rsync changes ownership when syncing two
areas. Currently, I have this situation:
I have two areas over a WAN, we are trying to
On Mon, Dec 03, 2001 at 09:55:53AM -0700, [EMAIL PROTECTED] wrote:
| rsync already has a memory-hogging issue. Imagine having it search your
| entire directory tree, checksumming all files, storing and sending them
| all, comparing both lists looking for matching date/time/checksums to
|
Hi,
I run rsync, with a Netware-directory mounted on a linux system (using ncpfs)
as
DESTINATION of the copy. This configuration works fine, but rsync incorrectly sets the
archive
bit (modify) for ALL the files included in the transfered directory (both modified and
not
modified).
In article [EMAIL PROTECTED] (at Tue, 4 Dec 2001 16:45:43 +1100),
Martin Pool [EMAIL PROTECTED] says:
Would it be sufficient for us to just read into a byte array large
enough to hold all reasonable IPv6 encodings, and then cast it as
appropriate? I have not had a chance to follow this idea
Would it be sufficient for us to just read into a byte array large
enough to hold all reasonable IPv6 encodings, and then cast it as
appropriate? I have not had a chance to follow this idea through yet.
I don't think at most 240 byte larger array has bad influence to
system. Moreover all of
On 4 Dec 2001, SUMIKAWA Munechika [EMAIL PROTECTED] wrote:
Would it be sufficient for us to just read into a byte array large
enough to hold all reasonable IPv6 encodings, and then cast it as
appropriate? I have not had a chance to follow this idea through yet.
I don't think at most
On 4 Dec 2001, SUMIKAWA Munechika [EMAIL PROTECTED] wrote:
client_addr(), client_name() always fails for IPv6 connection sice in
most of system,
sizeof(struct sockaddr_in) sizeof(struct sockaddr) sizeof(struct sockaddr_in6)
you should use sockaddr_storage for getpeername(). here is
19 matches
Mail list logo
