Cluster: Timeout inline

Version 1.60.2

Bugfix
Finished

If a remote server happens to be down, previously, the entire action would have waited until the usual 60 second DA timeout. By default, the cluster (Multi-Server Setup) has a 5 second timeout, however, although it was triggering the signal/hook, that hook was stepping out of the sequence. Fix was to use the set flag, and when the process returned to the connect/transfer section, the process would abort, instead of trying to move forward, hanging for the full 60s. Now, should the remote box be down, the proper 5s timeout will now work (for the connection part), and abort accordingly. User creation, deletion, and Admin record adding/deletion will also include a bold message embedded in the success result about the downed remote IP. ---- T22044

Interested to try DirectAdmin? Get a 30-day Free Trial!