On 2020/02/23 10:04:46, hanwenn wrote: > On 2020/02/23 09:49:24, dak wrote: > > Stupid question: does the database design of lilypond-book even allow for > > uncoordinated parallel runs? > > It's not a stupid question; it's a good question. > > Writing files atomically (open temp file, write, close, rename), seems a lot of > work. > > I've considered adding an advisory lock on the DB directory. Since we max out > CPUs when we run lp-book, it shouldn't slow down things, but I was worried about > doing file locks cross-platform. > > Maybe I can do flock(1), which at least lets limit the worry to OSX vs. Linux.
to answer your original question: I think the \sourcefileline statements can differ between snippets written from different lp-book instances, and this can trigger a consistency check failure. https://codereview.appspot.com/547680043/
