Since we do not check that the PID read from an existing PID file isn't our own, we can erronously detect ourselves as another running Peekaboo instance and refuse to start. This can happen for example if /run isn't cleared at boot and (particularly in containers) our process receives the same PID on consecutive executions. But obviously this can also happen in any other scenario if we're just restarted often enough to receive the same PID twice.
Since we do not check that the PID read from an existing PID file isn't our own, we can erronously detect ourselves as another running Peekaboo instance and refuse to start. This can happen for example if /run isn't cleared at boot and (particularly in containers) our process receives the same PID on consecutive executions. But obviously this can also happen in any other scenario if we're just restarted often enough to receive the same PID twice.