ID 347227 - Nuke ignores the FOUNDRY_HEARTBEAT_DISABLE environment variable

Problem summary
Nuke ignores the FOUNDRY_HEARTBEAT_DISABLE / foundry_HEARTBEAT_DISABLE environment variable

Customer reported version
nuke.10.0v4

Customer reported platform
Linux

Steps to reproduce

1) Setup a floating license server with Nuke licenses with a low TIMEOUTALL value, e.g. 120 seconds, to see the problem quicker.  You can either edit the value in the foundry.opt file by hand or via the RLM webserver.

2) In a terminal or command prompt set "foundry_HEARTBEAT_DISABLE" environment variable to True or 1

3) Launch Nuke from the same terminal/command prompt

4) Monitor the license usage on the server.  After the period specified by TIMEOUTALL setting you'll see one of Nuke's license checkouts returned with a "timed out" but the other checkout doesn't return the license and a license remains in use.

(The single timeout is due to bug 156955 where the DDImage license checkout doesn't maintain a heartbeat and always checks in after the timeout period).


Reproduced by support
This bug has been reproduced in:
Nuke 11.1v3 - Windows 7 - OSX - Centos 6
Nuke 11.1v1 - Windows 7 
Nuke 11.0v4 - Windows 7 
Nuke 10.5v6 - Windows 7 
Nuke 9.0v9 - Windows 7 
Nuke 8.0v7 - Windows 7 
Nuke 7.0v10 - Windows 7 

Earliest version tested
Nuke 7.0v10 - earliest version available for testing and RLM licensing introduced in Nuke 7.0

Expected behaviour
When the variable is set Nuke shouldn't maintain a heartbeat to the RLM server.  After the allotted timetout period the server should reclaim the Nuke license and all checkouts go back in, the user should get a pop up in Nuke saying that the license has timed out and give a Retry button to reclaim the license.

Actual behaviour
The license heartbeat keeps running so the license isn't fully reclaimed and checked back in.  This means facilities cannot reclaim licenses from idle Nuke sessions if they are left on over night.