@Stefano Bonicatti I think I’m ready to cut 5.2.2. Do you want to try to come to resolution on #7474 before?

There doesn’t seem to be consensus about that choice and we really have spoken briefly me and you about that, so I guess that kind of choice can be done on a blueprint. I’m still slightly concerned though by the high default graceful time period, which is really meant for the normal shutdown workflow. Would a solution where we keep the “force” logic for the resource limit kill, but we wait 4 seconds for the graceful kill and then forcefully kill. 4 seconds is about the time osquery was waiting before we have changed the alarm timeout.

Maybe a 4s grace is enough? That feels like enough that an unwedged process should be able to checkpoint.

Well, lets shift all of this to the 5.3.0 then

Okay! I’ll cut 5.2.2 later today, and we’ll see if we like it