Previous Up Next
Previous Up Next
If the execution of any of the jobs fail for any reason or the dispatcher
is prematurely terminated, then some of the jobs might not be completed.
enfpurge allows you to create a run file which contains only
jobs that have not been executed successfully.
During execution, the Dispatcher creates a log file
containing information which jobs have been successfully completed.
enfpurge takes a run file and its log and produces on standard
output a run file which contains only jobs that have not been completed.
The new run file can be used as a parameter to Dispatcher to
execute remaining jobs.
The syntax of the enfpurge utility is:
enfpurge "input_run" "log_file" > "output_run"
The following command line will take the run file first.run and
the log in enfuzion.log and generate a new run file named
next.run:
enfpurge first.run enfuzion.log > next.run
Node servers automatically terminate the child processes and clean up the used disk space when jobs terminate. This happens immediately after a normal Dispatcher termination, or up to 5 minutes after a forced Dispatcher termination by pressing CTRL-C, CTRL-BREAK or ending process using the Task Manager.
However there are some rare conditions, when the node cleanup operation might not occur:
For such conditions, the enfkill.exe, an additional command line utility
has been designed. The program kills tasks running on
enFuzion nodes, and cleans up the node workspace directories.
enfkill allows you to kill all running jobs and delete all
temporary working files and subdirectories on enFuzion Nodes. Installation
of enFuzion executables and other permanent enFuzion files is not influenced
by enfkill.
enfkill is not implemented on Unix platforms.
enfkill requires enFuzion Node configuration in file
"enfuzion.nodes" in the current working directory. If enfkill
is executed from the same directory as the Dispatcher, it
will clean up all the nodes started by the Dispatcher.
When executed, enfKill reads the 'enfuzion.nodes' file from the current directory, logs on all the specified nodes, kills all user tasks and deletes the enFuzion temporary files.
'enfKill' does not imply any constraints on which tasks to terminate on the nodes. You must use extreme care when performing the kill operation.
If, for example, a user is interactively logged on the machine and the enfkill operation is performed on the same machine with the same user name and password, all user's applications will terminate immediately without letting the user save his work.
Therefore it is strongly recommended to create a special account for running enFuzion nodes on each computer in order to use the enfkill program safely.
enfkill has no command line parameters. It is run simply by:
enfkill
For security purposes the enfKill program has been designed not to
terminate any program if run by an Administrator node account.
The Dispatcher creates a log file, describing execution progress.
The loghtml utility converts such a log file into a standard HTML
format. The result can be viewed
with standard Internet browsers, such as Netscape or Explorer.
loghtml is especially useful, when the Dispatcher is executed
in the batch mode.
loghtml takes as a parameter a log file, produced by the
Dispatcher. The resulting HTML page is available on standard output.
loghtml is executed by:
loghtml <log_file>
An example:
loghtml enfuzion.log > enfuzion.html
File enfuzion.html can be viewed using a standard Internet
browser, such as Netscape or Explorer. You can monitor the execution
progress by repeatedly running the loghtml utility and
reloading the resulting HTML page in your browser.