Claudio Jeker <cje...@diehard.n-r-g.com> wrote: > > So, that would suggest some sort of lockout against running multiple > > rpki-client with the correct termination strategy. I don't believe we > > have such a thing right now. We have the timeout, to ensure rpki-client > > doesn't run too long which may prevent simultaneous runs, but I'm not > > sure it covers all cases (imagine a weird case where two rpki-client are > > "unintentionally" started at the same time) > > > > We currently depend on cron to do the right thing and not start two > rpki-client at the same time. I would prefer to leave it up to cron (or > whatever other method people use to run rpki-client) and not add > complicated locking into rpki-client itself.
That is unrealistic. To diagnose a problem, someone will run rpki-client by hand on machine which has it enabled in cron.