When max_height == 0 the max_height is computed as the nearest round multiple (default 1000) below the current block height. This feature was added so that multiple instances of linearize.py being triggered simultaneously on multiple nodes (by cron on Linux for example) will all generate the same block range despite local clock errors and block propagation disparities. The concept here is that multiple nodes will be able to generate consistent bootstrap files which can be securely cross checked by comparing MD5 checksums by agreeing a regular (say weekly) time when the linearize script will be triggered.
When max_height == 0 the max_height is computed as the nearest round multiple (default 1000) below the current block height. This feature was added so that multiple instances of linearize.py being triggered simultaneously on multiple nodes (by cron on Linux for example) will all generate the same block range despite local clock errors and block propagation disparities. The concept here is that multiple nodes will be able to generate consistent bootstrap files which can be securely cross checked by comparing MD5 checksums by agreeing a regular (say weekly) time when the linearize script will be triggered.