This has been suggested before. Saving per time limit might work better, but we don't want to slow fast rollouts down. I'll put it on my todo.
Christian. On Mon, Jun 15, 2009 at 6:57 AM, Michael Petch<[email protected]> wrote: > Addendum to feature request: > > Posted By: Jason Lee <[email protected]> > Date: Sunday, 14 June 2009, at 10:50 p.m. > > Oh man, I want that too. In addition to those kind of regular saves, how > about regular saves when using the CMark function? I set up a couple dozen > to roll out, and it might take a week. There are all kinds of reasons why it > might die in the middle, and if it happens near the end... pffft, there goes > a week's worth of CPU time. > > Thanks very much in advance if this can be implemented. > > JLee > > > On 14/06/09 8:35 PM, "Michael Petch" <[email protected]> wrote: > > Posted By: dc-ohio <[email protected]> > Date: Sunday, 14 June 2009, at 8:58 p.m. > > auto save rollout after every (x)# of trials. When running really > realllllllly long rollouts, it would be nice to not lose a ton of data due > to a power outage or similar problem > > _______________________________________________ > Bug-gnubg mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/bug-gnubg > > _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
