next up previous contents index
Next: Error Code Summary Up: The OSFriends Interface Previous: Manipulating Logical Volumes

More Taos-only File-System Operations

  The procedures in this section do not have Ultrix implementations.

 

PROCEDURE StartRFS(
    dir: Dir;
    path: PathName;
    instance: Text.T := NIL)
  RAISES {Error};(* NotSuperUserEC, ... *)

  StartRFS exports an instance of the RFS interface with the specified instance name so that the files on the caller's machine can be used from other machines. If instance is NIL, the machine name is used. The path name specifies a log file, which StartRFS opens for appending. StartRFS raises NotSuperUserEC unless the caller is the super-user.

 

PROCEDURE SetRootDir(dir: Dir; path: PathName) RAISES {Error};

  SetRootDir sets the root of the local file system to the directory with the specified path name. For this to work properly, the directory must be the root of some file system, possibly remote. This changes the value of root for all local file accesses in the system, but not for an RFS server running on this machine. A remote path name with an explicit <machine> part--such as #srcf34/--can be used to change the root back to the local system. SetRootDir raises NotSuperUserEC unless the caller is the super-user.

     

PROCEDURE GetConfigurationParameter(name: Text.T): Text.T
  RAISES {Error}; (* LookUpEC *)

PROCEDURE SetConfigurationParameter(
    name: Text.T;
    value: Text.T)
  RAISES {Error}; (* LookUpEC, NotSuperUserEC, InvalidArgumentEC *)

PROCEDURE NextConfigurationParameter(name: Text.T): Text.T
  RAISES {}; (* LookUpEC *)

  These procedures get, set, and enumerate operating-system configuration parameters. If the value of a particular parameter is not printable, it consists of the characters `!!Pickle!!' prefixed to a pickle (see the Pickle interface). All three procedures raise LookUpEC to report that there is no parameter with the specified name. SetConfigurationParameter raises NotSuperUserEC unless it is called by the super-user, and raises InvalidArgumentEC if the the parameter is read-only or the specified value has the wrong type for that parameter. Pass NIL to NextConfigurationParameter to begin an enumeration; a NIL result indicates the end. The names, types, and meaning of the configuration parameters are implementation-dependent and subject to change with little notice; the currently defined parameters are:

    Read-  
Name Type only? Description
OpenFiles CARDINAL No Number of open files to keep in memory even after they have been closed
InfoRecords CARDINAL No Number of info records kept for unopened files
RemoteDirPrefix Text.T No String to use as the prefix to the instance name to find the directory to be used as the parent of a remote root
CacheEntries CARDINAL Yes Number of LocalFile read-cache entries
EntryBlocks CARDINAL Yes Number of 512-byte blocks per cache entry
ReadEntryLimit CARDINAL Yes Maximum number of entries for reads that go through the cache
WriteEntryLimit CARDINAL Yes Maximum number of cache entries to update for a write
WriteBlocks CARDINAL Yes Number of blocks in the write buffer
WriteDescs CARDINAL Yes Number of elements in the write descriptor queue

END OSFriends.


next up previous contents index
Next: Error Code Summary Up: The OSFriends Interface Previous: Manipulating Logical Volumes
Paul McJones
8/28/1997