Hello cvsusers,
First: I currently have 4+ years old Dell PE2300 PII 400MHZ. It is our cvs
server. Now we want to upgrade this server to newer Dell Systems with P4
3.2GHZ.
Second: Will be no changes on server name and its repository.
Now I just need your help or opinions on how to approaching ab
Courier [mailto:[EMAIL PROTECTED] wrote:
> Here is I would like to do: I will take currently cvs server off line,
> then tar the whole Repository, then bring up a new system and
> cp and untar
> Repository on new server. Our cvs server is a stand alone
> server. All my
> users are accessing via p
Jim,
Thank you. That is what I have in mind. Good things about our cvs server
is locally. Thus I have schedule for down time about and works with
couple developers when new cvs server back on line for testing and double
check very things are ok.
Again thank you very much for your comments.
C-
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, February 02, 2004 3:00 PM
Subject: RE: CVS server upgrade?
> Courier [mailto:[EMAIL PROTECTED] wrote:
> > Here is I would like to do: I will take currently cvs server off line,
> > then tar the whole Repository,
Hello,
* On Mon, Feb 02, 2004 at 03:00:35PM -0500 Jim.Hyslop wrote:
> In order to minimize the impact on the users, we took the original server
> off-line just long enough to create the tarball. As soon as the tar was
> complete, we restarted the server in read-only mode (create an empty
> CVSRO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Spiro Trikaliotis <[EMAIL PROTECTED]> writes:
> Hello,
>
> * On Mon, Feb 02, 2004 at 03:00:35PM -0500 Jim.Hyslop wrote:
>
> > In order to minimize the impact on the users, we took the original server
> > off-line just long enough to create the tarb
David R. Chase [mailto:[EMAIL PROTECTED] wrote:
> Just wondering what minor problems you had, just in case they
> might pertain
> to other peoples' migration strategies (or my own someday)?
Well, our situation was much more complex than "Courier's". Not only did we
upgrade the server hardware, we
Spiro Trikaliotis [mailto:[EMAIL PROTECTED] wrote:
> not that I would recommend it, but:
>
> But about
>
> 1. Taking the CVS repository offline
> 2. Create the tarball
> 3. Take the CVS repository online with full access (!)
> 4. do anything needed to move to the new server
> 5. When everything i
Well, I would like to extended my thanks to:
Jim Hyslop, Mark D. Baushke and David R. Chase. I am appreciate that you
guys take time to respond.
1. I will setting up a newer server with the same name and the same
/Repository file system as the old one.
2. Notify to all my users that CVS server wi
Hello Jim,
* On Tue, Feb 03, 2004 at 09:28:59AM -0500 Jim.Hyslop wrote:
> Spiro Trikaliotis [mailto:[EMAIL PROTECTED] wrote:
> > not that I would recommend it, but:
[...]
> > Would this make sense, or could 6. break something that was made with
> > 4.?
> That would work, as long as nobody checked
Courier writes:
>
> 3. Then take old server off line, then tar its Repository.
> 4. Connecting these two server by Crossover CAT5 for cp and untar new
> Repository.
You minimize the downtime by connecting the two machines first then
running the two tars in parallel through a remote shell:
Hello everyone,
I am reasonably new to CVS and am looking for some tips/handy hints for upgrading the CVS server. can anybody give me any help or advice please ?
my OS is :
SunOS xultra1 5.8 Generic_108528-15 sun4u sparc SUNW,Ultra-2System = SunOS
Node = xultra1
Release = 5.8
Thanks in adv
Download the latest source, unpack it, cd into the directory:
./configure
make
su
make install
(Some systems allow sudo make install)
HTH
Alex
Am 10.06.2004 um 12:16 schrieb mark hanna:
Hello everyone,
I am reasonably new to CVS and am looking for some tips/handy hints
for upgrading the CVS serv
Alex v.Below writes:
>
> Download the latest source, unpack it, cd into the directory:
>
> ./configure
> make
> su
> make install
cvs init
It hasn't been strictly required so far, but it's a good idea. It gives
the new CVS a chance to update the existing repository should the format
change, ad
14 matches
Mail list logo
