|
|
Log in / Subscribe / Register

Changing Fedora's shutdown timeouts

Changing Fedora's shutdown timeouts

Posted Jan 24, 2023 9:38 UTC (Tue) by kleptog (subscriber, #1183)
In reply to: Changing Fedora's shutdown timeouts by Wol
Parent article: Changing Fedora's shutdown timeouts

> My employer is a supermarket. If customers commit a transaction, the LAST thing we want is for the system to "crash" and lose those transactions. But if the system does not give the database time to flush those transactions to the log, that is exactly what will happen.

Then that database is broken. Once the database acknowledges the COMMIT from the user, it must not lose the transaction, even if the power fails, SIGKILL, whatever (asteroid impact may be an exception). If you require synchronisation with other systems, you have two-phase commit where the decision whether a transaction will be committed or aborted can be made even after a crash and restart.

There are many ways to do this, usually the database has it's own transaction log. For individual files you have the write/sync/rename trick which every editor should be doing. You're right that the file-system doesn't guarantee anything without using one of the *sync() syscalls, it's debatable whether it should.


The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:

Note: you can avoid this step in the future by logging into your LWN account.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds