| 1 |
zmedico 07/09/22 05:18:12 |
| 2 |
|
| 3 |
Modified: faq.xml |
| 4 |
Log: |
| 5 |
In the portage tree via NFS section, add a note about the metadata_overlay cache module. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.28 xml/htdocs/proj/en/portage/doc/faq.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml?rev=1.28&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml?rev=1.28&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml?r1=1.27&r2=1.28 |
| 13 |
|
| 14 |
Index: faq.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml,v |
| 17 |
retrieving revision 1.27 |
| 18 |
retrieving revision 1.28 |
| 19 |
diff -u -r1.27 -r1.28 |
| 20 |
--- faq.xml 22 Sep 2007 01:31:32 -0000 1.27 |
| 21 |
+++ faq.xml 22 Sep 2007 05:18:11 -0000 1.28 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml,v 1.27 2007/09/22 01:31:32 zmedico Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml,v 1.28 2007/09/22 05:18:11 zmedico Exp $ --> |
| 27 |
|
| 28 |
<guide link="/proj/en/portage/doc/faq.xml" lang="en"> |
| 29 |
<title>Portage Frequently Asked Questions (FAQ)</title> |
| 30 |
@@ -24,7 +24,7 @@ |
| 31 |
<license/> |
| 32 |
|
| 33 |
<version>1.0</version> |
| 34 |
-<date>2006-04-04</date> |
| 35 |
+<date>2007-09-21</date> |
| 36 |
<chapter> |
| 37 |
<title>Frequently Asked Questions</title> |
| 38 |
<section> |
| 39 |
@@ -66,7 +66,15 @@ |
| 40 |
Mounting <path>/usr/portage</path> over NFS is possible. However you must be |
| 41 |
careful to run <c>emerge --metadata</c> on all clients who are mounting the tree |
| 42 |
over NFS. Otherwise their Portage cache's will be stable and Portage will run rather |
| 43 |
-slowly. You need not run <c>emerge --sync</c> on every client. If you encounter |
| 44 |
+slowly. You need not run <c>emerge --sync</c> on every client. |
| 45 |
+</p> |
| 46 |
+<note>It is unnecessary to run <c>emerge --metadata</c> if the |
| 47 |
+metadata_overlay cache module is enabled in <path>/etc/portage/modules</path>. |
| 48 |
+The portage manual page (run <c>man portage</c>) describes the steps necessary |
| 49 |
+to enable this. |
| 50 |
+</note> |
| 51 |
+<p> |
| 52 |
+If you encounter |
| 53 |
problems with an NFS setup it is important that you ensure you have the proper locking |
| 54 |
daemons on both the NFS client machines and the NFS server machine. Portage uses |
| 55 |
hardlinks over NFS in an attempt to lock files; if the locking daemon fails to lock |
| 56 |
|
| 57 |
|
| 58 |
|
| 59 |
-- |
| 60 |
gentoo-commits@g.o mailing list |
Archives