Race condition when starting multiple instances simultaneously about elvish HOT 2 OPEN

This situation happened to me many times when I starting using Elvish. I had to add a randomized "sleep" command to my Elvish program that started Elvish on my Tmux sessions to minimize being affected by this race to start the Elvish daemon. This scenario is one of the reasons I am working on replacing the existing BoltDB history mechanism with a simple flat-file store. A flat-file history store has its own race conditions but does not include a race involving launching a new process. It is therefore easier to reason about and avoid races as described in the above problem statement.

from elvish.

To clarify my previous comment... I (re)wrote an Elvish program that initialized multiple Tmux sessions in parallel. The program was originally written as a POSIX script but that isn't really relevant. What is relevant is that both programs launched multiple interactive Elvish programs on the same system more or less simultaneously. Which caused those interactive Elvish shells to race creating the interactive daemon.

from elvish.