[Top][All Lists]

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

Re: Next Steps: CVS Import Bug - Please Respond

From: Todd Denniston
Subject: Re: Next Steps: CVS Import Bug - Please Respond
Date: Wed, 10 Aug 2005 08:42:42 -0500

"Oproescu Bogdan (KTXA 3)" wrote:
>    Hello Bernd,
>    Thanks for your message below. Here are my answers to your questions:
>    1. The failures seem to move around at random, but the pattern seems
>    always to be large .jar files, causing time overlap between 2 or more
>    parallel CVS Clients into the SAME Module and Repository pair on our
>    CVS Central Server. Same is true for the import-tag pair on 2 or more
>    parallel CVS Clients, but I think this is another manifestation of the
>    first problem, namely that the "cvs import" is not atomic, so 2 or more
>    parallel CVS Clients will produce this issue, over and over again.
>    2. Our CVS Central Server is Unix Solaris 8.0:
> cvsadmin@su64sr20% uname -i -m -p -r -s -v
> SunOS 5.8 Generic_117350-02 sun4u sparc SUNW,Sun-Fire-480R
> cvsadmin@su64sr20%
Sorry for replying to the other message before reading this one...

Along the lines of the information from my previous email, you should be
aware that, at least with the sun machines I have used:
 solaris shares (at least part of) its tmp directory space with its virtual
memory space,
 and you may need to mod my previous limits to:
2) the source or ,v file reaches ~1/4 or ~1/6 the size of your server's temp
partition's limit.
3) the source or ,v file reaches ~1/2 the full Virtual Memory size of the
server, i.e., ~1/2 of real ram + ~1/4 of swap space.
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

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