Martchus
7ade757c8d
* Only lock the config for writing the reloading the config file
* Make sure all write operations to the database acquire an "update mutex"
to ensure only one write operation happens at a time
* Do *not* acquire any additional locks when reading from a database as it
should be safe to do so even when a write operation happens because
* LMDB read and write transactions can happen at the same time
* The package cache has its own mutex anyways
* Write ops to the package cache try to lock the "update mutex" to
prevent writing "old" data to the cache during updates
* Make "lastUpdate" atomic to avoid locking the config when accessing it
|
||
|---|---|---|
| .. | ||
| buildaction.cpp | ||
| buildaction.h | ||
| buildactionfwd.h | ||
| buildactionlivestreaming.cpp | ||
| buildactionmeta.cpp | ||
| buildactionmeta.h | ||
| buildactionprivate.h | ||
| buildactiontemplate.cpp | ||
| buildactiontemplate.h | ||
| conductbuild.cpp | ||
| customcommand.cpp | ||
| makelicenseinfo.cpp | ||
| preparebuild.cpp | ||
| reloadconfiguration.cpp | ||
| reloaddatabase.cpp | ||
| reloadlibrarydependencies.cpp | ||
| repomanagement.cpp | ||
| subprocess.h | ||
| subprocessfwd.h | ||
| updatecheck.cpp | ||