Translations by Thomas Reitelbach

<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>

Options

<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>

<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>

<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>

<b>All squash</b> <p> Map all uids and gids to the anonymous user. Useful for NFS-exported public FTP directories, news spool directories, etc. </p>

<b>No root squash</b> <p> Turn of root squashing. This option is mainly useful for diskless clients. </p> <i>root squashing</i> <p> Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does not apply to any other uids that might be equally sensitive, such as user bin. </p>

<b>Anonym. UID/GID</b> <p> These options explicitly set the uid and gid of the anonymous account. This option is primarily useful for PC/NFS clients, where you might want all requests appear to be from one user. </p>

Here you can see a list of hosts which are allowed to access this directory via NFS. The first column shows the name or address of the host, the second column shows the access parameters. The name '*' donates public access.

&OK

&Cancel

This is a username which will be used for access to services which are specified as guest ok. Whatever privileges this user has will be available to any client connecting to the guest service. Typically this user will exist in the password file, but will not have a valid login. The user account \"ftp\" is often a good choice for this parameter. If a username is specified in a given service, the specified username overrides this one.

The opposite of hosts allow - hosts listed here are NOT permitted access to services unless the specific services have their own lists to override this one. Where the lists conflict, the allow list takes precedence.

Allow following of symbolic links that &point to areas outside the directory tree

Directory security mask:

Inherit ac&ls

&NT ACL support

Map DOS archi&ve to UNIX owner execute

Map DOS hidden to UNI&X world execute

Use sen&dfile

Client-side cachin&g policy:

Preser&ve case

Case sensi&tive

Yes

No

S&trict locking

Root pr&eexec:

Root &postexec:

root pree&xec close

Misc

Mag&ic output:

Msdfs pro&xy

Setdir command allo&wed

Ms&dfs root

&Help

<qt> Here you can edit the Samba users, stored in the smbpasswd file. <p> Every Samba user must have a corresponding UNIX user. On the right you can see all UNIX users, stored in the passwd file and not configured as Samba users. You can see the Samba users on the left-hand side. <p> To add new Samba users simply press the <em>&lt; add</em> button. The selected UNIX users will then become Samba users and will be removed from the UNIX users list (but they will remain UNIX users). <p> To remove Samba users click the <em>&gt; remove</em> button. The selected Samba users will be removed from the smbpasswd file and reappear on the right-hand side, as UNIX users which are not Samba users. </qt>

Samba config file:

Help

For detailed help about every option please look at:

Properties

Add

Chan&ge Password...

Root director&y:

Algorithmic rid base:

Passdb bac&kend: