Two major concerns regarding client and server machine failures are:
When a client application or connection is terminated with Ctrl+C or a kill command (other than a kill -9), AcuConnect detects the termination and closes all files/programs held open for that client process. However, other terminal software and hardware failures are not detected. Note that although files are not broken when you use this command, they may not be consistent. If a child runtime is terminated between two file updates that are both required for consistency, the runtime shuts down between them.
Should the server go down, all clients actively using AcuConnect get access errors when attempting to communicate with the server. Client systems must terminate their current applications and wait for the return of the server. All files that were open on the server at the time of the termination are left in an unknown state and may be corrupt.
Before you start AcuConnect, you should check all files that might have been affected by the termination and, if necessary, rebuild them. After you have verified all files, you can start the acurcl daemon.
To view an AcuConnect system status report, issue the acurcl -info command. In Windows, you can use the graphical control panel's Info tab to check the status of active child runtimes. Click Query to select a server/port combination and list the child processes running on the selected server.