Re: Bug#149491: dpkg depends hard on working F_SETLK fcntl
On Mon, Jun 10, 2002 at 06:43:57PM +0200, Wichert Akkerman wrote:
> Are you running rpc.statd on the client?
That makes locking work. Thank you very much.
statd and lockd aren't on woody_netinst-20020416-powerpc.iso.
Will they be on the stable woody installation CD?
Maybe they should because the installer expressly supports
installation to an NFS root.
They'll also have to be in basedebs.tar, so that dpkg
can run after the second boot. (I just downloaded
basedebs.tar from ftp.de.debian.org. They're missing.)
Let me restate the argument I've got left for my case:
Some users may want to use an NFS server with broken locking
when they don't have enough control over it to fix it.
Reserving one directory name for the lockfile only would make
that easy (a tiny local filesystem can be mounted there, a ramdisk
for example), and it would leave dpkg essentially unchanged
(just "/var/lib/dpkg/lock-dir/lock" or similar
instead of "/var/lib/dpkg/lock").
--
To UNSUBSCRIBE, email to debian-dpkg-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: