[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: always read-write: how? ...newbie

From: vvor
Subject: RE: always read-write: how? ...newbie
Date: Mon, 11 Mar 2002 21:42:46 -0500

We've had this option UN-checked forever. That didn't cause this!

We have /cvs as the top of the tree.

/cvs/CVSROOT is the repository.

/cvs/CVSROOT/$module_names is where all the modules are.

When co-ing, either from cmdline or wincvs, over pserver, the files are
checked out read-only. CVSREAD is NOT set at all. There are no ./cvsrc files
anywhere. I've looked thru all the admin files and I cannot find anything
that might be causing this, but I may be missing something obvious to
someone experienced.

We have a group "users" within which belong all the users. These are system
accounts only, and authentication is functioning.

Permissions are:

user            r w x
group   r w s
others  r - x

Umask appears to be 022.

When I co via telnet, the files are checked out read-write.

I don't know how to tell if there a watch or a lock that is doing this.


> -----Original Message-----
> From: address@hidden [mailto:address@hidden Behalf Of
> Datla, Raghav
> Sent: Monday, March 11, 2002 1:08 PM
> To: 'address@hidden'; address@hidden
> Subject: RE: always read-write: how? ...newbie
> In WinCvs, by default the option checkout ready-only is checked. You can
> uncheck it by going to Admin menu, then to preferences and then go to
> Globals tab. There uncheck the first option.
> Thanks,
> -Raghav
> -----Original Message-----
> From: address@hidden [mailto:address@hidden
> Sent: Monday, March 11, 2002 11:39 AM
> To: address@hidden
> Subject: Re: always read-write: how? ...newbie
> vvor writes:
> >
> > however, when any user checks out using pserver, files are
> always checked
> > out readonly. so users have to edit each file. when that file is
> committed,
> > it becomes read-only. but when the same user telnets in and does a co in
> > their remote /home, the files are rw. something to do with pserver?
> No, probably something set wrong in WinCVS.  It's the *client* that
> determines the permissions on the working files, not the server.
> -Larry Jones
> They say winning isn't everything, and I've decided
> to take their word for it. -- Calvin
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]