Working battery ≠= avoiding system crashes | my local node has a UPS, and still Monero's client is dicey (Mac & Linux distros).

Particularly on its initial sync, Monero's daemon is flakeyAF.

If you (e.g.) don't allow `sync in background` (why is this not the default behavior?!), the official Monero client is notorious for locking up on wakeup. Once you kill the process, your local blockchain is [most likely] unusable.

Another reason to use safe-sync is (e.g.) if your system (Linux or whatnot) decides to update/restart during the several days it takes to sync-initially.

----

Just out of curiosity, why do you abuse an SSD so (safe-mode, or not)?

For SSD-diehards, I'd recomment getting a very large size because this'll last longer, presuming the drive self-levels.

▲

hyc_symas 2 hours ago | parent [-]

> Once you kill the process, your local blockchain is [most likely] unusable.

Totally false. LMDB is perfectly crash-proof in that scenario and killing the process never damages the DB. The only thing that's not guaranteed is turning off syncs, in the face of an OS crash/power outage.

If you don't sync, you're not abusing the SSD. If you run on Windows, the OS is too unstable to use without safe sync mode though.

	▲	ProllyInfamous an hour ago \| parent [-]
		>Totally false. This is a well-documented failstate. Usually results in "unable to connect to 127.0.0.1:18081" errorlog, which is most-commonly due to a corrupt database/blockchain (from hardstop/kill). In order of crashout likelihood: Windows >> MacOS > Linux >If you don't sync, you're not abusing the SSD. If you don't sync then you're not (cannot be) a fullnode / network verifyer / ringsigner. ---- >LMDB is perfectly crash-proof It is my understanding that once your initial-sync has completed, the default monero node behavior is to then automatically enter the --safe flag (I described above). This may be old behavior... I go way back (years beyond a decade). My only modern use in xmrworld is as a personal foot-heating ATM.