Klaas van Schelven eb23d44962 Enforce a single pc_registry for a single ingesting process ...

Using a pid-file that's implied by the ingestion directory.

We do this in `get_pc_registry`, i.e. on the first request. This means failure is
in the first request on the 2nd process.

Why not on startup? Because we don't have a configtest or generic on-startup location
(yet). Making _that_ could be another source of fragility, and getting e.g. the nr
of processes might be non-trivial / config-dependent.

2024-07-09 13:14:27 +02:00

..

management

Add checksnappea command

2024-05-17 12:03:40 +02:00

migrations

Pea -> Task

2024-04-19 21:29:04 +02:00

__init__.py

Explicit error message for malformed task name

2024-07-05 15:54:55 +02:00

admin.py

Midway checking to preserve state

2024-04-19 11:58:20 +02:00

apps.py

Midway checking to preserve state

2024-04-19 11:58:20 +02:00

datastructures.py

Convert snappea 'wakeup' signal to inotify-based

2024-04-22 15:34:33 +02:00

decorators.py

Snappea connection_close

2024-07-05 16:28:23 +02:00

example_tasks.py

Snappea: logging

2024-04-23 11:28:07 +02:00

foreman.py

Enforce a single pc_registry for a single ingesting process

2024-07-09 13:14:27 +02:00

models.py

Fix typo

2024-05-17 15:52:43 +02:00

settings.py

Add missing file

2024-04-24 12:30:25 +02:00

tests.py

Midway checking to preserve state

2024-04-19 11:58:20 +02:00

views.py

Midway checking to preserve state

2024-04-19 11:58:20 +02:00