unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@pragmatique.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 26931@debbugs.gnu.org
Subject: bug#26931: GuixSD rebooting fails when tmux is running
Date: Thu, 18 May 2017 12:22:50 +0000	[thread overview]
Message-ID: <20170518122250.thgu2qo7wvbvzwor@abyayala> (raw)
In-Reply-To: <87a86aa60r.fsf@gnu.org>

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/

  reply	other threads:[~2017-05-18 12:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-14 19:30 bug#26931: GuixSD rebooting fails when tmux is running Leo Famulari
2017-05-14 21:36 ` Ludovic Courtès
2017-05-16 23:18   ` Leo Famulari
2017-05-17  7:39     ` Ludovic Courtès
2017-05-18  1:13       ` Leo Famulari
2017-05-18  9:06         ` Ludovic Courtès
2017-05-18 12:22           ` ng0 [this message]
2017-08-28  8:22     ` Ludovic Courtès
2017-08-28  8:30       ` Clément Lassieur
2017-08-28 10:16         ` Ludovic Courtès
2017-08-30  7:35           ` Clément Lassieur
2017-08-30  8:39             ` Ludovic Courtès
2017-08-28  8:50       ` ng0
2017-08-28 10:18         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170518122250.thgu2qo7wvbvzwor@abyayala \
    --to=ng0@pragmatique.xyz \
    --cc=26931@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).