if second instance is executed id doesn't stop, but uses hi % of CPU

[forgie1]

Bug Description:

systemd started second instance for unknow reason (maybe thought first instance is down). If second instance is started it causes hi usage of CPU waiting for the first instance to stop running, in infinite loop.

Better would be if second instance would close itself with reason it is already running.

Manticore Search Version:

version 6.0.x

Operating System Version:

Debian GNU/Linux 12 (bookworm)

Have you tried the latest development version?

No

Internal Checklist:

^{To be completed by the assignee. Check off tasks that have been completed or are not applicable.}

• [ ] Implementation completed
• [ ] Tests developed
• [ ] Documentation updated
• [ ] Documentation reviewed
• [ ] Changelog updated