Richard Purdie 85256c8fa9 bitbake: prserv: SIGTERM and deamonization fixes ...

Worryingly, if you SIGKILL the bitbake cooker, an autostarted PR server
will remain behind. It turns out there are a few things we should do:

* The PR service doesn't need to daemonize when started from cooker,
  it just complicated the process lifecycle. Add a fork() method
  to handle this and use the non-daemon mode for the singleton.

* Reset the sigterm and sigint handlers. Bitbake cooker installs its
  own which we inherit meaning PR server was ignoring SIGTERM. Installing
  our own handlers which include a sync makes most sense here. Since
  we're in the code, make it sync the database on SIGINT.

* Use the new bb.utils.signal_on_parent_exit() call so that we get a
  SIGTERM when the parent (usually cooker) exits and we can shutdown
  too. Alternatives would be having an open pipe or polling
  os.getppid() for changes but this seems more effective.

(Bitbake rev: 05d31fa1f56bd3d3d363a16a421d9ba7541d4293)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2015-09-09 14:27:56 +01:00

..

__init__.py

bitbake: lib: fix no newline at end of file

2014-07-04 09:28:36 +01:00

db.py

bitbake: prserv/db: Document history modes

2015-07-12 22:50:40 +01:00

serv.py

bitbake: prserv: SIGTERM and deamonization fixes

2015-09-09 14:27:56 +01:00