From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: bug#26931: GuixSD rebooting fails when tmux is running Date: Thu, 18 May 2017 12:22:50 +0000 Message-ID: <20170518122250.thgu2qo7wvbvzwor@abyayala> References: <20170514193043.GA5396@jasmine> <87lgpzqfxq.fsf@gnu.org> <20170516231839.GA22678@jasmine> <87inl00w5a.fsf@gnu.org> <20170518011355.GA29685@jasmine> <87a86aa60r.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50738) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dBKTP-0001bS-Q1 for bug-guix@gnu.org; Thu, 18 May 2017 08:24:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dBKTK-0000ec-PQ for bug-guix@gnu.org; Thu, 18 May 2017 08:24:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:49423) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dBKTK-0000eY-Lt for bug-guix@gnu.org; Thu, 18 May 2017 08:24:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dBKTK-0004Pp-GK for bug-guix@gnu.org; Thu, 18 May 2017 08:24:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87a86aa60r.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 26931@debbugs.gnu.org Ludovic Courtès transcribed 0.7K bytes: > Leo Famulari 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/