Re: [cvsnt] Migrate CVSNT
> > Is there a procedure to migrate the CVSNT software from one dying MS2003 > server to another? > > I think what you are asking is to install a fresh cvsnt on the new server, then just copy the repository over (using cwrsync or xcopy /v), then point the new cvsnt at the repository, no? Steve ___ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
Re: [cvsnt] Migrate CVSNT
It was a mistake, I received an error when I sent the original one. I apologize, forgive me for the poor etiquette. It there is a way to remove I will. "Bo Berglund" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On Fri, 21 Nov 2008 10:56:43 -0600, "Bryan" <[EMAIL PROTECTED]> > wrote: > >>Is there a procedure to migrate the CVSNT software from one dying MS2003 >>server to another? >> > Why did you post the exact same question in another thread? > This is not appropriate. > > -- > > /Bo > (Bo Berglund, developer in Sweden) ___ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
Re: [cvsnt] Migrate CVSNT from one server to another
On Fri, 21 Nov 2008 11:55:22 -0600, "Bryan" <[EMAIL PROTECTED]> wrote: >"Bo Berglund" <[EMAIL PROTECTED]> wrote in message >news:[EMAIL PROTECTED] >> On Fri, 21 Nov 2008 10:05:01 -0600, "Bryan" <[EMAIL PROTECTED]> >> wrote: >> >>>Does anyone have a process to migrate the CVSNT application from one dying >>>MS 2003 server to another 2003 server. >>> >>>Much appreciated. >>> >> >> How about: >> - Arrange the disks the same way on the new server as on the old one >> - Install CVSNT on the new server, then stop the CVSNT service. >> - Install other software that you know you use with CVSNT (like >> CVSMailer for example) to the same locations as on the old server. >> - Stop the CVSNT service on the dying server >> - Copy the repositories from old to new server over the network to the >> same locations on the new as on the old server >> - Export the registry settings for CVSNT on the old PC to a reg file >> - Import the registry settings on the new server via the reg file >> - Now disconnect the old server from the network >> - Then rename the new server to the same name as the old one (restart >> needed) >> - Make sure CVSNT service is started >> >> - Make tests from clients that they have a connection like they used >> to. >> >> Done. >> >> What this does is replicating the repository into the same structure >> as on the old one, which makes the CVSNT settings work also on the new >> server when you import them via the reg file. This way the new server >> will use the same conbfiguration as the old server. >> >> And by installing support software like CVSMailer to the same location >> on the new server as on the old you make sure that the scripts in >> CVSROOT will still run as before. >> >> Finally by renaming the server to the old name the clients will not >> notice any difference, their sandboxes will continue to work. >> >> Note that you need to shut down the old CVSNT service (and never bring >> it up again) before copying the repository files so that there will >> not be an intermediate commit or other action in the repository while >> you migrate. >> >Changing the name of the server is not an option. How much do that change >the procedure? > If you cannot change the server name then you can modify the DNS settings of your network so that the old server name is kept but pointing to the same IP address as the new server. The reason for this exercise is to keep all of the developer's sandboxes functional against the new server. Ideally they should not have to do anything to keep their workflow, just observe the downtime during migration. Next possibility is to have every developer with checked out files modify his %systemroot%\system32\drivers\etc\hosts file and add an entry with the old server's name and the new server's IP address. This masquerades the new server as the old as seen from the clients. If also this is not possible then every single developer will have to go over his checked out file sets (sandbox) and either delete them and check out fresh from the new server or alternatively run a macro or similar to modify every single Root file throughout his data to reflect the new server name. The WinCvs front-end has such a macro that can be activated on a directory level and works recursively down It all boils down to convenience of the users. If you are the only user then the trick to change the Root file contents is possibly the best bet. -- /Bo (Bo Berglund, developer in Sweden) ___ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
Re: [cvsnt] Migrate CVSNT
On Fri, 21 Nov 2008 10:56:43 -0600, "Bryan" <[EMAIL PROTECTED]> wrote: >Is there a procedure to migrate the CVSNT software from one dying MS2003 >server to another? > Why did you post the exact same question in another thread? This is not appropriate. -- /Bo (Bo Berglund, developer in Sweden) ___ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
Re: [cvsnt] Connection issues to new server
Additional info. I did try the command forcing port 2403, just as a test. I did get an appropriate error so I think the port is correctly open. connect to 199.2.222.222:2403 failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Thanks, Rick ___ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
[cvsnt] Connection issues to new server
Hi gang, It's been awhile. I am having connections issues to a new cvsnt server. Client: Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2382 (client/server) Server: Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2382 (client/server) I originally configured SSPI only. I am connecting to this server (Windows Server 2003) via Terminal Services. I can successfully check out CVSROOT to a sandbox on the server itself using SSPI. I had the IT admin open port 2401 to the Internet. I cannot connect remotely to the server via SSPI. I have made an entry in the Managed Passwords user control panel for the server which is what I've had to do in the past. trace: 09:58:08: -> Tracelevel set to 3. PID is 4192 09:58:08: -> Session ID is 10604926f6b06248 09:58:08: -> Session time is Fri Nov 21 17:58:08 2008 09:58:08: -> Loading protocol sspi as sspi.dll 09:58:08: -> CLibraryAccess::Load loading C:\PROGRA~1\CVSNT/protocols/sspi.dll 09:58:08: -> main loop with CVSROOT=:sspi:[EMAIL PROTECTED]:/CVSHOME The rick.martin account is an admin on the CVSNT server box. I decided to enable pserver for testing and setup a testuser mapped to the rick.martin account. I set SystemAuth=No in the config. I've never used pserver before on one of my servers so please forgive any stupidity. When I try to log in either running on the server itself or remotely I get this trace: 09:46:14: -> Tracelevel set to 3. PID is 6068 09:46:14: -> Session ID is 17b44926f3e6592c 09:46:14: -> Session time is Fri Nov 21 17:46:14 2008 09:46:14: -> Loading protocol pserver as pserver.dll 09:46:14: -> CLibraryAccess::Load loading C:\PROGRA~1\CVSNT/protocols/pserver.dll 09:46:14: -> main loop with CVSROOT=:pserver:[EMAIL PROTECTED]:/CVSHOME 09:46:14: -> wrap_add(*.a -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.avi -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.bin -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.bmp -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.bz2 -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.chm -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.class -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.dll -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.doc -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.dvi -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.exe -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.gif -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.gz -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.hqx -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.ico -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.ilk -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.iso -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.lib -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.jar -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.jpg -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.jpeg -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.lnk -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.mpg -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.mpeg -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.mov -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.mp3 -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.ncb -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.o -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.ogg -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.obj -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.pdb -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.pdf -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.png -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.ppt -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.res -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.rpm -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.sit -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.so -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.tar -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.tga -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.tgz -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.tif -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.tiff -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.wav -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.wmv -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.xls -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.zip -kb, 0, 0, 0, 0) 09:46:14: -> wrap_add(*.Z -kb, 0, 0, 0, 0) Logging in to :pserver:[EMAIL PROTECTED]:2401:/CVSHOME cvs [login aborted]: Error reading from server 199.2.222.222: -1: Unknown error Can anyone point me in the right direction? TIA, Rick Martin ___ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
Re: [cvsnt] Migrate CVSNT from one server to another
Changing the name of the server is not an option. How much do that change the procedure? "Bo Berglund" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On Fri, 21 Nov 2008 10:05:01 -0600, "Bryan" <[EMAIL PROTECTED]> > wrote: > >>Does anyone have a process to migrate the CVSNT application from one dying >>MS 2003 server to another 2003 server. >> >>Much appreciated. >> > > How about: > - Arrange the disks the same way on the new server as on the old one > - Install CVSNT on the new server, then stop the CVSNT service. > - Install other software that you know you use with CVSNT (like > CVSMailer for example) to the same locations as on the old server. > - Stop the CVSNT service on the dying server > - Copy the repositories from old to new server over the network to the > same locations on the new as on the old server > - Export the registry settings for CVSNT on the old PC to a reg file > - Import the registry settings on the new server via the reg file > - Now disconnect the old server from the network > - Then rename the new server to the same name as the old one (restart > needed) > - Make sure CVSNT service is started > > - Make tests from clients that they have a connection like they used > to. > > Done. > > What this does is replicating the repository into the same structure > as on the old one, which makes the CVSNT settings work also on the new > server when you import them via the reg file. This way the new server > will use the same conbfiguration as the old server. > > And by installing support software like CVSMailer to the same location > on the new server as on the old you make sure that the scripts in > CVSROOT will still run as before. > > Finally by renaming the server to the old name the clients will not > notice any difference, their sandboxes will continue to work. > > Note that you need to shut down the old CVSNT service (and never bring > it up again) before copying the repository files so that there will > not be an intermediate commit or other action in the repository while > you migrate. > > -- > > /Bo > (Bo Berglund, developer in Sweden) ___ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
Re: [cvsnt] Migrate CVSNT from one server to another
On Fri, 21 Nov 2008 10:05:01 -0600, "Bryan" <[EMAIL PROTECTED]> wrote: >Does anyone have a process to migrate the CVSNT application from one dying >MS 2003 server to another 2003 server. > >Much appreciated. > How about: - Arrange the disks the same way on the new server as on the old one - Install CVSNT on the new server, then stop the CVSNT service. - Install other software that you know you use with CVSNT (like CVSMailer for example) to the same locations as on the old server. - Stop the CVSNT service on the dying server - Copy the repositories from old to new server over the network to the same locations on the new as on the old server - Export the registry settings for CVSNT on the old PC to a reg file - Import the registry settings on the new server via the reg file - Now disconnect the old server from the network - Then rename the new server to the same name as the old one (restart needed) - Make sure CVSNT service is started - Make tests from clients that they have a connection like they used to. Done. What this does is replicating the repository into the same structure as on the old one, which makes the CVSNT settings work also on the new server when you import them via the reg file. This way the new server will use the same conbfiguration as the old server. And by installing support software like CVSMailer to the same location on the new server as on the old you make sure that the scripts in CVSROOT will still run as before. Finally by renaming the server to the old name the clients will not notice any difference, their sandboxes will continue to work. Note that you need to shut down the old CVSNT service (and never bring it up again) before copying the repository files so that there will not be an intermediate commit or other action in the repository while you migrate. -- /Bo (Bo Berglund, developer in Sweden) ___ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
[cvsnt] Migrate CVSNT
Is there a procedure to migrate the CVSNT software from one dying MS2003 server to another? ___ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
[cvsnt] Migrate CVSNT from one server to another
Does anyone have a process to migrate the CVSNT application from one dying MS 2003 server to another 2003 server. Much appreciated. ___ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
Re: [cvsnt] March-Hare message into my commit messages
Luigi, With EVS almost done now I finally had time to reply to the last points you made. > > Taking the analogy a step further: Luigi (and others) appear to be > > suggesting > > Not at all. You choose the Open Source model, not us. It is perfectly valid under the GPL open source license to both charge a fee for the distribution of the software and also to advertise within it. Tony and I have both recently posted to this thread indicating we are perfectly happy with the open source model. Are you sure you understand what the open SOURCE model is? > Budget constraint does not allow us to buy whatever we like > just to "support good development". No - but we the developers can encourage you the user to support the tools that may be a critical part of your infrastructure. You cannot 'buy' CVSNT, but you can 'pay' for it (in various ways) - it's one of the geatest freedoms that the GPL gives people. > Again, I am telling you how some customers perceive your > package. And that is appreciated. Comments from other people in this thread about the considerable value of CVS Suite are also appreciated. > be forced somehow to buy a CVS suite, We are not forcing anyone. The software is open source - you have the source code, we have also provided ways to turn off the advertising (see FAQ). > prices, and at 4000 euro per ten users your competitors are At current exchance rates it's less than 2400 Euro (once you provide a VAT Number) and is the cheapest commercial SCM on the market (when priced over 3 years) and includes 2 hour Service Level Agreement on the telephone support (by far the best SLA for any product costing less than EUR5000 per user plus 15% maintenance). However we deliberately did not advertise 'CVS Pro' since Sales of 'CVS Pro' are already quite healthy (we expect a smaller percentage of users will find value in CVS Pro). We are advertising CVS Suite and deliberately targeting a minimum of sales target of: 1 x 1 copy per 100 downloads. Based on feedback in this thread alone a higher number of those who are downloading CVSNT will find considerable value in 1 copy of Suite. A further percentage of users have been using CVSNT for years and have not responded to previous calls for users to become contributors and whilst they may not find Suite 'more valuable' than the FOSS offering they will find it less annoying and appreciate the continued development and FOSS support. > Would you like some support/investment? Set up a way to > "donate to the project", as many OS project do. It is not possible for an individual or company to collect donations. Donations are heavily regulated by governments. If you want to contribute - buy a copy of a product we have for sale. > You're using Apache/PHP/Debian on your cvsnt.com server. > Would you like if it printed "Page generated with a free > version of Apache Web Server with a free version of PHP > on a free version of Debian operating system" on each > page it serves? I wouldn't mind at all - cvsnt.org is a free web site. All the stable downloads require a user visit the march-hare.com web site which runs on a Microsfot Web server running IIS. Regardless of the fact we wouldn't mind such a message - we pay (actual hard cash) for the hosting of those web sites and we trust that the companies we are paying are in turn paying their vendors (or contributing in direct tangible ways to the development of FOSS software). > Why don't you pay for RedHat or SuSE to support Linux > development? We do - we have these systems internally - along with Windows and HPUX and Solaris and Mac systems all of which we need to pay actual hard cash for (except notably HP who have generously provided us with free hardware and software). > > Or switch off the message (read the FAQ) > > None of the methods works yet They do in my tests - if you are running server and client you need to turn the message off on the server and the client but the FAQ already informs people of that. I was just using CVSNT 2.5.04 yesterday and there are no advertisments in my commit messages. > As explained in a previous message, we don't have any SQL > Server database nor we plan to have one. And as I have written previously - why not contribute to the EVSCM project and instead of telling the group what you wont use, ie: tell the project what you will use. We have many ideas what the next database is that we'll support (Oracle, Postgres, Sybase) and platform (Solaris 10 Sparc, Solaris 10 Intel, HPUX 11iv3 Itanium, SLES10 x32, SLES10 x64, RHEL5 x32, RHEL5 x64, RHEL Itanium) - and in the absence of any constructive replies we'll make an uninformed choice. Post to the evs newsgroup not the cvsnt newsgroup. Users of Free Software (like CVSNT) have a choice. To financially support the companies who are enhancing Free software (like CVSNT) and not limiting your freedoms by continuing to supply all the source code under the GPL (ie: the work Tony and March Ha
