Stale lock files with "anonymous" CVS

2003-10-13 Thread David Wood
We have a CVS repository here where some users have read only access except in a few directories, and the rest have read-write access everywhere. This does work as advertised, except that when a read-only user attempts to put a file where they shouldn't, we end up with a stale lock. Then no on

Re: Stale lock files with "anonymous" CVS

2003-10-13 Thread Larry Jones
David Wood writes: > > This does work as advertised, except that when a read-only user attempts > to put a file where they shouldn't, we end up with a stale lock. Then no > one can use the repository until it's manually removed. Are you accessing the repository using client/server mode, or loca

Re: Stale lock files with "anonymous" CVS

2003-10-13 Thread David Wood
Accessing with pserver. Server is 1.11.7. Client is WinCVS version 1.3.13.1 (Beta 13 Build 1). Both are on Solaris 9. And this is the only problem I've found with this setup. [EMAIL PROTECTED] (Larry Jones) wrote on 10/13/2003 11:49:37 AM: > David Wood writes: > > > > This does work as adverti

Re: Stale lock files with "anonymous" CVS

2003-10-13 Thread Larry Jones
David Wood writes: > > This does work as advertised, except that when a read-only user attempts > to put a file where they shouldn't, we end up with a stale lock. Then no > one can use the repository until it's manually removed. What versions of CVS? -Larry Jones Sometimes I think the surest

RE: Stale lock files with "anonymous" CVS

2003-10-13 Thread Andy Baker
Title: RE: Stale lock files with "anonymous" CVS FYI I've also started seeing some strange "signal 11" errors to do with lock files since 1.11.7 (same in .8 and .9). Yet to get to the bottom of it. I'll let you know when I have something more specific. NOT

RE: Stale lock files with "anonymous" CVS

2003-10-13 Thread Andy Baker
Damn. I'll try doing it in plain text next time. 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 re