Initializes the Fileset Location (FL) Server
Synopsis
flserver [-adminlist filename] [-verbose] [-help]
Options
-adminlist filename
Specifies the administrative list file that contains principals and groups authorized to execute flserver RPCs (usually using fts
commands). If this option is omitted, the flserver process uses the default administrative list file, dcelocal/var/dfs/admin.fl.
-verbose
Directs the flserver process to provide a detailed report on what it is doing by displaying messages on standard error.
-help
Prints the online help for this command. All other valid options specified with this option are ignored.
The help and apropos commands available with all command suites are also available with the flserver command. See the bos help and bos apropos reference pages for examples of using these commands.
Description
The Fileset Location (FL) Server maintains the Fileset Location Database (FLDB), which tracks the location of all DCE LFS and non-LFS filesets. The FL Server, or
flserver process, must run on all Fileset Database machines. It is usually started and controlled by the BOS Server; if it is not, execute the flserver process as a background
process. The binary file for the flserver process resides in dcelocal/bin/flserver.
The first time it is initialized, the flserver process creates the FLDB files in dcelocalvar/dfs; all FLDB files have a root name of fldb. The flserver process also creates the dcelocal/var/dfs/admin.fl administrative list file if the file does not already exist.
The principals and members of groups in the admin.fl administrative list are authorized to issue commands to create server entries and fileset entries in the FLDB. The list must also include the abbreviated DFS server principals of all Fileset Database machines to allow for the proper distribution of changes via the Ubik database synchronization mechanism. Because the FLDB is a replicated database, the admin.fl administrative lists for all flserver processes in a cell must contain the same principals and groups.
In addition, when the flserver process is first initialized, it makes a ubik_ServerInit call to register its existence as a server process with the Ubik coordinator. It then listens for incoming RPCs to which to respond.
Each time it is started, the flserver process creates the dcelocal/var/dfs/adm/FlLog event log file if the file does not already exist. It then appends messages to the file. If the file exists when the flserver process is started, the process moves it to the FlLog.old file in the same directory (overwriting the current FlLog.old file if it exists) before creating a new version to which to append messages.
Privilege Required
The issuer must be logged in as root on the local machine.
Output
If problems are encountered during initialization, the flserver process displays error messages on standard error output. The flserver process keeps an
event log in the file dcelocal/var/dfs/adm/FlLog.
If run with the -verbose option, the flserver process provides a detailed report on what it is doing by displaying messages on standard error.
Related Information
Files: admin.fl(4dfs)