| 1 |
neysx 07/06/29 08:33:12 |
| 2 |
|
| 3 |
Modified: openafs.xml |
| 4 |
Log: |
| 5 |
Update from #176407 |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.24 xml/htdocs/doc/en/openafs.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?rev=1.24&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?rev=1.24&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?r1=1.23&r2=1.24 |
| 13 |
|
| 14 |
Index: openafs.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v |
| 17 |
retrieving revision 1.23 |
| 18 |
retrieving revision 1.24 |
| 19 |
diff -u -r1.23 -r1.24 |
| 20 |
--- openafs.xml 9 Nov 2005 20:58:07 -0000 1.23 |
| 21 |
+++ openafs.xml 29 Jun 2007 08:33:12 -0000 1.24 |
| 22 |
@@ -1,5 +1,5 @@ |
| 23 |
<?xml version='1.0' encoding="UTF-8"?> |
| 24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.23 2005/11/09 20:58:07 fox2mike Exp $ --> |
| 25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.24 2007/06/29 08:33:12 neysx Exp $ --> |
| 26 |
|
| 27 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 28 |
|
| 29 |
@@ -7,6 +7,9 @@ |
| 30 |
<title>Gentoo Linux OpenAFS Guide</title> |
| 31 |
|
| 32 |
<author title="Editor"> |
| 33 |
+ <mail link="stefaan@g.o">Stefaan De Roeck</mail> |
| 34 |
+</author> |
| 35 |
+<author title="Editor"> |
| 36 |
<mail link="darks@g.o">Holger Brueckner</mail> |
| 37 |
</author> |
| 38 |
<author title="Editor"> |
| 39 |
@@ -19,9 +22,6 @@ |
| 40 |
<mail link="fnjordy@×××××.com">Steven McCoy</mail> |
| 41 |
</author> |
| 42 |
<author title="Editor"> |
| 43 |
- <mail link="stefaan@g.o">Stefaan De Roeck</mail> |
| 44 |
-</author> |
| 45 |
-<author title="Editor"> |
| 46 |
<mail link="fox2mike@g.o">Shyam Mani</mail> |
| 47 |
</author> |
| 48 |
|
| 49 |
@@ -34,8 +34,8 @@ |
| 50 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 51 |
<license/> |
| 52 |
|
| 53 |
-<version>1.1</version> |
| 54 |
-<date>2005-11-10</date> |
| 55 |
+<version>1.2</version> |
| 56 |
+<date>2007-06-29</date> |
| 57 |
|
| 58 |
<chapter> |
| 59 |
<title>Overview</title> |
| 60 |
@@ -44,7 +44,7 @@ |
| 61 |
<body> |
| 62 |
|
| 63 |
<p> |
| 64 |
-This document provides you with all neccessary steps to install an OpenAFS |
| 65 |
+This document provides you with all necessary steps to install an OpenAFS |
| 66 |
server on Gentoo Linux. Parts of this document are taken from the AFS FAQ and |
| 67 |
IBM's Quick Beginnings guide on AFS. Well, never reinvent the wheel. :) |
| 68 |
</p> |
| 69 |
@@ -78,7 +78,7 @@ |
| 70 |
</p> |
| 71 |
|
| 72 |
</body> |
| 73 |
-</section> |
| 74 |
+</section> |
| 75 |
<section> |
| 76 |
<title>What is an AFS cell?</title> |
| 77 |
<body> |
| 78 |
@@ -92,11 +92,11 @@ |
| 79 |
file which they are accessing, is located. They even won't notice if a server |
| 80 |
will be located to another room, since every volume can be replicated and |
| 81 |
moved to another server without any user noticing. The files are always |
| 82 |
-accessible. Well, it's like NFS on steroids :) |
| 83 |
+accessible. Well, it's like NFS on steroids :) |
| 84 |
</p> |
| 85 |
|
| 86 |
</body> |
| 87 |
-</section> |
| 88 |
+</section> |
| 89 |
<section> |
| 90 |
<title>What are the benefits of using AFS?</title> |
| 91 |
<body> |
| 92 |
@@ -111,7 +111,7 @@ |
| 93 |
</p> |
| 94 |
|
| 95 |
</body> |
| 96 |
-</section> |
| 97 |
+</section> |
| 98 |
<section> |
| 99 |
<title>Where can I get more information?</title> |
| 100 |
<body> |
| 101 |
@@ -134,7 +134,7 @@ |
| 102 |
</p> |
| 103 |
|
| 104 |
</body> |
| 105 |
-</section> |
| 106 |
+</section> |
| 107 |
<section> |
| 108 |
<title>How Can I Debug Problems?</title> |
| 109 |
<body> |
| 110 |
@@ -160,7 +160,7 @@ |
| 111 |
This section aims to help you through the process of upgrading an existing |
| 112 |
OpenAFS installation to OpenAFS version 1.4.0 or higher (or 1.2.x starting from |
| 113 |
1.2.13. The latter will not be handled specifically, as most people will want |
| 114 |
-1.4 for a.o.linux-2.6 support, large file support and bug fixes). |
| 115 |
+1.4 for a.o. linux-2.6 support, large file support and bug fixes). |
| 116 |
</p> |
| 117 |
|
| 118 |
<p> |
| 119 |
@@ -168,7 +168,7 @@ |
| 120 |
safely skip this chapter. However, if you're upgrading from a previous version, |
| 121 |
we strongly urge you to follow the guidelines in the next sections. The |
| 122 |
transition script in the ebuild is designed to assist you in quickly upgrading |
| 123 |
-and restarting. Please not that it will (for safety reasons) not delete |
| 124 |
+and restarting. Please note that it will (for safety reasons) not delete |
| 125 |
configuration files and startup scripts in old places, not automatically change |
| 126 |
your boot configuration to use the new scripts, etc. If you need further |
| 127 |
convincing, using an old OpenAFS kernel module together with the updated system |
| 128 |
@@ -289,7 +289,7 @@ |
| 129 |
into <path>/etc/conf.d/openafs-client</path> and |
| 130 |
<path>/etc/conf.d/openafs-server</path>. Also, options in |
| 131 |
<path>/etc/conf.d/afs</path> to turn either client or server on or off have |
| 132 |
-been obsoleted. |
| 133 |
+been obsoleted. |
| 134 |
</p> |
| 135 |
|
| 136 |
<p> |
| 137 |
@@ -309,7 +309,7 @@ |
| 138 |
<li> |
| 139 |
Some people use soft-links to point to the real disk cache location. |
| 140 |
The init script didn't like this, because then this cache location |
| 141 |
- didn't turn up in <path>/proc/mounts</path>. |
| 142 |
+ didn't turn up in <path>/proc/mounts</path>. |
| 143 |
</li> |
| 144 |
<li> |
| 145 |
Many prefer ext3 over ext2 nowadays. Both filesystems are valid for |
| 146 |
@@ -342,7 +342,7 @@ |
| 147 |
</p> |
| 148 |
|
| 149 |
<pre caption="Checking your CONFIG_PROTECT_MASK"> |
| 150 |
-# <i>emerge info | grep "CONFIG_PROTECT_MASK</i> |
| 151 |
+# <i>emerge info | grep "CONFIG_PROTECT_MASK"</i> |
| 152 |
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" |
| 153 |
</pre> |
| 154 |
|
| 155 |
@@ -367,7 +367,7 @@ |
| 156 |
|
| 157 |
<ul> |
| 158 |
<li> |
| 159 |
- <path>/usr/afs/etc</path> is copied to<path>/etc/openafs/server</path> |
| 160 |
+ <path>/usr/afs/etc</path> is copied to <path>/etc/openafs/server</path> |
| 161 |
</li> |
| 162 |
<li> |
| 163 |
<path>/usr/vice/etc</path> is copied to <path>/etc/openafs</path> |
| 164 |
@@ -378,7 +378,7 @@ |
| 165 |
<li> |
| 166 |
<path>/usr/afs/local/BosConfig</path> is copied to |
| 167 |
<path>/etc/openafs/BosConfig</path>, while replacing occurrences of |
| 168 |
- <path>/usr/afs/bin/</path> with <path>/usr/libexec/openafs</path>, |
| 169 |
+ <path>/usr/afs/bin/</path> with <path>/usr/libexec/openafs</path>, |
| 170 |
<path>/usr/afs/etc</path> with <path>/etc/openafs/server</path> |
| 171 |
and <path>/usr/afs/bin</path> (without the / as previously) with |
| 172 |
<path>/usr/bin</path> |
| 173 |
@@ -459,7 +459,7 @@ |
| 174 |
|
| 175 |
<p> |
| 176 |
Before starting the OpenAFS client again, please take time to check your |
| 177 |
-cache settings. They are determined by <path>/etc/openafs/cacheinfo</path>. |
| 178 |
+cache settings. They are determined by <path>/etc/openafs/cacheinfo</path>. |
| 179 |
To restart your OpenAFS client installation, please type the following: |
| 180 |
</p> |
| 181 |
|
| 182 |
@@ -533,7 +533,7 @@ |
| 183 |
the OpenAFS client and server on startup. Those who don't can safely skip |
| 184 |
this section. If you had your system configured to start them automatically, |
| 185 |
you will need to re-enable this, because the names of the init scripts have |
| 186 |
-changed. |
| 187 |
+changed. |
| 188 |
</p> |
| 189 |
|
| 190 |
<pre caption="Re-enabling OpenAFS startup at boot time"> |
| 191 |
@@ -555,10 +555,10 @@ |
| 192 |
<body> |
| 193 |
|
| 194 |
<p> |
| 195 |
-Don't panic. You shouldn't have lost any data or configuration files. So |
| 196 |
-let's analyze the situation. Please file a bug at |
| 197 |
-<uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri> in any case, |
| 198 |
-preferably with as much information as possible. |
| 199 |
+Don't panic. You shouldn't have lost any data or configuration files. So let's |
| 200 |
+analyze the situation. Please file a bug at <uri |
| 201 |
+link="http://bugs.gentoo.org">bugs.gentoo.org</uri> in any case, preferably |
| 202 |
+with as much information as possible. |
| 203 |
</p> |
| 204 |
|
| 205 |
<p> |
| 206 |
@@ -572,7 +572,7 @@ |
| 207 |
</li> |
| 208 |
<li> |
| 209 |
Check <path>/etc/openafs/cacheinfo</path>. It should be of the form: |
| 210 |
- /afs:{path to disk cache}:{number of blocks for disk cache}. |
| 211 |
+ /afs:{path to disk cache}:{number of blocks for disk cache}. |
| 212 |
Normally, your disk cache will be located at |
| 213 |
<path>/var/cache/openafs</path>. |
| 214 |
</li> |
| 215 |
@@ -638,7 +638,7 @@ |
| 216 |
Documentation. |
| 217 |
</p> |
| 218 |
|
| 219 |
-</body> |
| 220 |
+</body> |
| 221 |
</section> |
| 222 |
</chapter> |
| 223 |
|
| 224 |
@@ -648,11 +648,6 @@ |
| 225 |
<title>Building the Client</title> |
| 226 |
<body> |
| 227 |
|
| 228 |
-<note> |
| 229 |
-All commands should be written in one line!! In this document they are |
| 230 |
-sometimes wrapped to two lines to make them easier to read. |
| 231 |
-</note> |
| 232 |
- |
| 233 |
<pre caption="Installing openafs"> |
| 234 |
# <i>emerge net-fs/openafs</i> |
| 235 |
</pre> |
| 236 |
@@ -702,7 +697,7 @@ |
| 237 |
10.0.0.1 #storage |
| 238 |
|
| 239 |
ThisCell: |
| 240 |
-netlabs |
| 241 |
+netlabs |
| 242 |
</pre> |
| 243 |
|
| 244 |
<warn> |
| 245 |
@@ -711,7 +706,14 @@ |
| 246 |
</warn> |
| 247 |
|
| 248 |
<p> |
| 249 |
-For a quick start, you can now start <path>/etc/init.d/openafs/client</path> and |
| 250 |
+CellServDB tells your client which server(s) it needs to contact for a |
| 251 |
+specific cell. ThisCell should be quite obvious. Normally you use a name |
| 252 |
+which is unique for your organisation. Your (official) domain might be a |
| 253 |
+good choice. |
| 254 |
+</p> |
| 255 |
+ |
| 256 |
+<p> |
| 257 |
+For a quick start, you can now start <path>/etc/init.d/openafs-client</path> and |
| 258 |
use <c>klog</c> to authenticate yourself and start using your access to the |
| 259 |
cell. For automatic logons to you cell, you want to consult the appropriate |
| 260 |
section below. |
| 261 |
@@ -725,12 +727,13 @@ |
| 262 |
|
| 263 |
<note> |
| 264 |
Unfortunately the AFS Client needs a ext2/3 filesystem for its cache to run |
| 265 |
-correctly, because there are some issues with reiserfs. |
| 266 |
+correctly. There are some issues when using other filesystems (using e.g. |
| 267 |
+reiserfs is not a good idea). |
| 268 |
</note> |
| 269 |
|
| 270 |
<p> |
| 271 |
-You can house your cache on an existing filesystem (if it's ext2/3), but some |
| 272 |
-may want to create a separate partition for that. The default location of the |
| 273 |
+You can house your cache on an existing filesystem (if it's ext2/3), or you |
| 274 |
+may want to have a separate partition for that. The default location of the |
| 275 |
cache is <path>/var/cache/openafs</path>, but you can change that by editing |
| 276 |
<path>/etc/openafs/cacheinfo</path>. A standard size for your cache is |
| 277 |
200MB, but more won't hurt. |
| 278 |
@@ -739,39 +742,6 @@ |
| 279 |
</body> |
| 280 |
</section> |
| 281 |
<section> |
| 282 |
-<title>Adjusting the cell access configuration</title> |
| 283 |
-<body> |
| 284 |
- |
| 285 |
-<p> |
| 286 |
-In case you want to do more than just read-only browsing of globally available |
| 287 |
-AFS cells, you need to adjust the two files CellServDB and ThisCell. These |
| 288 |
-are located in <path>/etc/openafs</path>. |
| 289 |
-</p> |
| 290 |
- |
| 291 |
-<pre caption="Adjusting CellServDB and ThisCell"> |
| 292 |
-CellServDB: |
| 293 |
->netlabs #Cell name |
| 294 |
-10.0.0.1 #storage |
| 295 |
- |
| 296 |
-ThisCell: |
| 297 |
-netlabs |
| 298 |
-</pre> |
| 299 |
- |
| 300 |
-<warn> |
| 301 |
-Only use spaces inside the <path>CellServDB</path> file. The client will most |
| 302 |
-likely fail if you use TABs. |
| 303 |
-</warn> |
| 304 |
- |
| 305 |
-<p> |
| 306 |
-CellServDB tells your client which server(s) it needs to contact for a |
| 307 |
-specific cell. ThisCell should be quite obvious. Normally you use a name |
| 308 |
-which is unique for your organisation. Your (official) domain might be a |
| 309 |
-good choice. |
| 310 |
-</p> |
| 311 |
- |
| 312 |
-</body> |
| 313 |
-</section> |
| 314 |
-<section> |
| 315 |
<title>Starting AFS on startup</title> |
| 316 |
<body> |
| 317 |
|
| 318 |
@@ -786,8 +756,8 @@ |
| 319 |
if your AFS server is down. (And this is quite a long long time) |
| 320 |
</warn> |
| 321 |
|
| 322 |
-<pre caption="Adding AFS server to the default runlevel"> |
| 323 |
-# <i>rc-update add openafs-server default</i> |
| 324 |
+<pre caption="Adding AFS client to the default runlevel"> |
| 325 |
+# <i>rc-update add openafs-client default</i> |
| 326 |
</pre> |
| 327 |
|
| 328 |
</body> |
| 329 |
@@ -800,9 +770,14 @@ |
| 330 |
<title>Building the Server</title> |
| 331 |
<body> |
| 332 |
|
| 333 |
+<note> |
| 334 |
+All commands should be written in one line!! In this document they are |
| 335 |
+sometimes wrapped to two lines to make them easier to read. |
| 336 |
+</note> |
| 337 |
+ |
| 338 |
<p> |
| 339 |
-The following command will install all necessary binaries for setting up an AFS |
| 340 |
-Server <e>and</e> Client. |
| 341 |
+If you haven't already done so, the following command will install all |
| 342 |
+necessary binaries for setting up an AFS Server <e>and</e> Client. |
| 343 |
</p> |
| 344 |
|
| 345 |
<pre caption="Installing openafs"> |
| 346 |
@@ -812,20 +787,11 @@ |
| 347 |
</body> |
| 348 |
</section> |
| 349 |
<section> |
| 350 |
-<title>Starting AFS Server</title> |
| 351 |
+<title>Starting AFS Server</title> |
| 352 |
<body> |
| 353 |
|
| 354 |
<p> |
| 355 |
-You need to remove the sample CellServDB and ThisCell file first. |
| 356 |
-</p> |
| 357 |
- |
| 358 |
-<pre caption="Remove sample files"> |
| 359 |
-# <i>rm /usr/vice/etc/ThisCell</i> |
| 360 |
-# <i>rm /usr/vice/etc/CellServDB</i> |
| 361 |
-</pre> |
| 362 |
- |
| 363 |
-<p> |
| 364 |
-Next you will run the <c>bosserver</c> command to initialize the Basic OverSeer |
| 365 |
+You need to run the <c>bosserver</c> command to initialize the Basic OverSeer |
| 366 |
(BOS) Server, which monitors and controls other AFS server processes on its |
| 367 |
server machine. Think of it as init for the system. Include the <c>-noauth</c> |
| 368 |
flag to disable authorization checking, since you haven't added the admin user |
| 369 |
@@ -844,17 +810,17 @@ |
| 370 |
</pre> |
| 371 |
|
| 372 |
<p> |
| 373 |
-Verify that the BOS Server created <path>/usr/vice/etc/CellServDB</path> |
| 374 |
-and <path>/usr/vice/etc/ThisCell</path> |
| 375 |
+Verify that the BOS Server created <path>/etc/openafs/server/CellServDB</path> |
| 376 |
+and <path>/etc/openafs/server/ThisCell</path> |
| 377 |
</p> |
| 378 |
|
| 379 |
<pre caption="Check if CellServDB and ThisCell are created"> |
| 380 |
-# <i>ls -al /usr/vice/etc/</i> |
| 381 |
+# <i>ls -al /etc/openafs/server/</i> |
| 382 |
-rw-r--r-- 1 root root 41 Jun 4 22:21 CellServDB |
| 383 |
-rw-r--r-- 1 root root 7 Jun 4 22:21 ThisCell |
| 384 |
</pre> |
| 385 |
|
| 386 |
-</body> |
| 387 |
+</body> |
| 388 |
</section> |
| 389 |
<section> |
| 390 |
<title>Defining Cell Name and Membership for Server Process</title> |
| 391 |
@@ -894,8 +860,8 @@ |
| 392 |
<body> |
| 393 |
|
| 394 |
<p> |
| 395 |
-Next use the <c>bos create</c> command to create entries for the four database |
| 396 |
-server processes in the <path>/etc/openafs/BosConfig</path> file. The four |
| 397 |
+Next use the <c>bos create</c> command to create entries for the four database |
| 398 |
+server processes in the <path>/etc/openafs/BosConfig</path> file. The four |
| 399 |
processes run on database server machines only. |
| 400 |
</p> |
| 401 |
|
| 402 |
@@ -923,13 +889,21 @@ |
| 403 |
Very important :) |
| 404 |
</ti> |
| 405 |
</tr> |
| 406 |
-</table> |
| 407 |
+</table> |
| 408 |
|
| 409 |
<pre caption="Create entries for the database processes"> |
| 410 |
-# <i>bos create <server name> kaserver simple /usr/libexec/openafs/kaserver -cell <cell name> -noauth</i> |
| 411 |
-# <i>bos create <server name> buserver simple /usr/libexec/openafs/buserver -cell <cell name> -noauth</i> |
| 412 |
-# <i>bos create <server name> ptserver simple /usr/libexec/openafs/ptserver -cell <cell name> -noauth</i> |
| 413 |
-# <i>bos create <server name> vlserver simple /usr/libexec/openafs/vlserver -cell <cell name> -noauth</i> |
| 414 |
+# <i>bos create <server name> kaserver \ |
| 415 |
+simple /usr/libexec/openafs/kaserver \ |
| 416 |
+-cell <cell name> -noauth</i> |
| 417 |
+# <i>bos create <server name> buserver \ |
| 418 |
+simple /usr/libexec/openafs/buserver \ |
| 419 |
+-cell <cell name> -noauth</i> |
| 420 |
+# <i>bos create <server name> ptserver \ |
| 421 |
+simple /usr/libexec/openafs/ptserver \ |
| 422 |
+-cell <cell name> -noauth</i> |
| 423 |
+# <i>bos create <server name> \ |
| 424 |
+vlserver simple /usr/libexec/openafs/vlserver \ |
| 425 |
+-cell <cell name> -noauth</i> |
| 426 |
</pre> |
| 427 |
|
| 428 |
<p> |
| 429 |
@@ -995,7 +969,7 @@ |
| 430 |
</pre> |
| 431 |
|
| 432 |
<p> |
| 433 |
-Run the <c>bos adduser</c> command, to add the <b>admin</b> user to |
| 434 |
+Run the <c>bos adduser</c> command, to add the <b>admin</b> user to |
| 435 |
the <path>/etc/openafs/server/UserList</path>. |
| 436 |
</p> |
| 437 |
|
| 438 |
@@ -1004,7 +978,7 @@ |
| 439 |
</pre> |
| 440 |
|
| 441 |
<p> |
| 442 |
-Issue the <c>bos addkey</c> command to define the AFS Server |
| 443 |
+Issue the <c>bos addkey</c> command to define the AFS Server |
| 444 |
encryption key in <path>/etc/openafs/server/KeyFile</path> |
| 445 |
</p> |
| 446 |
|
| 447 |
@@ -1049,13 +1023,50 @@ |
| 448 |
system:administrators |
| 449 |
</pre> |
| 450 |
|
| 451 |
+</body> |
| 452 |
+</section> |
| 453 |
+<section> |
| 454 |
+<title>Properly (re-)starting the AFS server</title> |
| 455 |
+<body> |
| 456 |
+ |
| 457 |
+<p> |
| 458 |
+At this moment, proper authentication is possible, and the OpenAFS server can |
| 459 |
+be started in a normal fashion. Note that authentication also requires a |
| 460 |
+running OpenAFS client (set it up is described in the previous chapter). |
| 461 |
+<!-- Left out because deemed confusing> |
| 462 |
+Continuing without this step is possible, but in that case a quick restart of |
| 463 |
+the server is required, as demonstrated at the end of this section. |
| 464 |
+<--> |
| 465 |
+</p> |
| 466 |
+ |
| 467 |
+<pre caption="Shutdown bosserver"> |
| 468 |
+# <i>bos shutdown <server name> -wait -noauth</i> |
| 469 |
+# <i>killall bosserver</i> |
| 470 |
+</pre> |
| 471 |
+ |
| 472 |
+<pre caption="Normal OpenAFS server (and client) startup"> |
| 473 |
+# <i>/etc/init.d/openafs-server start</i> |
| 474 |
+# <i>/etc/init.d/openafs-client start</i> |
| 475 |
+</pre> |
| 476 |
+ |
| 477 |
+<pre caption="Adding AFS server to the default runlevel"> |
| 478 |
+# <i>rc-update add openafs-server default</i> |
| 479 |
+</pre> |
| 480 |
+ |
| 481 |
+<pre caption="Getting a token as the admin user"> |
| 482 |
+# <i>klog admin</i> |
| 483 |
+</pre> |
| 484 |
+ |
| 485 |
+<!-- Left out because deemed confusing> |
| 486 |
<p> |
| 487 |
-Restart all AFS Server processes |
| 488 |
+If you chose not to restart OpenAFS without the -noauth flag, you can simply |
| 489 |
+perform the following procedure instead: |
| 490 |
</p> |
| 491 |
|
| 492 |
<pre caption="Restart all AFS server processes"> |
| 493 |
# <i>bos restart <server name> -all -cell <cell name> -noauth</i> |
| 494 |
</pre> |
| 495 |
+<--> |
| 496 |
|
| 497 |
</body> |
| 498 |
</section> |
| 499 |
@@ -1064,18 +1075,18 @@ |
| 500 |
<body> |
| 501 |
|
| 502 |
<p> |
| 503 |
-Start the <c>fs</c> process, which consists of the |
| 504 |
-File Server, |
| 505 |
-Volume Server and Salvager (fileserver, |
| 506 |
-volserver and salvager processes). |
| 507 |
+Start the <c>fs</c> process, which consists of the File Server, Volume Server |
| 508 |
+and Salvager (fileserver, volserver and salvager processes). |
| 509 |
</p> |
| 510 |
|
| 511 |
<pre caption="Start the fs process"> |
| 512 |
-# <i>bos create <server name> fs fs /usr/libexec/openafs/fileserver /usr/libexec/openafs/volserver /usr/libexec/openafs/salvager -cell <cell name> -noauth</i> |
| 513 |
+# <i>bos create <server name> fs \ |
| 514 |
+fs /usr/libexec/openafs/fileserver /usr/libexec/openafs/volserver /usr/libexec/openafs/salvager \ |
| 515 |
+-cell <cell name> -noauth</i> |
| 516 |
</pre> |
| 517 |
|
| 518 |
<p> |
| 519 |
-Verify that all processes are running |
| 520 |
+Verify that all processes are running: |
| 521 |
</p> |
| 522 |
|
| 523 |
<pre caption="Check if all processes are running"> |
| 524 |
@@ -1114,14 +1125,19 @@ |
| 525 |
</p> |
| 526 |
|
| 527 |
<p> |
| 528 |
-If you are installing the first AFS Server ever in the cell create the |
| 529 |
-first AFS volume, <b>root.afs</b> |
| 530 |
+If you are installing the first AFS Server ever in the cell, create the first |
| 531 |
+AFS volume, <b>root.afs</b> |
| 532 |
</p> |
| 533 |
|
| 534 |
<note> |
| 535 |
For the partition name argument, substitute the name of one of the machine's |
| 536 |
-AFS Server partitions. By convention |
| 537 |
-these partitions are named <path>/vicepx</path>, where x is in the range of a-z. |
| 538 |
+AFS Server partitions. Any filesystem mounted under a directory called |
| 539 |
+<path>/vicepx</path>, where x is in the range of a-z, will be considered and |
| 540 |
+used as an AFS Server partition. Any unix filesystem will do (as opposed to the |
| 541 |
+client's cache, which can only be ext2/3). Tip: the server checks for each |
| 542 |
+<path>/vicepx</path> mount point whether a filesystem is mounted there. If not, |
| 543 |
+the server will not attempt to use it. This behaviour can be overridden by |
| 544 |
+putting a file named <path>AlwaysAttach</path> in this directory. |
| 545 |
</note> |
| 546 |
|
| 547 |
<pre caption="Create the root.afs volume"> |
| 548 |
@@ -1145,7 +1161,7 @@ |
| 549 |
|
| 550 |
<pre caption="Synchronise the VLDB"> |
| 551 |
# <i>vos syncvldb <server name> -cell <cell name> -verbose -noauth</i> |
| 552 |
-# <i>vos syncserv <server name> -cell <cell name> -verbose -noauth</i> |
| 553 |
+# <i>vos syncserv <server name> -cell <cell name> -verbose -noauth</i> |
| 554 |
</pre> |
| 555 |
|
| 556 |
</body> |
| 557 |
@@ -1155,9 +1171,9 @@ |
| 558 |
<body> |
| 559 |
|
| 560 |
<pre caption="Start the update server"> |
| 561 |
-# <i>bos create <server name> |
| 562 |
-upserver simple "/usr/libexec/openafs/upserver |
| 563 |
--crypt /etc/openafs/server -clear /usr/libexec/openafs" |
| 564 |
+# <i>bos create <server name> \ |
| 565 |
+upserver simple "/usr/libexec/openafs/upserver \ |
| 566 |
+-crypt /etc/openafs/server -clear /usr/libexec/openafs" \ |
| 567 |
-cell <cell name> -noauth</i> |
| 568 |
</pre> |
| 569 |
|
| 570 |
@@ -1172,6 +1188,16 @@ |
| 571 |
<path>/afs</path>. |
| 572 |
</p> |
| 573 |
|
| 574 |
+<note> |
| 575 |
+The default OpenAFS client configuration has <b>dynroot</b> enabled. |
| 576 |
+This option turns <path>/afs</path> into a virtual directory composed of the |
| 577 |
+contents of your <path>/etc/openafs/CellServDB</path> file. As such, the |
| 578 |
+following command will not work, because it requires a real AFS directory. |
| 579 |
+You can temporarily switch dynroot off by setting <b>ENABLE_DYNROOT</b> to |
| 580 |
+<b>no</b> in <path>/etc/conf.d/openafs-client</path>. Don't forget to issue |
| 581 |
+a client after changing parameters. |
| 582 |
+</note> |
| 583 |
+ |
| 584 |
<pre caption="Set access control lists"> |
| 585 |
# <i>fs setacl /afs system:anyuser rl</i> |
| 586 |
</pre> |
| 587 |
@@ -1183,12 +1209,19 @@ |
| 588 |
</p> |
| 589 |
|
| 590 |
<pre caption="Prepare the root volume"> |
| 591 |
-# <i>vos create <server name><partition name> root.cell</i> |
| 592 |
-# <i>fs mkmount /afs/<cell name> root.cell </i> |
| 593 |
+# <i>vos create <server name> <partition name> root.cell</i> |
| 594 |
+# <i>fs mkmount /afs/<cell name> root.cell</i> |
| 595 |
# <i>fs setacl /afs/<cell name> system:anyuser rl</i> |
| 596 |
# <i>fs mkmount /afs/.<cell name> root.cell -rw</i> |
| 597 |
</pre> |
| 598 |
|
| 599 |
+<pre caption="Adding volumes underneath"> |
| 600 |
+# <i>vos create <server name> <partition name> <myvolume></i> |
| 601 |
+# <i>fs mkmount /afs/<cell name>/<mymountpoint> <myvolume></i> |
| 602 |
+# <i>fs mkmount /afs/<cell name>/.<mymountpoint> <myvolume> -rw</i> |
| 603 |
+# <i>fs setquota /afs/<cell name>/.<mymountpoint> -max <quotum></i> |
| 604 |
+</pre> |
| 605 |
+ |
| 606 |
<p> |
| 607 |
Finally you're done!!! You should now have a working AFS file server |
| 608 |
on your local network. Time to get a big |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
-- |
| 613 |
gentoo-doc-cvs@g.o mailing list |
Archives