Browsing Norwegian Nynorsk translation

3.

<b>Name / Address field</b>
<p>
Here you can enter the host name or address.<br>
The host may be specified in a number of ways:
<p>
<i>single host</i>
<p>
This is the most common format. You may specify a host either by an abbreviated name recognized by the resolver, the fully qualified domain name, or an IP address.
</p>

<i>netgroups</i>
<p>
NIS netgroups may be given as @group. Only the host part of each netgroup members is consider in checking for membership. Empty host parts or those containing a single dash (-) are ignored.
</p>

<i>wildcards</i>
<p>
Machine names may contain the wildcard characters * and ?. This can be used to make the exports file more compact; for instance, *.cs.foo.edu matches all hosts in the domain cs.foo.edu. However, these wildcard characters do not match the dots in a domain name, so the above pattern does not include hosts such as a.b.cs.foo.edu.
</p>

<i>IP networks</i>
<p>
You can also export directories to all hosts on an IP (sub-) network simultaneously. This is done by specifying an IP address and netmask pair as address/netmask where the netmask can be specified in dotted-decimal format, or as a contiguous mask length (for example, either `/255.255.252.0' or `/22' appended to the network base address result in identical subnetworks with 10 bits of host).
</p>

5.

<b>Public access</b>
<p>
If you check this, the host address will be a single wildcard , which means public access.
This is just the same as if you would enter a wildcard in the address field.
</p>

6.

Options

8.

<b>Writable</b>
<p>
Allow both read and write requests on this NFS volume.
</p>
<p>
The default is to disallow any request which changes the filesystem
</p>

10.

<b>Insecure</b>
<p>
If this option is checked, it is not required that requests originate on an internet port less than IPPORT_RESERVED (1024).
</p>
<p>
If unsure leave it unchecked.
</p>

12.

<b>Sync</b>
<p>
This option requests that all file writes be committed to disk before the write request completes. This is required for complete safety of data in the face of a server crash, but incurs a performance hit.
</p>
<p>
The default is to allow the server to write the data out whenever it is ready.
</p>

14.

<b>No wdelay</b>
<p>
This option only has effect if sync is also set. The NFS server will normally delay committing a write request to disk slightly if it suspects that another related write request may be in progress or may arrive soon. This allows multiple write requests to be committed to disk with the one operation which can improve performance. If an NFS server received mainly small unrelated requests, this behavior could actually reduce performance, so no wdelay is available to turn it off. </p>

16.

<b>No hide</b>
<p>
This option is based on the option of the same name provided in IRIX NFS. Normally, if a server exports two filesystems one of which is mounted on the other, then the client will have to mount both filesystems explicitly to get access to them. If it just mounts the parent, it will see an empty directory at the place where the other filesystem is mounted. That filesystem is "hidden".
</p>
<p>
Setting the nohide option on a filesystem causes it not to be hidden, and an appropriately authorized client will be able to move from the parent to that filesystem without noticing the change.
</p>
<p>
However, some NFS clients do not cope well with this situation as, for instance, it is then possible for two files in the one apparent filesystem to have the same inode number.
</p>
<p>
The nohide option is currently only effective on single host exports. It does not work reliably with netgroup, subnet, or wildcard exports.
</p>
<p>
This option can be very useful in some situations, but it should be used with due care, and only after confirming that the client system copes with the situation effectively.
</p>

18.

<b>No subtree check</b>
<p>
This option disables subtree checking, which has mild security implications, but can improve reliability is some circumstances.
</p>
<p>
If a subdirectory of a filesystem is exported, but the whole filesystem is not, then whenever a NFS request arrives, the server must check not only that the accessed file is in the appropriate filesystem (which is easy) but also that it is in the exported tree (which is harder). This check is called the subtree_check.
</p>
<p>
In order to perform this check, the server must include some information about the location of the file in the "filehandle" that is given to the client. This can cause problems with accessing files that are renamed while a client has them open (though in many simple cases it will still work).
</p>
<p>
subtree checking is also used to make sure that files inside directories to which only root has access can only be accessed if the filesystem is exported with no_root_squash (see below), even the file itself allows more general access.
</p>
<p>
As a general guide, a home directory filesystem, which is normally exported at the root and may see lots of file renames, should be exported with subtree checking disabled. A filesystem which is mostly read-only, and at least does not see many file renames (e.g. /usr or /var) and for which subdirectories may be exported, should probably be exported with subtree checks enabled.
</p>

20.

<b>Insecure locks</b>
<p>
This option tells the NFS server not to require authentication of locking requests (i.e. requests which use the NLM protocol). Normally the NFS server will require a lock request to hold a credential for a user who has read access to the file. With this flag no access checks will be performed.
</p>
<p>
Early NFS client implementations did not send credentials with lock requests, and many current NFS clients still exist which are based on the old implementations. Use this flag if you find that you can only lock files which are world readable.
</p>