quiesce

I think more inclusive verbs are disable or quiesce.

Message passing still requires copying, or some way to quiesce other threads and recursively change lock ownership of an object graph.

If you're the one that came up with the idea of the "quiesce", I feel like you owe quite a few of us in the systems software community a beer or three...

The way it was backed up was to quiesce the standby, take a snapshot of its filesystems on the SAN, then send those to tape while the standby was reenabled.

It's still in heavy development, but I'm guessing it's easier than trying to quiesce browser activity and tease out network events manually.

On one hand, it seems liberating to move away from bound-servers, but who maintains the configs and mental-model for all of the "unbound" processes that can "materialize", do work, then quiesce again?

Also sometimes, like holidays, I find I need some ingredient and it's better to have it delivered than to quiesce all my cooking activity, roundtrip to the store, and resume without breaking my timeline.

Execution pipelines would stop issuing and resolve all in-process instructions and push registers to a stack, the memory system would need to quiesce the memory system and flush all structures, and finally the processor could rewrite low-level addressing crossbars.

The conclusion I've come down to, is that the app has to take some responsibility to provide for consistent backups, either via checkpoints / write barriers, or via a quiesce command that can finalize in-flight transactions, and pause / buffer operations long enough for a volume snapshot to take place.