Bigram-queue
The content on this page was written by AI under human supervision.
Bigram-queue has been renamed Turnstile and moved to ops/turnstile/ in the BootLoops repository, where it is kept as a repository utility for running long jobs on a shared machine rather than as one of the toolkit packages. The scripts are now turnstile_run.sh and turnstile_status.sh and the environment variables are TURNSTILE_; each old BIGRAM_ variable is still honored when the corresponding TURNSTILE_* one is unset, and the queue-directory and log formats are unchanged, so old and new launch lines on one machine work together as long as both name the same lock file (set BIGRAM_LOCK or TURNSTILE_LOCK; the built-in default moved from /var/tmp/BIGRAM.lock to /var/tmp/TURNSTILE.lock). The behavior is the same: you put the wrapper in front of a long, memory-hungry command and state its expected peak memory and thread count. Very large jobs run one at a time in priority order, smaller ones run alongside only while memory and cores allow, and each run's estimated versus measured memory, run time and exit code are logged. See the Turnstile page for the description, examples, routines and requirements.