On 6/7/06, Darko Miletic <darko@uvcms.com> wrote:
> Eric Tsang wrote:
> > I am having a serious trouble on production subversion with below setting:
> >
> >
> >
> > Windows 2003 Server x64 Std.
> > Apache 2.0.54
> > Subversion 1.2.1 with windows auth.
> > My problem is,
> > The subversion (or maybe apache) just stops responding after several days.
>
> I use subversion a lot and from my experience if you need something that
> works 24 hours 7 days in a week you will need to switch to linux. Apache
> on windows simply can not compare with apache on linux.
Changing server OSes is hardly a trivial task, especially in a large
corporate environment - nor is it a guarantee of a fix (consider the
damage done to the reputations of Apache, Linux, and SVN in his
organization if switching to Linux didn't solve the problem).
Corporations don't just switch their server OS on a whim.
Moreover, this SVN server may do multiple jobs, all requiring Windows.
Making a switch that much harder.
Windows 2003 is a pretty solid OS, and there are lots of people
running Apache on it successfully.
Let's focus instead on helping him get the system he has working properly.
> I recommend you to install Redhat Enterprise 4 or at least CentOS 4.2
> and you will see it working like a charm, and you should at least use
> subversion 1.2.3 because it is the first really good version that is
> fully usable.
Moving up to a known solid SVN release is a smart move - 1.2.1 is
pretty old, 1.2.3 would be good or even 1.3.x. Eric may also want to
look for x64-native builds of Apache & SVN, as they may help reduce
conflicts & weird behavior.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 7 14:45:06 2006