7

I try to kill a process with sudo kill 30602. But after I killed it I use ps aux | grep gmond to check, it appear again with another pid.That's like:

ganglia  30997  0.0  0.1 121812  2128 ?        Ssl  16:05   0:00 /usr/sbin/gmond --pid-file=/var/run/ganglia-monitor.pid

Whatever how I kill it, it just appear again with another pid, even with kill -9.

What's the problem? And how to solve this?

manav m-n
  • 11,136
  • 23
  • 74
  • 97
Tony Han
  • 2,130
  • 3
  • 24
  • 37
  • It might be restarted automatically, see [here](http://superuser.com/a/507835/83249). – Christian.K Jul 31 '14 at 08:10
  • possible duplicate of [How to kill respawned process by init in linux](http://stackoverflow.com/questions/21016641/how-to-kill-respawned-process-by-init-in-linux) – manav m-n Jul 31 '14 at 08:14

1 Answers1

1

You should change the entry in the /etc/inittab file. Probably your gmond service entry is starting with respawn. It will respawn every time you kill the process.

Link: To disable the process you have to edit /etc/inittab and comment out that line. To inform init about this change you have to send a SIGHUP to init:

kill -HUP pid-of-init

The /etc/inittab file was the configuration file used by the original System V init daemon. The Upstart init daemon does not use this file, and instead reads its configuration from files in /etc/init directory.

Community
  • 1
  • 1
manav m-n
  • 11,136
  • 23
  • 74
  • 97