Improvements to Acquiring Lock File

[Martinski4GitHub]

Code improvements when the script is trying to obtain a lock file by allowing a 2nd instance to wait for the 1st instance to perform its job and exit. This means that 2 or more instances could execute in a staggered pattern and not terminate immediately when a lock file is found.

[Martinski4GitHub]

@ExtremeFiretop,

Please review & test this PR when you get a chance.

Essentially, the way the "_AcquireLock_" function works now is that it allows any secondary instances while the current process is executing to wait for a 120-sec maximum timeout (unless no parameter is given in which case the timeout is only 10 seconds) for the Lock file to be available. Once the Lock file becomes available, the 2nd instance takes the Lock and can proceed normally. The assumption here is that a normal script execution launched from the "services-start" script file would take less than 120 seconds to exit (e.g. "addCronJob" or "postUpdateEmail"). The only outlier (so far) would be the call to do the "postRebootRun" which can take more than 120 seconds, but in such a case a F/W Update and a subsequent reboot are expected anyway.

[ExtremeFiretop]

@Martinski4GitHub

Sorry buddy was a busy day and I was tired so I didn't get to test this out.
However I noticed a new alpha for 3006 so I'm going to test this out now and advise! :)

[ExtremeFiretop]

Tested! And worked perfectly!! :)

[Martinski4GitHub]

@Martinski4GitHub

Sorry buddy was a busy day and I was tired so I didn't get to test this out. However I noticed a new alpha for 3006 so I'm going to test this out now and advise! :)

No worries, bud. I completely get it. We both have "other things" going on and sometimes we're too tired to do other things.