Nidhi, Hi. It does'nt seems that this is linked to perm settings to the cvs binary files. This is related to the perm settings you have applied to the repository only!! You need to check on that tracks.
As using the passwd and the pserver authentication protocol method- the cvs_login should be mapped fine with its sys_user in the passwd file and that sy_user is a member of the group_owner of the repository you are maintaining. Regards, Gurpreet S -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Malhotra, Neti Sent: Tuesday, October 05, 2004 9:53 PM To: Cvs Mailing List (E-mail) Subject: Looking for Help with CVS 1.11.17 Fellow CVS Users, I am attempting to upgrade cvs on my Solaris server from cvs 1.10 to cvs 1.11.17. The build was successful, and I am able to use cvs from that server without a problem. Unfortunately, if I try to connect to the server from my PC using a pserver connection in WinCVS, I am unable to perform a cvs login. The error I am getting is: cvs [login aborted]: setgid failed: Not owner I have noticed in the source code that when trying to authenticate a pserver connection, it is trying to switch users to the cvs user requesting the login. My concern is that if I change ownership/permission of the cvs executable on the server so that it is run as root (which will allow the swith in user) that this may cause problems for users trying to access cvs from the server directly. I do not see the "switch user" happening if you are not using a pserver connection. Does anyone have any ideas/guidance on how to tackle this problem? Thank you very much for your help - Neti _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
