From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#26931: GuixSD rebooting fails when tmux is running Date: Thu, 18 May 2017 11:06:12 +0200 Message-ID: <87a86aa60r.fsf@gnu.org> References: <20170514193043.GA5396@jasmine> <87lgpzqfxq.fsf@gnu.org> <20170516231839.GA22678@jasmine> <87inl00w5a.fsf@gnu.org> <20170518011355.GA29685@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54726) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dBHOk-0004AK-OE for bug-guix@gnu.org; Thu, 18 May 2017 05:07:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dBHOg-0002Yk-PO for bug-guix@gnu.org; Thu, 18 May 2017 05:07:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:49197) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dBHOg-0002Yg-MV for bug-guix@gnu.org; Thu, 18 May 2017 05:07:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dBHOg-0001LN-Gj for bug-guix@gnu.org; Thu, 18 May 2017 05:07:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20170518011355.GA29685@jasmine> (Leo Famulari's message of "Wed, 17 May 2017 21:13:55 -0400") 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: Leo Famulari Cc: 26931@debbugs.gnu.org Leo Famulari skribis: > On Wed, May 17, 2017 at 09:39:45AM +0200, Ludovic Court=C3=A8s 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 =E2=80=98wait=E2=80=99 loo= p, but that >> doesn=E2=80=99t sound right. > > Agreed. > >> Does /var/log/messages contain any hints as to why tmux wasn=E2=80=99t >> terminated? > > Not from what I can see. I'll keep digging. Could it be that =E2=80=9Csomething=E2=80=9D respawned a tmux process after= the first one had been killed with SIGKILL? Ludo=E2=80=99.