Node:sfscd_config,
Previous:sfs_srp_params,
Up:SFS configuration
sfscd_config--Meta-client configurationThe sfscd_config is really part of the SFS protocol
specification. If you change it, you will no longer be executing the
SFS protocol. Nonetheless, you need to do this to innovate, and SFS was
designed to make implementing new kinds of file systems easy.
sfscd_config takes the following directives:
Extension string
sfscd should send string to all servers
to advertise that it runs an extension of the protocol. Most servers
will ignore string, but those that support the extension can
pass off the connection to a new "extended" server daemon. You can
specify multiple Extension directives.
Protocol name daemon [arg ...]
/sfs/name:anything should be handled by the
client daemon daemon. name may not contain any
non-alphanumeric characters. The Protocol directive is useful
for implementing file systems that are not mounted on self-certifying
file systems.
Release {* | sfs-version}
* signifies arbitrarily large SFS
release numbers. The Release directive does not do anything on
its own, but applies to all subsequent Program directives until
the next Release directive.
Libdir path
/. The default is
/usr/local/lib/sfs-0.6. The Libdir directive
does not do anything on its own, but applies to all subsequent
Program directives until the next Libdir or Release
directive.
Program prog.vers daemon [arg ...]
Program directive must be preceded by a Release directive.
The default sfscd_config file is:
Release * Program 344444.3 sfsrwcd
To run a different set of daemons when talking to sfs-0.3 or older
servers, you could add the following lines:
Release 0.3 Libdir /usr/local/lib/sfs-0.3 Program 344444.3 sfsrwcd