[Top][All Lists]

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

Re: RCI (co -l)

From: Bob Proulx
Subject: Re: RCI (co -l)
Date: Thu, 14 Sep 2006 07:15:38 -0600
User-agent: Mutt/1.5.9i

Mike Galvin wrote:
> We would like to see who has locked the file if it is already 
> checked out.

The rlog command will print out who has a file locked.

  co -l foo
  rlog foo
  locks: strict
        bob: 1.1

> As I understand, the command already does this with -l...our problem
> is that we have restricted the use of co and ci to a superuser
> function, to prevent accidental deletion, and co stores the
> superuser Id instead of the developers user Id.

How does restricting ci and co to the superuser prevent accidental

> Is there a way that we can retrieve the developers original user ID for 
> the co command?

Not that I know of.  By the time it is stored in the ,v file it is too

At co time rcs will check for LOGNAME and USER in that order as
overrides to the current user name and will store the value determined
as the locker.  If you are using sudo then setting LOGNAME=$SUDO_USER
before invoking co and ci should store the original user as the locker.


reply via email to

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