ingest sometimes does not close cleanly

[markmacgillivray]

I occasionally seem to have spurious ingest processes running, and slowly eating more CPU. Not sure why yet, but may be an issue particularly if we are running multiple bibservers on one machine - are the ingest proceses tied to their parent bibserver processes, or will they start trying to talk to each other?

[epoz]

Because of the reloader, (running in dev mode) multiple ingest processes were being started up.
Have added a check to make sure that only process runs at the same time.
In production we should consider making it run separate from the main process, by checking a config variable.