From novel@novel.fannet.ru Tue Oct 3 17:26:57 2006 Return-Path: Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB39A16A403 for ; Tue, 3 Oct 2006 17:26:57 +0000 (UTC) (envelope-from novel@novel.fannet.ru) Received: from novel.fannet.ru (novel.fannet.ru [82.116.56.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28E7743D49 for ; Tue, 3 Oct 2006 17:26:56 +0000 (GMT) (envelope-from novel@novel.fannet.ru) Received: from novel.fannet.ru (localhost [127.0.0.1]) by novel.fannet.ru (8.13.8/8.13.6) with ESMTP id k93HRFhO075331 for ; Tue, 3 Oct 2006 21:27:15 +0400 (MSD) (envelope-from novel@novel.fannet.ru) Received: (from novel@localhost) by novel.fannet.ru (8.13.8/8.13.6/Submit) id k93HRFeU075330; Tue, 3 Oct 2006 21:27:15 +0400 (MSD) (envelope-from novel) Message-Id: <200610031727.k93HRFeU075330@novel.fannet.ru> Date: Tue, 3 Oct 2006 21:27:15 +0400 (MSD) From: Roman Bogorodskiy Reply-To: Roman Bogorodskiy To: FreeBSD-gnats-submit@freebsd.org Cc: Subject: [ patch ] [ handbook ] add a section about NFS locking to Handbook X-Send-Pr-Version: 3.113 X-GNATS-Notify: >Number: 103956 >Category: docs >Synopsis: [ patch ] [ handbook ] add a section about NFS locking to Handbook >Confidential: no >Severity: non-critical >Priority: medium >Responsible: remko >State: closed >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Tue Oct 03 17:30:14 GMT 2006 >Closed-Date: Fri Oct 13 14:11:48 GMT 2006 >Last-Modified: Fri Oct 13 14:20:16 GMT 2006 >Originator: Roman Bogorodskiy >Release: FreeBSD 6.1-STABLE i386 >Organization: >Environment: System: FreeBSD novel.fannet.ru 6.1-STABLE FreeBSD 6.1-STABLE #4: Thu Aug 24 15:55:09 MSD 2006 root@novel.fannet.ru:/usr/obj/usr/src/sys/NOVEL i386 >Description: Add an instruction to Handbook how to enable NFS locking. remko@ and shaun@ helped to improve wording and markup. >How-To-Repeat: >Fix: --- nfslocking.diff begins here --- Index: chapter.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml,v retrieving revision 1.89 diff -u -r1.89 chapter.sgml --- chapter.sgml 24 Sep 2006 14:17:15 -0000 1.89 +++ chapter.sgml 3 Oct 2006 17:09:59 -0000 @@ -822,6 +822,23 @@ + Locking + + Some applications (e.g. mutt) + require file locking to operate correctly. In the case of + NFS, rpc.lockd + can be used for file locking. To enable it, add the following + to the /etc/rc.conf file on both client + and server (it is assumed that NFS + client and server are configured already): + + rpc_lockd_enable="YES" +rpc_statd_enable="YES" + + Start the application by using: + &prompt.root; /etc/rc.d/nfslocking start + + Practical Uses NFS has many practical uses. Some of --- nfslocking.diff ends here --- >Release-Note: >Audit-Trail: From: "Simon L. Nielsen" To: Roman Bogorodskiy Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: docs/103956: [ patch ] [ handbook ] add a section about NFS locking to Handbook Date: Tue, 3 Oct 2006 21:12:49 +0200 On 2006.10.03 21:27:15 +0400, Roman Bogorodskiy wrote: > Add an instruction to Handbook how to enable NFS locking. remko@ and > shaun@ helped to improve wording and markup. It might be a good idea adding a note that rpc.lockd is still considered rather buggy and depending on setup it might be better to use the -L for the NFS mount which just does local locking, which of cause only works if you only have program(s) from one host... -- Simon L. Nielsen From: Roman Bogorodskiy To: bug-followup@FreeBSD.org Cc: "Simon L. Nielsen" Subject: Re: docs/103956: [ patch ] [ handbook ] add a section about NFS locking to Handbook Date: Thu, 5 Oct 2006 11:25:33 +0400 --St7VIuEGZ6dlpu13 Content-Type: multipart/mixed; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline An updated patch with a note about mount_nfs -L, as simon@ suggested. --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="nfslocking.diff" Content-Transfer-Encoding: quoted-printable Index: chapter.sgml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/network-servers/cha= pter.sgml,v retrieving revision 1.89 diff -u -r1.89 chapter.sgml --- chapter.sgml 24 Sep 2006 14:17:15 -0000 1.89 +++ chapter.sgml 5 Oct 2006 07:15:10 -0000 @@ -822,6 +822,29 @@ =20 + Locking + =20 + Some applications (e.g. mutt) + require file locking to operate correctly. In the case of + NFS, rpc.lockd + can be used for file locking. To enable it, add the following + to the /etc/rc.conf file on both client + and server (it is assumed that NFS + client and server are configured already): +=09 + rpc_lockd_enable=3D"YES" +rpc_statd_enable=3D"YES" +=09 + Start the application by using: + &prompt.root; /etc/rc.d/nfslocking start + + However, there is one more way of doing locking in + NFS avaible. It is possible to pass -L to + mount_nfs, but it is suitable for + local locking only. Refer to &man.mount.nfs.8; for details. + + + Practical Uses =20 NFS has many practical uses. Some of --cNdxnHkX5QqsyA0e-- --St7VIuEGZ6dlpu13 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iQCVAwUBRSSzbYB0WzgdqspGAQJ6rAQAt7oPGXMwWMDSvc8tTMa6meOd/HTSRDHQ RSdsxVBw8DEpbqYorzqgRtAUoDAJv/x8TjgZ2k2MeZ55uGEW9SxOQGmjvYTiy/fq fQI4CoFNYsFaa0bbV+m1Y86uT577djB+DJpEcpEh5Y9qrlncGb+WHwgG7AXy1cfh VdLGXSnlZ8Q= =x7Y+ -----END PGP SIGNATURE----- --St7VIuEGZ6dlpu13-- From: Roman Bogorodskiy To: bug-followup@FreeBSD.org Cc: Remko Lodder , "Simon L. Nielsen" Subject: Re: docs/103956: [ patch ] [ handbook ] add a section about NFS locking to Handbook Date: Thu, 5 Oct 2006 15:05:59 +0400 --cmJC7u66zC7hs+87 Content-Type: multipart/mixed; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Update - fixed problems reported by remko. --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="nfslocking.diff" Content-Transfer-Encoding: quoted-printable Index: chapter.sgml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/network-servers/cha= pter.sgml,v retrieving revision 1.89 diff -u -r1.89 chapter.sgml --- chapter.sgml 24 Sep 2006 14:17:15 -0000 1.89 +++ chapter.sgml 5 Oct 2006 11:02:38 -0000 @@ -822,6 +822,30 @@ =20 + Locking + =20 + Some applications (e.g. mutt) + require file locking to operate correctly. In the case of + NFS, rpc.lockd + can be used for file locking. To enable it, add the following + to the /etc/rc.conf file on both client + and server (it is assumed that NFS + client and server are configured already): +=09 + rpc_lockd_enable=3D"YES" +rpc_statd_enable=3D"YES" +=09 + Start the application by using: + &prompt.root; /etc/rc.d/nfslocking start + + However, there is one more way of doing locking in + NFS available. It is possible to pass=20 + to &man.mount.nfs.8;, but it is suitable + for local locking only. Refer to &man.mount.nfs.8; for + details. + + + Practical Uses =20 NFS has many practical uses. Some of --HlL+5n6rz5pIUxbD-- --cmJC7u66zC7hs+87 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iQCVAwUBRSTnF4B0WzgdqspGAQIYGAQAgqc3yIbIJgfesuGFl+Pvg1HC502+HK8e AP9cdsrMF8+Y9yT66mYmdBc8mGJ5l90+pbrZXUbq5e3AR0rscIeANR0Fiq0yrPPs Amf6mj4EKVi4A81ZA+zptxCZngWpDL4prY/jyVkcKVfrMlbE5dUY2I5+fF2bEf5n vuSvhE2v1qA= =1A8a -----END PGP SIGNATURE----- --cmJC7u66zC7hs+87-- From: "Simon L. Nielsen" To: Roman Bogorodskiy Cc: bug-followup@FreeBSD.org, Remko Lodder Subject: Re: docs/103956: [ patch ] [ handbook ] add a section about NFS locking to Handbook Date: Sun, 8 Oct 2006 19:30:23 +0200 On 2006.10.05 15:05:59 +0400, Roman Bogorodskiy wrote: > Update - fixed problems reported by remko. > > + Locking > + > + Some applications (e.g. mutt) > + require file locking to operate correctly. In the case of > + NFS, rpc.lockd > + can be used for file locking. To enable it, add the following > + to the /etc/rc.conf file on both client > + and server (it is assumed that NFS > + client and server are configured already): > + > + rpc_lockd_enable="YES" > +rpc_statd_enable="YES" > + > + Start the application by using: Here should be an extra newline. > + &prompt.root; /etc/rc.d/nfslocking start > + > + However, there is one more way of doing locking in > + NFS available. It is possible to pass > + to &man.mount.nfs.8;, but it is suitable > + for local locking only. Refer to &man.mount.nfs.8; for > + details. How about instead, something like: If real locking between the NFS clients and NFS server is not required, it is possible to let the NFS client do locking locally by passing -L to &man.mount.nfs.8;. Refer to the &man.mount.nfs.8; manual page for further details. ? You also have a bit of end-of-line whitespace which should be removed. > + > + > + > Practical Uses > > NFS has many practical uses. Some of -- Simon L. Nielsen From: Roman Bogorodskiy To: "Simon L. Nielsen" Cc: bug-followup@FreeBSD.org, Remko Lodder Subject: Re: docs/103956: [ patch ] [ handbook ] add a section about NFS locking to Handbook Date: Sun, 8 Oct 2006 22:29:44 +0400 --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Simon L. Nielsen wrote: > On 2006.10.05 15:05:59 +0400, Roman Bogorodskiy wrote: > > Update - fixed problems reported by remko. >=20 > > > > + Locking > > + =20 > > + Some applications (e.g. mutt) > > + require file locking to operate correctly. In the case of > > + NFS, rpc.lockd > > + can be used for file locking. To enable it, add the following > > + to the /etc/rc.conf file on both client > > + and server (it is assumed that NFS > > + client and server are configured already): > > +=09 > > + rpc_lockd_enable=3D"YES" > > +rpc_statd_enable=3D"YES" > > +=09 > > + Start the application by using: >=20 > Here should be an extra newline. >=20 > > + &prompt.root; /etc/rc.d/nfslocking start > > + > > + However, there is one more way of doing locking in > > + NFS available. It is possible to pass=20 > > + to &man.mount.nfs.8;, but it is suitable > > + for local locking only. Refer to &man.mount.nfs.8; for > > + details. >=20 > How about instead, something like: >=20 > If real locking between the NFS clients and NFS server is not > required, it is possible to let the NFS client do locking > locally by passing -L to &man.mount.nfs.8;. Refer to the > &man.mount.nfs.8; manual page for further details. >=20 > ? >=20 > You also have a bit of end-of-line whitespace which should be removed. Here's an updated diff: http://novel.fannet.ru/~novel/nfslocking.diff.=20 Roman Bogorodskiy --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iQCVAwUBRSlDmIB0WzgdqspGAQJOLQP/WVRv9LUtHwXa5+LZ+YDQAWuyRmRhtN0v 5gOtlntkYobHLnzHIjVZdc2q9g84/WU53/gaMj3PzAGb1juYqd05RJMNW8X5f+II 15JbuvS46doq2wbKrvRy6zQo4XAppvkP2oiF0LVukjt2XlKzfkd8oC1cMm7TmyEl XJa2YN8btJg= =fELa -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- From: Remko Lodder To: Roman Bogorodskiy Cc: "Simon L. Nielsen" , bug-followup@FreeBSD.org Subject: Re: docs/103956: [ patch ] [ handbook ] add a section about NFS locking to Handbook Date: Fri, 13 Oct 2006 11:25:13 +0200 Where is the diff now?? (The url no longer has the nfslocking.diff command) On Sun, Oct 08, 2006 at 10:29:44PM +0400, Roman Bogorodskiy wrote: > Simon L. Nielsen wrote: > > > On 2006.10.05 15:05:59 +0400, Roman Bogorodskiy wrote: > > > Update - fixed problems reported by remko. > > > > > > > > + Locking > > > + > > > + Some applications (e.g. mutt) > > > + require file locking to operate correctly. In the case of > > > + NFS, rpc.lockd > > > + can be used for file locking. To enable it, add the following > > > + to the /etc/rc.conf file on both client > > > + and server (it is assumed that NFS > > > + client and server are configured already): > > > + > > > + rpc_lockd_enable="YES" > > > +rpc_statd_enable="YES" > > > + > > > + Start the application by using: > > > > Here should be an extra newline. > > > > > + &prompt.root; /etc/rc.d/nfslocking start > > > + > > > + However, there is one more way of doing locking in > > > + NFS available. It is possible to pass > > > + to &man.mount.nfs.8;, but it is suitable > > > + for local locking only. Refer to &man.mount.nfs.8; for > > > + details. > > > > How about instead, something like: > > > > If real locking between the NFS clients and NFS server is not > > required, it is possible to let the NFS client do locking > > locally by passing -L to &man.mount.nfs.8;. Refer to the > > &man.mount.nfs.8; manual page for further details. > > > > ? > > > > You also have a bit of end-of-line whitespace which should be removed. > > Here's an updated diff: http://novel.fannet.ru/~novel/nfslocking.diff. > > Roman Bogorodskiy -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ Responsible-Changed-From-To: freebsd-doc->remko Responsible-Changed-By: remko Responsible-Changed-When: Fri Oct 13 11:23:59 UTC 2006 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=103956 From: Roman Bogorodskiy To: Remko Lodder Cc: "Simon L. Nielsen" , bug-followup@FreeBSD.org Subject: Re: docs/103956: [ patch ] [ handbook ] add a section about NFS locking to Handbook Date: Fri, 13 Oct 2006 15:53:59 +0400 --zq44+AAfm4giZpo5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Remko Lodder wrote: > Where is the diff now?? (The url no longer has the nfslocking.diff comman= d) Hm, there's a weird problem with Apache. The diff should be avaible again. =20 > On Sun, Oct 08, 2006 at 10:29:44PM +0400, Roman Bogorodskiy wrote: > > Simon L. Nielsen wrote: > >=20 > > > On 2006.10.05 15:05:59 +0400, Roman Bogorodskiy wrote: > > > > Update - fixed problems reported by remko. > > >=20 > > > > > > > > + Locking > > > > + =20 > > > > + Some applications (e.g. mutt) > > > > + require file locking to operate correctly. In the case of > > > > + NFS, rpc.lockd > > > > + can be used for file locking. To enable it, add the follo= wing > > > > + to the /etc/rc.conf file on both clie= nt > > > > + and server (it is assumed that NFS > > > > + client and server are configured already): > > > > +=09 > > > > + rpc_lockd_enable=3D"YES" > > > > +rpc_statd_enable=3D"YES" > > > > +=09 > > > > + Start the application by using: > > >=20 > > > Here should be an extra newline. > > >=20 > > > > + &prompt.root; /etc/rc.d/nfslocking start<= /userinput> > > > > + > > > > + However, there is one more way of doing locking in > > > > + NFS available. It is possible to pass= =20 > > > > + to &man.mount.nfs.8;, but it is suitab= le > > > > + for local locking only. Refer to &man.mount.nfs.8; for > > > > + details. > > >=20 > > > How about instead, something like: > > >=20 > > > If real locking between the NFS clients and NFS server is not > > > required, it is possible to let the NFS client do locking > > > locally by passing -L to &man.mount.nfs.8;. Refer to the > > > &man.mount.nfs.8; manual page for further details. > > >=20 > > > ? > > >=20 > > > You also have a bit of end-of-line whitespace which should be removed. > >=20 > > Here's an updated diff: http://novel.fannet.ru/~novel/nfslocking.diff.= =20 > >=20 > > Roman Bogorodskiy >=20 >=20 >=20 > --=20 > Kind regards, >=20 > Remko Lodder ** remko@elvandar.org > FreeBSD ** remko@FreeBSD.org >=20 > /* Quis custodiet ipsos custodes */ --zq44+AAfm4giZpo5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iQCVAwUBRS9+V4B0WzgdqspGAQLpHQP/SRr4RMeG+uxx5ZsDFhz/y7QgCVOdZntY lu69dANIsrNKhEW95xYXca83cF0hmBCggef/xLVLd9MTKNXSS7AzokiQ9vnIZsqJ TLwLDMOkK93q4bdJCx5hGgcGARaaIis1ov2Oz1Sgo4Zyo5dOdW4hbLlsqCu5D9oe e14m4gg5Kuk= =xzle -----END PGP SIGNATURE----- --zq44+AAfm4giZpo5-- State-Changed-From-To: open->closed State-Changed-By: remko State-Changed-When: Fri Oct 13 14:11:47 UTC 2006 State-Changed-Why: I committed the patch, thank you very much. I only changed a little (formatting style) but the rest was OK, keep it up. http://www.freebsd.org/cgi/query-pr.cgi?pr=103956 From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/103956: commit references a PR Date: Fri, 13 Oct 2006 14:11:07 +0000 (UTC) remko 2006-10-13 14:11:00 UTC FreeBSD doc repository Modified files: en_US.ISO8859-1/books/handbook/network-servers chapter.sgml Log: Add documentation about NFSlocking. PR: docs/103956 Submitted by: novel Facilitated by: Snow B.V. Revision Changes Path 1.91 +26 -0 doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" >Unformatted: