bug#26931: GuixSD rebooting fails when tmux is running

[ng0 <ng0@pragmatique.xyz>]

Ludovic Courtès transcribed 0.7K bytes:
> Leo Famulari <leo@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’.
> 
> 
> 

terminal 1:
tmux new

terminal 2:
[user@abyayala ~]$ killall tmux
tmux: no process found

I haven't looked into the core of shepherd, but I think
it should try to kill the process by processid:

terminal 1:
[user@abyayala ~]$ pidof tmux
29611 29609
[user@abyayala ~]$ kill 29611

terminal 2 (the "tmux" is still from when I started it):
[user@abyayala ~]$ tmux
[server exited]


I hope this helps.
-- 
https://pragmatique.xyz
PGP: https://people.pragmatique.xyz/ng0/