ÎÒºÜÇî2003ÄêµÚÒ»ÆÚ×ã²ÊÔ¤²â×ÊÁÏ
1¡¢²©ÂåÄáÑÇVSACÃ×À¼
»ðÌì´óÓУº´ÓØÔÃû¿´£¬Ö÷¶Ó»ñʤµÄ¿ÉÄÜÐԽϴ󣬵«¸¸Ä¸³ÖÊÀ£¬µ£ÐÄÖ÷¶ÓÄÜȡʤ£¬Ó¦»ðÉúÊÀÍÁ£¬¶ÔÖ÷¶ÓÓÐÀû¡£2س±äµÃµ½ÀëΪ»ð£¬±ÈºÍØÔË«·½ÄÑ·Öʤ¸º£¬¹Ù¹í³ÖÊÀ¶ÔÖ÷¶Ó²»Àû£¬Ó¦Ë®¿ËÊÀ»ð¶Ô¿Í¶ÓÓÐÀû£¬µ«ÈÕ½¨ÊÜÊÀ»ðËùº¦£¬¶ÔÖ÷¶ÓÓÐÀû¡£ÈÕ½¨ÖúӦˮ£¬¶Ô¿Í¶ÓÓÐÀû¡£ÍƼö£º01£¨3£©
2¡¢²¼
Wayne Davison [mailto:[EMAIL PROTECTED]] wrote:
>Here are my comments on the changes:
> ? I have a question about the portability of the u_FOO -> uFOO_t
> changes. The former is the BSD syntax for the unsigned FOO typedefs,
> and the latter is what, POSIX? The changes work on Linux, at least
On Fri, Jan 10, 2003 at 02:25:57PM -0600, Edward King wrote:
> Has anyone seen this? Looking for past experiences / ideas. Will post
> progress.
>
> I'm tracking down a problem that seems to be caused by rsync. When
> moving files from a remote server I get a kernel panic.
>
> We have a numb
Here's my experience with a recent full restore exercise on a system/boot disk
which is
among the more interesting scenarios.
Rsync Backup Overview
-
I've a script based on Mike Rubel's rsync/snapshot backup notes
(www.mikerubel.org)
with two primary differences:
1. Files th
Has anyone seen this? Looking for past experiences / ideas. Will post
progress.
I'm tracking down a problem that seems to be caused by rsync. When
moving files from a remote server I get a kernel panic.
We have a number of servers that back up to a main box -- the panic only
occurs when a
On Fri, Jan 10, 2003 at 11:33:00AM -0800, Wayne Davison wrote:
> On Fri, Jan 10, 2003 at 01:23:45PM -0500, Green, Paul wrote:
> > The following patch still applies cleanly to the current cvs copy of rsync.
>
> Or did before the most recent Makefile.in changes. It's easy to merge
> this one proble
"Dr. Poo" <[EMAIL PROTECTED]> wrote
on 01/11/2003 09:25:18 AM:
> I'm very interested in this...
>
> My question(s) are why did you have to install a minimal system?
> Could you have just booted up with network and rsync and just rsynced
to a
> freshly paritioned/formatted disk?
And your proba
On Fri, Jan 10, 2003 at 01:23:45PM -0500, Green, Paul wrote:
> The following patch still applies cleanly to the current cvs copy of rsync.
Or did before the most recent Makefile.in changes. It's easy to merge
this one problem, though.
> Does anyone object to having these changes applied now, dur
Dave Dykstra wrote:
> Ok, I agree --modify-window should default to 2 (or 1 if that's all
> that's really needed) on cygwin. However, I don't like os-specific
> defines.
They have the advantage that the entire logic is visible in the .c file,
rather than split between the .c and configure.in.
>
The following patch still applies cleanly to the current cvs copy of rsync.
I apply it each night after I grab rsync from the build farm. Without it, I
don't get far at all. The purpose of the patch is to add executable
extension handling, which we need, and to clean up a few POSIX things and
supp
Dave Dykstra [mailto:[EMAIL PROTECTED]] wrote:
> 3. The Stratus VOS port is failing all 3 daemon tests in code
>that is used just for testing, saying it can't create the test
>socket. I don't know if there's a corresponding problem in the
>corresponding non-test code.
The socketpair_t
In article <[EMAIL PROTECTED]> (at Wed, 8 Jan 2003 08:24:13 -0600),
Dave Dykstra <[EMAIL PROTECTED]> says:
> In particular, I see that yours includes documentation changes and his
> doesn't.
Sorry,... One reason why I did not include manpage is that I'm not
so good at English...
Here's the des
Ok, I agree --modify-window should default to 2 (or 1 if that's all that's
really needed) on cygwin. However, I don't like os-specific defines.
That _WIN32 we've got there is the only one currently in the code, and
there's no occurrances of __CYGWIN__. I'd rather have a configure.in
rule for it.
I checked in this patch.
- Dave
On Thu, Jan 09, 2003 at 06:41:19PM -0800, jw schultz wrote:
> I just did a make clean to tidy up a bit and found four
> objects were missed. The seem to belong to the CHECK_PROGS
> set. Not sure where best to put them so created a
> CHECK_OBJS variable and added
On Fri, Jan 10, 2003 at 12:46:13AM -0800, Wayne Davison wrote:
> On Thu, Jan 09, 2003 at 05:09:07PM -0600, Dave Dykstra wrote:
> > I'm stuck on a problem that some machines on build.samba.org are
> > showing on the 'chgrp' test.
>
> I've checked in a fix for this bug.
Thanks, Wayne! Great work.
Hi,
I have a problem synchronizing a windows directory to a linux directory.
The filenames on the windows machine have sometimes french characters
with accents (quite usual for french language...). Rsync or the
filesystem of the linux box can obviously not handle this character type
and create fil
I'm very interested in this...
My question(s) are why did you have to install a minimal system?
Could you have just booted up with network and rsync and just rsynced to a
freshly paritioned/formatted disk?
What command did you use (to clarify) to make the origal rsync's of your
disk, and what w
On Thu, 9 Jan 2003, Dave Dykstra wrote:
> I went ahead and submitted Hideaki's patch pretty much as is. I took off
> the ifdef around the memset at the beginning of client_sockaddr() because
> I figured it wouldn't hurt to do anywhere. Besides, it was checking
> for a specific operating system (
On Fri, Jan 10, 2003 at 12:46:13AM -0800, Wayne Davison wrote:
> This is significant because -vvv is needed for the receiver to try to
> do IO after killing off the generator. This IO would sometimes fail
> if the generator died before [the IO] finished.
For the anal, I mixed up the generator and
On Thu, Jan 09, 2003 at 05:09:07PM -0600, Dave Dykstra wrote:
> I'm stuck on a problem that some machines on build.samba.org are
> showing on the 'chgrp' test.
I've checked in a fix for this bug. Here's what I discovered:
The reason only the chgrp test failed is that it is the only test that
use
20 matches
Mail list logo
