Date: Mon, 11 Jun 2018 11:03:20 +0200 From: Michael Schuster <michaelsprivate@gmail.com> To: ole@free.de Cc: freeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Unable to kill processes using either Ctrl-C or 'kill' Message-ID: <CADqw_g%2B4g71Q3rFu959coCVrHTtwJzJ-hk604riWsmCwtVX96Q@mail.gmail.com> In-Reply-To: <20180611104857.272ba600.ole@free.de> References: <9a7f62c4-80aa-7eea-91ec-6712612a0451@pobox.com> <CAOZUxFu7LkafvT30H_ZZG6uJ-CkU537RD=dSHcEP=UVRgOdrZw@mail.gmail.com> <CADqw_gLwsSKT3w8iyY7d9%2Bisqyt7YH4CvifRL2WG54OQdvK7Xw@mail.gmail.com> <20180611104857.272ba600.ole@free.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <ole@free.de> wrote: > Sun, 3 Jun 2018 21:03:31 +0200 - Michael Schuster > <michaelsprivate@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. > > Thanks > Ole > -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion'
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADqw_g%2B4g71Q3rFu959coCVrHTtwJzJ-hk604riWsmCwtVX96Q>