software: redone job handling

There was a serious flaw in previous object model. JobManager was a
thread spawned from inside of separated YumWorker process. Meanwhile
IndicationManager was spawned in provider process which is correct
otherwise it coult not send indications through broker.

The problem is that JobManager needs to create indications and access
IndicationManager. But they were in different processes.
JobManager worked with static data duplicated from provider process when
the worker process has been forked. Therefor all subscriptions and
indication enablement made after the worker processed has been
created did not affect jobmanager.

For some unknown reasons this could also cause a segfault to worker
process when creating indications that were sent to provider process.

This patch shuffles classes a bit:
 * JobManager is spawned as a thread in provider process by YumDB.
 * JObManager spawns its own SessionManager that is a wrapper for
   YumWorker process
 * SessionManager is a thread running in provider's process. It
   manages worker process and ensures that yum database is locked when
   there is an active session.
 * YumWorker does not spawn any other process. It processes jobs one by
   one.

Resolves: #1039018

0 files changed, 0 insertions, 0 deletions