From owner-freebsd-questions@freebsd.org  Tue Jun 12 00:10:10 2018
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 594461013BA2
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Tue, 12 Jun 2018 00:10:10 +0000 (UTC)
 (envelope-from cyberleo@cyberleo.net)
Received: from mail.cyberleo.net (paka.cyberleo.net [216.226.128.180])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0A54486AA1
 for <freebsd-questions@freebsd.org>; Tue, 12 Jun 2018 00:10:09 +0000 (UTC)
 (envelope-from cyberleo@cyberleo.net)
Received: from [172.16.44.4] (vitani.den.cyberleo.net [216.80.73.130])
 by mail.cyberleo.net (Postfix) with ESMTPSA id 4AD76581FB;
 Mon, 11 Jun 2018 20:10:01 -0400 (EDT)
Subject: Re: Unable to kill processes using either Ctrl-C or 'kill'
To: Ole <ole@free.de>, freebsd-questions@freebsd.org
References: <9a7f62c4-80aa-7eea-91ec-6712612a0451@pobox.com>
 <CAOZUxFu7LkafvT30H_ZZG6uJ-CkU537RD=dSHcEP=UVRgOdrZw@mail.gmail.com>
 <CADqw_gLwsSKT3w8iyY7d9+isqyt7YH4CvifRL2WG54OQdvK7Xw@mail.gmail.com>
 <20180611104857.272ba600.ole@free.de>
From: CyberLeo Kitsana <cyberleo@cyberleo.net>
Message-ID: <7cf1c687-f424-4612-7809-da45713588db@cyberleo.net>
Date: Mon, 11 Jun 2018 19:10:00 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <20180611104857.272ba600.ole@free.de>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2018 00:10:10 -0000

On 06/11/2018 03:48 AM, Ole wrote:
<snip>> I got stuck in the same situation:
> 
> # kill -9 91651
> # ps -o pid,jid -awux | grep 91651
> 91651  11 root              0.0  0.0   101488   29344  -  TsJ Fri05       2:10.18 /usr/local/sbin/syslog-ng -p /var/run/syslog.pid
> 
> and I wonder if there is anything I can do to get rid of this process.
> I had this situation last year too and ended up in restarting the whole
> system. But now I can't reboot.

This process is stopped (state T). Sending it signal 19 (SIGCONT) might
help unstick it long enough for it to receive SIGKILL.

It might be a good idea to try and figure out why it got stopped in the
first place, though.

-- 
Fuzzy love,
-CyberLeo

<CyberLeo@CyberLeo.Net>
Technical Administrator

CyberLeo.Net Webhosting
http://www.CyberLeo.Net

Element9 Communications
http://www.Element9.net


Furry Peace! - http://www.fur.com/peace/