executor/MaRS: fsync mars_db after writing
To increase the chances of the mars_db file being written back to disk after an update, we should fsync the file after being done writing to it (while keeping the global lock).
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
To increase the chances of the mars_db file being written back to disk after an update, we should fsync the file after being done writing to it (while keeping the global lock).