There are two major concerns regarding client and server machine failures:
When a client application is terminated with a <control-c> or 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.
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 crash are left in an unknown state and may be corrupt. If acuconnect is automatically started when the server boots, acuconnect should be immediately halted. Before AcuConnect is started, all files that might have been affected by the crash should be checked and, if necessary, rebuilt. After all files have been verified, the acuconnect daemon can be started.