encfs is started as a daemon with a keepalive timer so it automatically
closes when it has been unused for some time. This is because it can take
some time both for encfs to open the encrypted data and to finish writing
all changes to it.
Other designs that has been tried where:
# open and close as fast as possible
Directly after opening dsnapshot started writing data to the decrypted path
and then close it. If the writing of the data where faster than encfs took
to open the encrypted data it would result in everything being lost.
# encryp only the snapshot
This fails because while we are working on a new snapshot it has the
trailing prefix -in-progress. It is then renamed, by removing the prefix,
when it is done. This somehow breaks encfs in mysterious ways.
encfs is started as a daemon with a keepalive timer so it automatically closes when it has been unused for some time. This is because it can take some time both for encfs to open the encrypted data and to finish writing all changes to it.
Other designs that has been tried where:
# open and close as fast as possible Directly after opening dsnapshot started writing data to the decrypted path and then close it. If the writing of the data where faster than encfs took to open the encrypted data it would result in everything being lost.
# encryp only the snapshot This fails because while we are working on a new snapshot it has the trailing prefix -in-progress. It is then renamed, by removing the prefix, when it is done. This somehow breaks encfs in mysterious ways.