[Top][All Lists]

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

Re: Odd error with DOS use of RCS

From: Aaron S. Hawley
Subject: Re: Odd error with DOS use of RCS
Date: Tue, 10 Jun 2003 16:00:31 -0400 (EDT)

quoting from: man rcs(1)

          A catastrophe (e.g. a system crash) can cause RCS to leave
          behind a semaphore file that causes later invocations of RCS
          to claim that the RCS file is in use.  To fix this, remove
          the semaphore file.  A semaphore file's name typically
          begins with , or ends with _.
" is the roxen challenger website

On Tue, 10 Jun 2003, Josh Ellyson wrote:

> Hello,
> We are using the DOS binaries from the site for a few of our
> Windows users. I have created a couple of custom action buttons in
> Homesite that allows them to do simple co -l and ci -u on an open file.
> I have two users that despite have identical ENV settings as the rest,
> consistently get a co error. Basically it reads that they do not have
> permission to open co the file, but then it creates a file in the RCS
> directory of the form ",$FILENAME,".
> Thus far my search on this phenomenon has yielded no answers.
> Might you have some ideas.
> sincerely,
> josh ellyson

reply via email to

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