The server of NFS: serveNfs hosts the service of a store on a TCP socket of the loopback (the NFS program and the mount protocol on the same port, which a mount names with port= and mountport=), reads the records of each connection, answers them in order, and bounds what a caller can make it hold: the connections, the size of a record and (in the service) the handles and the size of an object. It does not listen on any other address than the loopback, and it puts every buffer that holds a write when it is closed.
typeServeNfsOptions=NfsOptions& {
/** The port; 0 asks for a free one. */readonlyport?:number;
/** The most connections at once: 16 by default. */readonlymaxConnections?:number;
/** The policy of the view; empty directories are kept as `.keep` objects by default, so that a directory made persists. */readonlypolicy?:Policy;
};
What the server is told besides what the service is.
type NfsServing = {
readonly port: number;
readonly hostname: string;
/** How the boot of this server writes itsel…(574 characters)
typeNfsServing= {
readonlyport:number;
readonlyhostname:string;
/** How the boot of this server writes itself: the write verifier. */readonlyboot:Uint8Array;
/** The command that mounts the export on a Linux computer (`mount -t nfs`): the port is named, so that no portmapper is needed. */mountCommand(directory:string):string;
/** How many attributes were accepted without effect. */dropped():number;
/** Puts what is held, stops listening and ends the connections. The failures to put are given. */close():Promise<readonlystring[]>;
};