rand-seq --reset --seed $seed
rand-seq --get-next
somehow save the random generator state between calls - maybe to /tmp/rand-seq/$seed.bin?
Perhaps instead of serializing the generator to save its state, I run rand-seqd in the background, and use a unix socket to poke at it? This might perform better? But be more complex?
Both approaches should have a way to support multiple parallel instances. rand-seq --instance or rand-seqd through an instance flag on the IPC comms
somehow save the random generator state between calls - maybe to /tmp/rand-seq/$seed.bin?
Perhaps instead of serializing the generator to save its state, I run
rand-seqdin the background, and use a unix socket to poke at it? This might perform better? But be more complex?Both approaches should have a way to support multiple parallel instances.
rand-seq --instanceorrand-seqdthrough an instance flag on the IPC comms