On 5 Dec 2001 at 1:16, rahul parkhi wrote: > the config file by using checkout..yesterday i edited > the file directly on server..but it should not be a
It's not recommended practice by CVS developers. If they decide to put admin files under RCS you can not deploy those changes. Besides committing them makes sure that CVS doesn't get confused in between. If you directly edit them in place, CVS may not know about it and can result weird results for ongoing transactions. Like a good kid, I follow what they recommend. I really can't care less why they say so as long as it works as I want. > problem how u edit the administrative files..? Can u > please tell me what was the problem..& why lock files > can not be in the repository itself( as if u don't > specify the LockDir para. in the config file,the lock > files are created in the repo.) Many a time when strict access control is placed on repository, direct access to repository is eliminated using unix file permissions. Especially write access. In that case lock directory poses a problem. It's always a better idea not to give away write access. You should also set the OS user for cvspserver and make all transactions remote. So that a permission of 700 for user cvs should suffice for repository dir. Everything else is controlled by cvs admin. files. Of course CVS can't olve all the problems regarding repository but it's the best general solution. Shridhar _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
