Regarding autosave and non-blocking
-
- Fast Inserter
- Posts: 144
- Joined: Mon Mar 14, 2016 3:51 pm
- Contact:
Regarding autosave and non-blocking
I understand this is an experimental feature for the headless Linux server. Is there a way to use experimental non-blocking saves, but then do a blocking (safer) save once an hour or at a scheduled interval? Our megabase map is starting to take a long time for save and I would be interested in using this feature, but concerned about the potential of corruption.
-
- Fast Inserter
- Posts: 144
- Joined: Mon Mar 14, 2016 3:51 pm
- Contact:
Re: Regarding autosave and non-blocking
To reply to myself after some experimentation, I have found the following:
- The server can be configured to use non-blocking autosave, and this saves nicely and consistently.
- I can send "/save" to the server process on standard IN (ie: the console) and it will do a BLOCKING save to the original save file.
This means I have a method I can use to do a routine blocking save for safety every few hours, and leverage a more frequent non-blocking save every 15 minutes.
Now to script it and put it in cron.
- The server can be configured to use non-blocking autosave, and this saves nicely and consistently.
- I can send "/save" to the server process on standard IN (ie: the console) and it will do a BLOCKING save to the original save file.
This means I have a method I can use to do a routine blocking save for safety every few hours, and leverage a more frequent non-blocking save every 15 minutes.
Now to script it and put it in cron.