Oexportfs is older version of the exportfs(4) program that handles
an initial protocol to establish a root directory for the exported
name space. It also provides authentication and encryption using
the ssl(3) device. |
It is used exclusively by the deprecated cpu(1) and import(4)
The options are:
–d –f dbgfile
Log all 9P traffic to dbgfile (default /tmp/exportdb).|
R Make the served name space read only.
Restrict the set of exported files. Patternfile contains one regular
expression per line, to be matched against path names relative
to the current working directory and starting with /. For a file
to be exported, all lines with a prefix + must match and all those
with prefix – must not match.
Serve the name space rooted at root.|
s equivalent to –r /; kept for compatibility.
Serve the result of mounting service. A separate mount is used
for each attach(5) message, to correctly handle servers in which
each mount corresponds to a different client e.g.,( rio(4)).|
Set the maximum message size that oexportfs should offer to send
(see version(5)); this helps tunneled 9P connections to avoid
a Authenticate the user with the p9any protocol before running
the regular oexportfs session; used when oexportfs is invoked
to handle an incoming network connection. Exportfs creates a new
name space for each connection, using /lib/namespace by default
Use the network address to announce aan(8) connections, if requested
by the initial protocol.|
e 'enc auth'
Dial address, authenticate as a p9any client, and then serve that
network connection. Requires setting the root of the name space
with –r or –s. The remote system should run import –B to handle the
call. See import(4) for an example.|
Set the encryption and authentication algorithms to use for encrypting
the wire traffic (see ssl(3)). The defaults are rc4_256 and sha1.|
n Disallow mounts by user none.
Serve the name space described by nsfile.|