Leo Famulari <l...@famulari.name> skribis: > On Wed, May 17, 2017 at 09:39:45AM +0200, Ludovic Courtès wrote: >> This is on the bare metal and /etc/shepherd/do-not-kill does not exist, >> right? > > Yes, on a Thinkpad x200s (x86_64) with a recent kernel. Nothing is > protected by a 'do-not-kill' file. > >> We could always add a round of SIGKILL in the ‘wait’ loop, but that >> doesn’t sound right. > > Agreed. > >> Does /var/log/messages contain any hints as to why tmux wasn’t >> terminated? > > Not from what I can see. I'll keep digging.
Could it be that “something” respawned a tmux process after the first one had been killed with SIGKILL? Ludo’.
