On Wed, Oct 22, 2003 at 11:59:48PM -0400, John E. Malmberg wrote:
> jw schultz wrote:
> >On Tue, Oct 21, 2003 at 11:28:11PM -0400, John E. Malmberg wrote:
> >
> >>
> >>There are approximately 235 global and static variables in rsync, and
> >>of those 105 are obviously never modified after the fork(
jw schultz wrote:
On Tue, Oct 21, 2003 at 11:28:11PM -0400, John E. Malmberg wrote:
There are approximately 235 global and static variables in rsync, and
of those 105 are obviously never modified after the fork() takes place.
That may be the case for several of the others, like the 10 in batch.c
On Tue, Oct 21, 2003 at 11:28:11PM -0400, John E. Malmberg wrote:
> jw schultz wrote:
> >
> >Sounds promising.
> >
> >The pitfall you with rsync in threads is that rsync forks
> >with a COW expectation using a great deal of data set prior
> >to the fork. Some of that data is altered. In particula
jw schultz wrote:
Sounds promising.
The pitfall you with rsync in threads is that rsync forks
with a COW expectation using a great deal of data set prior
to the fork. Some of that data is altered. In particular a
slew of global variables that must become thread unique when
modified or things wil
On Mon, Oct 20, 2003 at 12:20:27AM -0400, John E. Malmberg wrote:
> John E. Malmberg wrote:
> >
> >While my testing is far from complete, and I have a few OpenVMS specific
> >things to work out, it appears that the changes to make the client use
> >pthreads were minor, and as of yesterday a clien
John E. Malmberg wrote:
While my testing is far from complete, and I have a few OpenVMS specific
things to work out, it appears that the changes to make the client use
pthreads were minor, and as of yesterday a client on OpenVMS is able to
properly replicate a sample directory of plain text file
jw schultz wrote:
On Sun, Oct 12, 2003 at 12:38:40AM -0400, John E. Malmberg wrote:
I am trying to restart getting rsync to run on OpenVMS, and find a way
around the fork() issue, posibly using POSIX threads.
It occurs to me that i may have been overly encouraging in
my last followup.
Getting rsy
On Tue, 2003-10-14 at 11:01, Donovan Baarda wrote:
> On Mon, 2003-10-13 at 13:00, John E. Malmberg wrote:
> > jw schultz wrote:
> > > On Sun, Oct 12, 2003 at 12:38:40AM -0400, John E. Malmberg wrote:
[...]
> > I have not heard of unison. I have heard that pysync was successful in
> > a limited te
On Mon, 2003-10-13 at 13:00, John E. Malmberg wrote:
> jw schultz wrote:
> > On Sun, Oct 12, 2003 at 12:38:40AM -0400, John E. Malmberg wrote:
[...]
> > I do not know but if OpenVMS support is a problem for rsync
> > proper you might wish to look at pysync or unison which
> > might meet your immedi
On Mon, 2003-10-13 at 13:00, John E. Malmberg wrote:
> jw schultz wrote:
> > On Sun, Oct 12, 2003 at 12:38:40AM -0400, John E. Malmberg wrote:
[...]
> > I do not know but if OpenVMS support is a problem for rsync
> > proper you might wish to look at pysync or unison which
> > might meet your immedi
jw schultz wrote:
On Sun, Oct 12, 2003 at 12:38:40AM -0400, John E. Malmberg wrote:
I am trying to restart getting rsync to run on OpenVMS, and find a way
around the fork() issue, posibly using POSIX threads.
It occurs to me that i may have been overly encouraging in
my last followup.
Getting rsy
On Sun, Oct 12, 2003 at 12:38:40AM -0400, John E. Malmberg wrote:
> I am trying to restart getting rsync to run on OpenVMS, and find a way
> around the fork() issue, posibly using POSIX threads.
It occurs to me that i may have been overly encouraging in
my last followup.
Getting rsync to work us
12 matches
Mail list logo
