Luca Boccassi 7233e91af0 core: store timestamps of unit load attempts ... When the system is under heavy load, it can happen that the unit cache is refreshed for an unrelated reason (in the test I simulate this by attempting to start a non-existing unit). The new unit is found and accounted for in the cache, but it's ignored since we are loading something else. When we actually look for it, by attempting to start it, the cache is up to date so no refresh happens, and starting fails although we have it loaded in the cache. When the unit state is set to UNIT_NOT_FOUND, mark the timestamp in u->fragment_loadtime. Then when attempting to load again we can check both if the cache itself needs a refresh, OR if it was refreshed AFTER the last failed attempt that resulted in the state being UNIT_NOT_FOUND. Update the test so that this issue reproduces more often.		2020-06-30 16:50:00 +02:00
..
Makefile	core: reload cache if it's dirty when starting a UNIT_NOT_FOUND unit	2020-05-30 16:50:05 +02:00
test.sh	core: reload cache if it's dirty when starting a UNIT_NOT_FOUND unit	2020-05-30 16:50:05 +02:00