Rudder

Jonathan CLARKE wrote:

This is a bug - we should never silently remove a lock.

The extra option (--force or whatever) could be a new feature for 3.3, but this definitely needs fixing in the next minor release.

On the contrary, we should never run the agent manually without the lock - the risks of misbehavour is too big. Exemple, run twice agent without lock if the disable agent is set, and the second run will e a complete run.
This is a simple example, but it appl for everything (check if service is running and restart it if not, one first run it will be ok, on the second, the check will not be done, and the service will be restarted)

This doesn't seem quick, we first need to understand how -K works and the implication of removing it.