kill not working

saiganesh@LAPTOP-EJBON1NM ~
$ pwd

saiganesh@LAPTOP-EJBON1NM ~
$ ps
      PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND
    14072   16116   14072      16120  pty1      197609 23:24:55 /usr/bin/ps
S   14584       1   14584      10368  pty0      197609 22:48:56 /usr/bin/man
S   11244       1   11244      14032  pty0      197609 21:50:41 /usr/bin/cat
S    4288   14584   14584      13752  pty0      197609 22:48:56 /usr/bin/less
    16116   14124   16116       6224  pty1      197609 23:24:48 /usr/bin/bash
    14124       1   14124      14124  ?         197609 23:24:48 /usr/bin/mintty

saiganesh@LAPTOP-EJBON1NM ~
$ kill 16116

saiganesh@LAPTOP-EJBON1NM ~

Open in new window

can you please advise why kill not working as above?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

A Q ChoudaryJunior Linux EngineerCommented:
You also can use any of three:
kill -9 16116
pkill 16116
pkill -9 16116
definately it will work for you

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Prabhin MPEngineer-TechOPSCommented:
Hi ,
Use kill -9 <pid>
As you did not specify which signal to send, a SIGTERM was sent
man kill
If no traps have been set, a bash shell in interactive mode normally ignores SIGTERM
man bash
If you want bash to do something with SIGTERM, you can set up a trap for it, or if you want to tell it something else, you can send it a different signal.
joolsSenior Systems AdministratorCommented:
I think the default kill is something like a signal 15 (dont have a system here to check) which is like asking it nicely to leave the premises.

You want to do the -9 (mentioned before) to pull the rug from under it and kick it out the door*.

* some processes may still appear to hang if they are still waiting IO.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.