Date: Wed, 15 Oct 2003 12:19:50 +0200 From: Volker Quetschke <quetschke@scytek.de> To: dev@porting.openoffice.org Cc: openoffice@freebsd.org Subject: Re: [porting-dev] Build fails on NFS volume Message-ID: <3F8D1F46.6050403@scytek.de> In-Reply-To: <20031014135525.GG30746@pmp.uni-hannover.de> References: <3F8B1626.8070406@scytek.de> <openoffice.porting.dev-3F8BD568.7000201@scytek.de> <3F8BDE9F.7020801@sun.com> <20031014135525.GG30746@pmp.uni-hannover.de>
next in thread | previous in thread | raw e-mail | index | archive | help
(Crossposting to openoffice@freebsd.org because this might be of some interest) Problem was: openoffice-devel cannot be build on NFS. >>>- use NFS instead of local file system >> >>Aha, that sounds like a 'file locking over NFS' issue. > > Seems so. I just copied the whole tree to a local partition, and now > everything seems to compile fine (though it's far from being finished by now > :-). > >>I've seen such things before on Linux, when the NFS 'lockd' is not >>running (some / few distributions have / had too 'clever' NFS startup >>scripts, omitting to start 'lockd'). Just starting 'lockd' usually >>solved all NFS file locking problems. > > In my experience locking via NFS is a real pain. I've never seen a working > lockd on Linux or *BSD (only on commercial unices like Solaris :-). Perhaps > this has changed meanwhile. However, just starting lockd didn't help, but > maybe the system needs a reboot for this to work (the manpage is somewhat > ambiguous here :-). I'll reboot the system and try NFS with activated lockd/statd > as soon as the local compile has successfully finished. The NFS server is a FreeBSD 4.8 machine and despite of <http://lists.freebsd.org/pipermail/freebsd-hackers/2003-April/000592.html>; we started the rpc.lockd on that machine. That helped and the build continued .... Volker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F8D1F46.6050403>