[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: doc on establishing pserver ...

From: Matthew Von-Maszewski
Subject: RE: doc on establishing pserver ...
Date: Thu, 28 Jun 2001 20:12:57 -0400

... uh, I suspect I just have the wrong expectations.  Someone else did the
CVS magic last two times I worked with it.  I am now trying to do it for my
personal stuff.  My expectations for CVS's setup are based upon how I worked
with perforce.

My goal is to edit stuff on the Windows box and have it automagically sync
to the web server (linux).  This satisfies my lust for backups, revisions,
and remote edits ... and general power trip of doing the way I want it done
since I used to control this stuff at a larger company ... a.k.a being a
nerd with a bug up his butt ...

Thanks for the info, I now have a better grip on what the manual is trying
to tell me.

-----Original Message-----
From: Jonathan M. Gilligan [mailto:address@hidden
Sent: Thursday, June 28, 2001 6:45 PM
To: Matthew Von-Maszewski
Cc: address@hidden
Subject: Re: doc on establishing pserver ...

cvs is designed to leak memory like a sieve and to exit from the middle of
deeply nested function calls. To make it a persistent process would require
a rewrite from the ground up.

Tony Hoyle established a "better cvs" project on SourceForge
( to attempt to do just that (rewrite
the code cleanly without redesigning the fundamentals), but the project is
dormant at the moment. Carrying that off would probably be the first step
towards being able to rewrite cvs as a daemon.

What you probably would like to do is to have a daemon running that calls
cvs when requested to by a client, but isn't that just the same as what
inetd does?

Also, why run as a daemon? Is your server really creaking under the load of
people checking code in and out?

Just my simple-minded understanding of things. If I'm wrong or just plain
ignorant, sorry for wasting time.

At 03:40 PM 6/28/01, Matthew Von-Maszewski wrote:
>Ok, I stupid.  Would someone be so kind as to tell me where the information
>exists for establishing cvs as a daemon, not inetd?  If it is in the html
>manual, I apologies for being blind (and stupid).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]