---
name: "sfsrwsd_config"
section: "5"
platform: "linux"
package: "sfs-server"
version: "1:0.8-0+pre20060720.1-1"
release: "Debian 4.0 (Etch)"
platforms: ["linux"]
url: "https://new.carta.tech/sfsrwsd_config"
---

# sfsrwsd\_config(5)

file server configuration

## NAME

sfsrwsd\_config - file server configuration

## DESCRIPTION

- Hostname *name*

  Set the *Location* part of the server's self-certifying pathname. The default is the current host's fully-qualified hostname.

- Keyfile *path*

  Tells **sfsrwsd** to look for its private key in file *path*. The default is *sfs\_host\_key*.  SFS looks for file names that do not start with */* in */etc/sfs*, or whatever directory you specified if you used the **-with-etcdir** option to **configure** ().

- Export *local-directory* *sfs-name* \[R\|W\]

  Tells **sfsrwsd** to export *local-directory*, giving it the name *sfs-name* with respect to the server's self-certifying pathname.  Appending **R** to an export directive gives anonymous users read-only access to the file system under the anonymous user group IDs specified in *sfs\_config*. (See the description of the **anonuser** directive in the *sfs\_config* man page for more information .) Appending **W** gives anonymous users both read and write access. See the *Quick server setup* section of the SFS info pages for an example of the **Export** directive.

  There is almost no reason to use the **W** flag.  The **R** flag lets anyone on the Internet issue NFS calls to your kernel as the anonymous user.  SFS filters these calls; it makes sure that they operate on files covered by the export directive, and it blocks any calls that would modify the file system.  This approach is safe given a perfect NFS3 implementation.  If, however, there are bugs in your NFS code, attackers may exploit them if you have the **R** option--probably just crashing your server but possibly doing worse.

- LeaseTime *seconds*

  Specifies the amount of time for which SFS clients can cache file attributes.  During this period, if a file is modified, the server will call back to the client to let it know that the file's attributes have changed.  Unfortunately, if a file is modified not through SFS (e.g., through the local file system interface on the server), the server may not realize the attributes have changed, and clients may see stale data for the lease period.  The default lease term is 60 seconds.

## FILES

- */etc/sfs/sfsrwsd\_config*

  - */usr/local/share/sfs/sfsrwsd\_config*

  file server configuration

(Files in */etc/sfs* supersede default versions in */usr/local/share/sfs*.)

## SEE ALSO

[*dirsearch*(1)](/dirsearch/1.md), [*newaid*(1)](/newaid/1.md), [*rex*(1)](/rex/1.md), [*sfsagent*(1)](/sfsagent/1.md), [*sfskey*(1)](/sfskey/1.md), [*ssu*(1)](/ssu/1.md), *sfs\_config*(5), [*sfs\_hosts*(5)](/sfs_hosts/5.md), [*sfs\_srp\_params*(5)](/sfs_srp_params/5.md), [*sfs\_users*(5)](/sfs_users/5.md), [*sfsauthd\_config*(5)](/sfsauthd_config/5.md), [*sfscd\_config*(5)](/sfscd_config/5.md), *sfsrosd\_config*(5), [*sfssd\_config*(5)](/sfssd_config/5.md), [*sfs\_environ*(7)](/sfs_environ/7.md), [*funmount*(8)](/funmount/8.md), *nfsmounter*(8), [*sfsauthd*(8)](/sfsauthd/8.md), [*sfscd*(8)](/sfscd/8.md), *sfsrosd*(8), *sfsrwcd*(8), [*sfsrwsd*(8)](/sfsrwsd/8.md), [*sfssd*(8)](/sfssd/8.md), [*vidb*(8)](/vidb/8.md)

The full documentation for **SFS** is maintained as a Texinfo manual.  If the **info** and **SFS** programs are properly installed at your site, the command **info SFS** should give you access to the complete manual.

For updates, documentation, and software distribution, please see the **SFS** website at *http://www.fs.net/*.

## AUTHOR

sfsdev@redlab.lcs.mit.edu