Date: Mon, 25 Dec 2006 13:40:26 +0100 From: Robert Joosten <robert@ml.erje.net> To: freebsd-stable@freebsd.org Cc: Mark Linimon <linimon@lonesome.com> Subject: Re: Possibility for FreeBSD 4.11 Extended Support Message-ID: <20061225124026.GA709@iphouse.com> In-Reply-To: <20061224193142.GA14696@soaustin.net> References: <20061223125916.GA30648@soaustin.net> <20061224180950.GA791@iphouse.com> <20061224193142.GA14696@soaustin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > >From my understanding, rpc.lockd needs substantial work from a fairly > experienced developer, to the point where IIRC we are not in a position > to hold up any releases because of it. Someone will surely correct me > if I am wrong. Afaik all is correct. Someone pointed out to disable rpc.lockd completely but that doesn't help either. Unless the pxe-clients have to do something on their end I'm not aware of. Another stated rpc.lockd is broken for years now and we should implement a dummy one accepting and positively ack all locks while doing nothing actually. That should work as long as you know what you're doing :-D My pxe clients all have separate directories so concurrent locks on one specific file shouldn't occur. The clients do run without rpc.lockd till the moment sendmail starts or you try to run vipw. I didn't observe other quirks but I didn't monitor lockd-less boxen extensively. Thanks for your reply. Kind regards, Robert Joosten
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061225124026.GA709>