top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Why SIGKILL signal not terminate a process?

+4 votes
309 views

I see weird thing - when killing processes (by commands as:

killall -9

or with PID:

kill -9 1322

then processes stay running - they are not zombies, but eat CPU, occupy memory etc. I cannot say this behavior is always (I'm killing processes only when I need it), but I saw this several times, with last Fedora distros.

It is bad glibc signal() implementation or what else?

posted Nov 29, 2013 by Majula Joshi

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button
nice question.

Similar Questions
+2 votes

Why, when installing a new app do we need to also install the -libs and the -devel if the app is needed to make another app work.

Why cannot -libs be part of the installation if they are that important to the operation. Why are -devel, which I'm guessing are development files for the app needed, does this mean the app is bar minimum and cannot be used when required by another app.

0 votes

I looked in /lib/systemd and /etc/systemd, recursively, and none of the services or dependencies have the string pulseaudio in them.

+3 votes

So, I read the blurb that strongly advises against doing an iso-based fedup, and strongly encouraging a network-based fedup in order to yank in all the updates at once.

I have a bunch of machines to upgrade to both the workstation and server products. Having each one download everything it needs, is going to get real old.

In the past I simply rsync-ed the installation image. I have plenty of disk space on the LAN. Then I just fedup-ed everything from my rsynced image. This was almost the most efficient way to get everything updated.

Is there a single repository that I can keep rsync-ing regularly, and use it to upgrade my machines “ to both workstation and server products“ over a period of time?

...