Changes between Version 5 and Version 6 of Public/Docs/CAEConfigChange

Timestamp:

Dec 16, 2019, 2:30:28 PM (5 years ago)

Author:

Administrator

Comment:

—

Public/Docs/CAEConfigChange

@@ -44 +44 @@
 again will show you whether {{{supervise}}} has successfully restarted CAE.
 
+== Stopping CAE
+You might want to stop CAE for one of the following reasons:
+* To start it by hand with active console logging and debug any unwanted behaviour CAE has shown in unattended mode. 
+* To run CAE in the debugger on a development system. 
+
+In both cases, you must stop the supervised CAE on the server to avoid interference with your second instance of the program.
+
+Stopping CAE works similarly as restarting CAE. Using the {{{kill}}} command on the CAE process stopped it and caused {{{supervise}}} to restart it. To stop CAE, therefore, first {{{supervise}}} must be stopped.
+
+Use the following commands to retrieve the process ids for {{{supervise}}} and CAE. Then use the following commands:
+{{{
+ps aux | grep supervise
+kill <supervise process id>
+ps aux | grep mono
+kill <mono process id>
+}}}