Unable to kill processes using either Ctrl-C or 'kill'
michaelsprivate at gmail.com
Mon Jun 11 09:03:33 UTC 2018
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 ...
On Mon, Jun 11, 2018 at 10:50 AM Ole <ole at free.de> wrote:
> Sun, 3 Jun 2018 21:03:31 +0200 - Michael Schuster
> <michaelsprivate at gmail.com>:
> > > 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.
recursion, n: see 'recursion'
More information about the freebsd-questions