This section gives an overall view of the EnFuzion environment on a root host. It describes the use of user accounts, the layout of directories on the root, the executables required and EnFuzion configuration files.
EnFuzion root processes execute under the same user account on the EnFuzion root system. Any user account on the root system can be used to execute EnFuzion root processes. EnFuzion does not impose any requirements on the user account.
If EnFuzion is used locally in a single run mode, then it is usually executed under the local user account.
If EnFuzion is used as a server with many users and executes on a remote system, it is recommended that a special user account is created for the EnFuzion root processes on that system.
The working directory of the Dispatcher is the main root directory. This directory contains the Dispatcher log file, called enfuzion.log , the internal Dispatcher directory enfinfo and any additional working files supplied by the user or created during execution. Configuration files can also be placed in this directory.
The enfinfo directory contains internal files, which are produced by the Dispatcher and required for its operation. An important subdirectory is acct, which contains the data to produce the accounting reports. If this subdirectory is deleted, then the accounting data is lost and reports will be empty.
For each run, the Dispatcher creates a subdirectory in the main root directory, called run-<run_id>. This subdirectory contains a run specific log, called enfuzion-run.log, and any run specific files, which can be temporary working files, user input files and job output files. The subdirectory also contains files that are required to restart a run.
If a run directory is not explicitly deleted by the user after the run completes, the directory is declared obsolete and it is deleted from the Dispatcher working directory. This automatic deletion prevents the accumulation of completed run directories. By default, a directory is declared obsolete 7 days after the run finishes. This default behavior can be changed through the root option ENFCLEANUP_LIMIT as described in the Section called Deleting Obsolete User Directories in Chapter 6.
Root executables must be in the path accessible to the Dispatcher. The following executables are provided by EnFuzion distribution packages on the root:
enfacct, the shell script that starts enfacct.bin;
enfacct.bin, the program for collecting accounting information;
enfauth, a dynamic library used for authentication;
enfcmd, the program that provides a command line user interface to the Dispatcher;
enfdispatcher, the central program;
enfecho, a system independent echo utility for use in tasks;
enfexecute, the program that provides EnFuzion commands in any scripting language;
enfeye, the shell script that starts enfeye.bin;
enfeye.bin, the program that provides a web based user interface to the Dispatcher;
enfgenerator, the program for converting plan files to run files;
enfinstall, the Linux/Unix network installation program;
enfjobdaemon, the program that executes job requests from nodes;
enfjobmanager, the program that executes rootstart and rootfinish tasks;
enfkey, the program for generating public and private keys for root authentication;
enfmail, the program to send a message to an SMTP server;
enfnodemanager, the program that handles communication with nodes;
enfnodestarter, the program that starts nodes;
enfpreparator, the program for generating plan files;
enfprotectpass, the program for encoding clear text passwords in enfuzion.nodes;
enfpurge, the program for removing completed jobs from run files, if the Dispatcher fails unexpectedly;
enfreport, the shell script that starts enfreport.bin;
enfreport.bin, the program for generating accounting reports in text;
enfrm, a system independent file deletion utility for use in tasks;
enfsub, the program for submitting runs for execution;
libglib*, a dynamic library used by the Eye.
On Windows, some of the programs are part of the enfdispatcher.exe executable.
The following configuration files are used by EnFuzion on the root:
admins, a list of users with administrative rights;
enfuzion.nodes, a description of nodes;
enfuzion.pkey, a root authentication file created by the EnFuzion provided enfauth library;
groups, a list of groups with their members;
root.options, root configuration options;
users, mappings to change default user assignments;
user.accounts, permitted user accounts on nodes.