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 > CVSROOT/writers file to make the whole repository read-only). Thus, people > could still check out and browse the repository, but they couldn't check > anything in (and thus throw the two repositories out of sync).
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 is working fine, take the (original) repository offline again 6. Now perform an rsync between the two repositories 7. Take the new one online (with changing DNS entries and the like). Would this make sense, or could 6. break something that was made with 4.? I understand that this procedure seems more "risky", but it seems to me that this should work, too, shouldn't it? Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
