[cvsnt] Re: Upgrade to 2.5.03.2260 Questions
Bo Berglund
bo.berglund at telia.com
Wed Apr 26 19:35:27 BST 2006
On Wed, 26 Apr 2006 12:40:52 -0500, RBuchholz at Chamberlain.com wrote:
Incomplete reply below....
>Q4: Must the database/auditing feature be enabled in order to use
>2.5.03.2260? If no, are there any caveats in setting up such an
>installation?
No auditing is not required at all..
>Q5: If it is not used at the start, can I enable the auditing capability
>at some later date?
At least on Windows you can switch it on and off at will via the
control panel and I suspect the same is true in Linux even though
there is no Control Panel application to help out.
>Q6: Is there a procedure documented somewhere on how to get the auditing
>feature running and using it? I am aware of this link:
>http://march-hare.com/cvsnt/features/audit/ and Bo's link at
>http://web.telia.com/~u86216177/CVSNTAuditing.html . Bo's docs are
>primarily for Win and SQLite installations - Is there anything else out
>there?
Actually it is for morew than SQlite:
MSSQLSERVER:
http://web.telia.com/~u86216177/CVSNTAuditing.html#SQLServer
ODBC to anything:
http://web.telia.com/~u86216177/CVSNTAuditing.html#ODBC
>Q11: Does a cvs init command need to be run on the repositories in order
>to "update" anything? If this command is needed, and it is executed, does
>this prevent going back to 2.0.58d if necessary?
In fact you CANNOT run a cvs init on a repository that has already
been initialized. I have asked about a command to in a friendly way
add the new admin files to a repository CVSROOT when I have done a
server update. But so far the only advice is to init a dummy repo
after the server update and then copy all of the files from that
CVSROOT on top of the old CVSROOT while making sure to *NOT OVERWRITE*
existing files by the same name!
>
HTH
/Bo
(Bo Berglund, developer in Sweden)
More information about the cvsnt
mailing list