Re: Problem sharing apt cache through NFS

On Tue, 20 Jul 2004 16:13:57 +0300
Panu Matilainen <[email protected]> wrote:

> On Tue, 2004-07-20 at 16:12, Andre Costa wrote:
> > On Tue, 20 Jul 2004 15:57:06 +0300
> > Panu Matilainen <[email protected]> wrote:
> > 
> > > You can't separate the lockfile without patching apt, and even if
> > > you move the lockfile someplace else .. it doesn't make much sense
> > > to have local lockfiles since the locking will be messed up
> > > anyway.
> > 
> > Thks, I thought so -- it would cause more evil than good...
> > 
> > > As a last resort/temporary workaround you could run apt with
> > > 'Debug::NoLocking=true" to completely avoid locking the archive
> > > directory but that might cause some "interesting" effects if two
> > > hosts are trying to simultaneously download the same file :)
> > 
> > Thks, that worked =) Yeah, I understand this would lead to weird
> > things, but I guess this is manageable -- updates are only performed
> > manually on the clients, so it won't be hard to avoid any upgrades
> > being done on the "master" server.
> 
> Ok since the updates are done manually it should be quite safe to do
> that.
> 
> > 
> > I don't intend to do this (I want this to be really a _temporary_
> > workaround), but, just to improve my apt management skills, how
> > would I put it on/etc/apt/apt.conf? Would it be
> > 
> > Debug {
> > 	NoLocking "true";
> > };
> > 
> > at the top level?
> 
> Yeah, that or
> Debug::NoLocking "true";
> 
> Both accomplish the same thing, the Foo { Bar "xxx"; }; format is
> really only beneficial when you need to set more than one Foo-option.

Thks a lot, Panu, you were really helpful. It really bothers me not
understanding what's causing NFS to be a hindrance, but, as I said, this
is OT for this list. I will get back to this to try to understand what
happened, and if I get somewhere, I will post back here my findings.

Best,

Andre

-- 
Andre Oliveira da Costa
([email protected])