diff options
author | Diego Santa Cruz <Diego.SantaCruz@spinetix.com> | 2016-02-02 13:04:20 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-02-04 23:47:48 +0000 |
commit | be032fc40eb315841fdd1f69c780726619ea1bad (patch) | |
tree | 71c6d9db5485ef8bfcf373dd85f94a9fc17e0274 /bitbake/bin/bitbake-dumpsig | |
parent | 1e95ebd4c3f8364479c371d2c4bc4f643db3262f (diff) | |
download | poky-be032fc40eb315841fdd1f69c780726619ea1bad.tar.gz |
bitbake: bitbake: prserv: -wal and -shm sqlite lost when daemonizing
When daemonizing the PR service the -wal and -shm sqlite files were
being deleted, although they should never be. While the daemonized
process keeps the file descriptors open and thus a clean exit does
not loose any data, a power outage would loose all data in the WAL.
Removing these files also breaks sqlite collaboration between
processes and furthermore prevents taking proper backups without
stopping the PR service.
The reason this happens is that the DB connection is opened in
the initial process, before forking for daemonization. When the
DB connection is closed by the exiting parent processes it can
delete the -wal and -shm files if it considers itself to be the
last connection to the DB. This is easily fixed by opening the
DB connection after all forking.
[YOCTO #9034]
(Bitbake rev: bc867c81e3894da5bdd2e45fa695bb5f5f1bb58b)
Signed-off-by: Diego Santa Cruz <Diego.SantaCruz@spinetix.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/bin/bitbake-dumpsig')
0 files changed, 0 insertions, 0 deletions