From owner-freebsd-questions Tue Dec 1 17:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17323 for freebsd-questions-outgoing; Tue, 1 Dec 1998 17:15:01 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from ns.novator.com ([199.45.114.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17312 for ; Tue, 1 Dec 1998 17:14:59 -0800 (PST) (envelope-from vmg@ns.novator.com) Received: (from vmg@localhost) by ns.novator.com (8.8.8/8.8.8) id UAA19697; Tue, 1 Dec 1998 20:10:42 -0500 (EST) Message-Id: <199812020110.UAA19697@ns.novator.com> Subject: Re: lockd To: eric@rdbewss.redstone.army.mil (Eric Patterson) Date: Tue, 1 Dec 1998 20:10:41 -0500 (EST) From: "Victor Granic" Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <001201be1d65$b1a7d020$8c01a8c0@marvin.rdbewss.redstone.army.mil> from "Eric Patterson" at Dec 1, 98 02:03:41 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you so much, Eric for the pointer to the patches. I did though run into some problems. I am running version 2.2.7 of FreeBSD. Most of the files that needed patching were not patchable because the diffs provided are not same as my original files on the system therefore most of the attempted patches ended up creating reject files. The diffs were very different than my originals therefore difficult to do by hand editting. Fine, no problem, I just downloaded the revisions that the patches expect from the CVS repository, ran patch on these files and replaced the origianls. This time the patch command completed successfully, creating newly patched files minus the rejects. I replaced the old files with the newly patched files, attempted to build a new kernel, but to no avail. Many compile errors. After attempting to fix some of the compile errors I realized I was in trouble. What I need to know is if anyone else has had the same problem with these patches? Any success with version 2.2.7? I'll try again if I know someone was successful. Btw, I originally installed from the Walnut Creek CD (does that make a difference?). I plan on upgrading our system to version 3.0 just so that these patches can be implemented. My FreeBSD machinces have become virtually useless without NFS locking. This is sad considering what a great operating system it is otherwise. Considering these patches were developed in February, I'm wondering why they aren't incorporated in the current releases? Thank you, Victor Eric Patterson said: : : Check out http://www.freebsd.org/~terry/ : : You'll find just the patches you're looking for there. I assume you're = : running 2.2.7. I do not know if these patches work with 2.2, but they = : work with 3.0 : : Eric Patterson : : : Hello, : : In /etc/rc.conf the comment after [en,dis]abling lockd says it's=20 : broken. I had been trying to use it before I noticed the comment : and in fact, it really is broken. I cannot exclusively lock a : file on an NFS mounted partition from my FreeBSD machines. Is : this problem fixed in 2.2.8 or 3.0? Is there an alternative to : using the default lockd? Could I compile/install another one that : isn't broken? : : Thank you, : : Victor : : : To Unsubscribe: send mail to majordomo@FreeBSD.org : with "unsubscribe freebsd-questions" in the body of the message : : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message