🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.sysadmin
Article #1347

Strange RCS behavior: summary

#1347
From: Kambiz Aghaiepour
Date: Thu, 12 Nov 1992 22:57
58 lines
2870 bytes
Recently I wrote :

> I have a next running 3.0 and I'm experiencing something rather annoying
> with rcs.  Everytime I use /usr/bin/co to check out a file, a background
> process is created as shown by the following output from ps :
> 
> kambiz@parkcity: [ ~ ] $ ps -augxwww | grep kambiz
> kambiz    9647   0.5  1.8 2.47M  432K ?  S     0:02 -bash (bash)
> kambiz    9424   0.0  1.8 2.47M  440K ?  S     0:05 -bash (bash)
> daemon   11176   0.0  0.8 1.52M  208K ?  S     0:00 /usr/lib/rcssnoop co         
> 1.5r   1b   0f   5t 92.11.11.14.16.31c 92.11.11.15.05.03o kambiz  
> Makefile,v
> kambiz   11189   0.0  0.8 1.52M  208K ?  S     0:00 grep kambiz
> 
> What is rcssnoop?????  The thing is that this process stays around just
> long enough to spew into the window where the co command was started the
> following output :
> 
> kambiz@parkcity: [ ~/tmp/testing ] $ RCS logfile /private/adm/rcs.log  
> seems permanently locked.
>                Please alert system administrator
> 
> 
> I also have the most recent dist of rcs by GNU and it doesn't behave  
like
> this.  The funny thing is that this behavior only happens on one  
machine.
> Other 3.0 machines aren't as naughty.
> 
> Has anyone else seen this happen?  Any tips would be appreciated.
> If you would rather e-mail, I will post responses.
> 
> --Kambiz
> 

  I found out what it was.  When you check things in and out using the 
NeXT version of RCS, the ci and co commands will spawn a background 
process (rcssnoop) whose job it is to update the rcslog found in 
/private/lib/rcslog.  In order for to checkout or checkin to not overwrite 
each others entries in the log file, rcssnoop keeps a lock file in the
/tmp directory.  If for some reason this lock file is not deleted, you
get the obnoxious error messages regarding the permanantly locked logfile.
The fix is to go into the /tmp directory and delete the lockfile.  
I don't know what it's called but it's something like rcs-lock or 
something.

What a stinker!!!  

Happy computing.

--Kambiz

-- 
 \o__O   o    Kambiz Aghaiepour           - |  kambiz@oceania.com       o   o
   \_   /|\   Oceania Health Care Systems |\-  netcom!oceania!kambiz   //\ //\
    |\   |\   325 Lytton Ave, Suite 400   | |  FAX:   (415) 322-0142    //  //
   / /   |/   Palo Alto, CA 94301           |  Voice: (415) 322-0127    |\  ||
Technical Details
Message-ID: <BxML40.4FG@oceania.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!know!mips2!news.bbn.com!usc!zaphod.mps.ohio-state.edu!wupost!csus.edu!netcom.com!netcomsv!oceania!kambiz

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!know!mips2!news.bbn.com!usc!zaphod.mps.ohio-state.edu!wupost!csus.edu!netcom.com!netcomsv!oceania!kambiz
From: kambiz@oceania.com (Kambiz Aghaiepour)
Newsgroups: comp.sys.next.sysadmin
Subject: Strange RCS behavior: summary
Message-ID: <BxML40.4FG@oceania.com>
Date: 12 Nov 92 22:57:35 GMT
Sender: kambiz@oceania.com (Kambiz Aghaiepour)
Reply-To: kambiz@oceania.com
Distribution: na
Organization: Oceania Health Care Systems
Lines: 58