Creation of global file /var/lock/scap-global-lock does not block scap deployments/self-updates anymore.
This above seems to be still the expectation from other teams, plus a cursory review of the TimeoutLock code shows the global lock is still treated as a special case but it's not immediately clear what the designed behavior for it is.
As it turns out, the manual creation of the file was superseded by the command scap lock We should update any references in the docs/wikis and let interested parties know.
Additionally, we should allow both locking for periods longer than 1h + mechanism to forcefully unlock the global lock.