[Fluent Inc. Logo] return to home search
next up previous contents index

1.5 Cleaning Up Processes From a FLUENT Simulation

FLUENT lets you easily remove extraneous processes in the event that a FLUENT simulation needs to be stopped.

When a session is started, FLUENT creates a kill-fluent script file. The script can be used to cleanly kill all FLUENT-related processes. FLUENT creates the kill-script file in the current working directory with a file name that includes the machine name and the process identification number (PID) (e.g., kill-fluent-mymachine-1234).

On UNIX and Linux platforms, if the current directory does not possess the proper write permissions, then FLUENT will write the kill-script file to your home directory.

On Windows, if the current directory does not possess the proper write permissions, FLUENT will save the kill-script file to a different directory (i.e., %APPDATA%/Fluent.Inc where it is assumed that the APPDATA environment variable is already defined). The Fluent.Inc directory will be created if it is not already present.

If, for example, FLUENT is started on a machine called thor and the process identification number is 32895, FLUENT will create a kill-script called kill-fluent-thor-32895 in the current directory. To run the kill-script, and kill all FLUENT processes related to your session, on Linux or UNIX platforms, type the following command in the console window:

  sh kill-fluent-thor-32895

Or, if the shell script already has executable permissions, simply type:

  kill-fluent-thor-32895

To clean up extraneous FLUENT processes on Windows, double-click the corresponding batch file (e.g., kill-fluent-thor-32895.bat) that FLUENT generates at the beginning of each session.

figure   

Once a FLUENT session has been closed, you can safely delete any left over kill scripts from your working directory.


next up previous contents index Previous: 1.4 Checkpointing a FLUENT
Up: 1. Starting and Executing
Next: 1.6 Exiting the Program
© Fluent Inc. 2006-09-20