RE: How to lock a file and don't allow multiple people to modify it at the same time.

[Andy Baker]

Don't use CVS?

-----Original Message-----
From: Rabbit Xu [mailto:address@hidden
Sent: 24 May 2002 02:04
To: address@hidden
Subject: How to lock a file and don't allow multiple people to modify it
at the same time.


Hello all:
   Becase I don't allow multiple people to modify at the same time.  I want
to lock a file when anyone checkout this file and want to modify it.
   How to do?

Thank you.


----- Original Message -----
From: "Norberto Meijome" <address@hidden>
Cc: <address@hidden>
Sent: Friday, May 24, 2002 8:25 AM
Subject: Re: Disabling TELNET access disables login to CVS


> Hi,
> does any other service hanging off xinetd work at all ? maybe xinetd's
> configuration is so badly broken that it cannot restart. Check the
> messages in /var/log/messages.
>
> As Matt R., my CVS box also runs CVS on 2401, no telnet but SSH. Not
> really a CVS problem.
> cheers,
> Beto
>
> N Garry wrote:
>
> > If I disable the TELNET access to my Linux (Red Hat 7.2) machine
> > running CVS 1.11 (using pserver authentication), my users are not able
> > to login to CVS.
> > Haven't been able to figure out how to reslove this.
> > Any solutions?
>
>
> >
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at
> > http://explorer.msn.com/intl.asp.
>
> no, thanks, NS 7 is a lot nicer. ;-)
>
> --
> Norberto Meijome
> If you were supposed to understand it, we wouldn't call it 'code'.
>
>
>
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs



_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs



NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.