Re: Problem sharing apt cache through NFS

On Tue, 2004-07-20 at 15:05, Andre Costa wrote:
> On Tue, 20 Jul 2004 14:53:46 +0300
> Panu Matilainen <[email protected]> wrote:
> 
> > > Yeah, I thought about it, too. Apparently, it is running; if I run this
> > > on the server:
> > > 
> > > service nfslock status
> > > 
> > > it returns:
> > > 
> > > rpc.statd (pid 9015) is running...
> > > 
> > > Anything else I should check?
> > 
> > Mm.. just realized you'll need to be running the nfslock service on all
> > the clients as well - IIRC (been a while since I last encountered nfs
> > locking :). 
> 
> Yeah, NFS is a beast, isn't it? ;)

Yeah :(

> 
> Unfortunately, rpc.statd is running on the client as well... =(
> 
> The weird thing is that this setup has been working, but something broke
> it. I am just trying to understand _what_ broke it =/

Hmm, now that I actually tried this myself:
- first I didn't have nfslock running at all and it worked just fine,
only giving a warning "W: Not using locking for nfs mounted lock file
/var/cache/apt/archives/lock" at the end of operation.
- once nfslock got started on both .. well, it "just worked"
- if the directory is actually locked then you should get "resource
temporarily unavailable" instead of "permission denied"

I'd guess this is just one of those nfs quirks.. a "stale lock" or
something like that :-/ How to clear the situation .. well, dunno
really. Maybe recycle the rpc.statd processes on all hosts or something?

	- Panu -