From owner-freebsd-questions@freebsd.org Mon Jun 11 09:03:33 2018 Return-Path: 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 019BB100288F for ; Mon, 11 Jun 2018 09:03:32 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EA3A77E49 for ; Mon, 11 Jun 2018 09:03:32 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: by mail-qt0-x22f.google.com with SMTP id h5-v6so19503162qtm.13 for ; Mon, 11 Jun 2018 02:03:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dpJKtTVoFT9rBYxaB9wdklV57UrynZGftCUG/52gZ8w=; b=W3TbTzbYUzX3Vks38hHnIbvvkqJZF54OteGJcIzYxDYRxIBhA/zCJ9d4HuHmm1PpDV Ru5SAPwomj4ec1cHgsm6GQwBDNn2udhfgfTLqKibyj5WQ8lkxQCfPivtVLOylVbsa3FF pq07vbBo3xRGyxuos/298nR6hi4N4kogtHgHJPJn50cL66WSrGw7r25eBkkv6u0MTvn5 Rmqq4NCSzzQZioLoXccVqSY86zURcZiWypWUNT4IbnKYHPx6QgZ2RuKGSTvF7yU+DiOy Xwe9VFreLW7wM4Vz+tkk6l6iwxFGCEqZcL+ByGadYYjzG9uIkFF0F9rUCm1K4gxMcR9v uCyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dpJKtTVoFT9rBYxaB9wdklV57UrynZGftCUG/52gZ8w=; b=S1ngk9jUKYCs64oQ1XcE7enVwbxoZoDloIiRucBVqWFOtdpuBnla1Osf0Sf6u0dzNN 758HrcpfnECYatI2Ig12aS8FvoS+2T8IsH51y7r7i20K5bdRLk5AzO+0Kgd1c0FqJdy5 qwYGmVJSfMUJwYRDGVbg1gfst/QRHdqcJD9pjKo4GRkJ3vTDVJRhJ4vOotaNyByERWJR IRfm3yhyOm477bN2kt2Uvd1Exyc//xJ2qjVtmSRR8gbw2gOn8KagRN7gQa7MoFn/IVqS OZM9H1Tmaq0myvcrDeOo0aMTbsF/Mxu7B1fBngcl5QbqOpJFaxEdOSxYPnPGgO5P6PKf Ft1A== X-Gm-Message-State: APt69E1NOPuShimwH+8DhJ6k/XHJCJmtd/gXVGLXfFX21yG+dhDaQcT4 ZH/cclcL4DJjXFGJ6CebjYFnG1RStr+/qUgXTCc= X-Google-Smtp-Source: ADUXVKJ/FJ/PGnxJ9eX7B082RYWfu9pmyqCD6jsMzVJv6xU7g6Fp4rX09B2iG5CUD24e+tTYOu+yMVFDiVxjVfphGxU= X-Received: by 2002:aed:3595:: with SMTP id c21-v6mr14810855qte.3.1528707812061; Mon, 11 Jun 2018 02:03:32 -0700 (PDT) MIME-Version: 1.0 References: <9a7f62c4-80aa-7eea-91ec-6712612a0451@pobox.com> <20180611104857.272ba600.ole@free.de> In-Reply-To: <20180611104857.272ba600.ole@free.de> From: Michael Schuster Date: Mon, 11 Jun 2018 11:03:20 +0200 Message-ID: Subject: Re: Unable to kill processes using either Ctrl-C or 'kill' To: ole@free.de Cc: freeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2018 09:03:33 -0000 I can think of two ways a process/thread gets "stuck" in the kernel 1) it's waiting for some kind of lock/resource to get released 2) like 1, but doing so "busy waiting" for 1), all I can think of is a kernel debugger and some fairly sophisticated twiddling of bits ... in the second case, the system's load is probably quite high, and you may be able to find out what it's doing using dtrace and a profile provider ... HTH Michael On Mon, Jun 11, 2018 at 10:50 AM Ole wrote: > Sun, 3 Jun 2018 21:03:31 +0200 - Michael Schuster > : > > > > Can you get added to sudoers? I realize that still implies a level > > > of root access but I really don't know of any other way to kill > > > processes which don't belong to you. I don't see why the sysadmin > > > would need to reboot. > > > > most likely, being root or equivalent won't help in this case. If a > > processes owner cannot kill it (using -9, which cannot be caught) that > > implies that the process is hung in the kernel (signal delivery > > happens when a process leaves kernel context). > > 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. > > Thanks > Ole > -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion'