Skip to content
This repository was archived by the owner on May 29, 2023. It is now read-only.
This repository was archived by the owner on May 29, 2023. It is now read-only.

HolyOrders should not start when it's already running #116

@crantila

Description

@crantila

Problem: HolyOrders is set to start according to a systemd timer. It's possible for a single HolyOrders run to take so long that the following execution begins before the first has finished. This would lead to a lot of unnecessary computation and would also potentially corrupt the update time database or produce errors because HolyOrders is not designed for that.

Solution: When HolyOrders starts, it should check whether another HolyOrders instance is already running. If so, the second HolyOrders instance should exit.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions