Problem Controlling CM Agent Start / Stop in a Script

[#1]

I tried to use a script which start / stop CM agent. It's found that if the agent was started and then stopped, the script will be killed. As show below:

[root@cdh52 ~]# cat myscript.sh
#!/bin/bash

service cloudera-scm-agent start
service cloudera-scm-agent stop
echo "Still Alive"


You have new mail in /var/spool/mail/root
[root@cdh52 ~]# ./myscript.sh
Starting cloudera-scm-agent:                               [  OK  ]
Stopping cloudera-scm-agent: Terminated

Note that [OK] and "Still Alive" is not displayed, because the parent script was killed when cloudera-scm-agent trying to stop the agent. The same effect if "service cloudera-scm-agent" was replaced by /etc/init.d/cloudera-scm-agent

What i don't understand is HOW kill find the parent processto kill. The cloudera-scm-agent script has already disown'ed the agent. And ps show that the PID of agent's parent is 1 (init), not myscript.sh. 

Any suggestion? 

[#2]

The supervisord log might have a clue. It is in
/var/log/cloudera-scm-agent/supervisord.log

[#3]

Thanks for the reply. It seems this is a general Linux issue when killing a "su" process (where agent is), not caused by CM.

Will update here when I get meaningful finding.

[#4 · Accepted solution]

Resolved by upgrade coreutils to 8.4-37.el6 (CentOS 6.5 original version: 8.4-31.el6)

[#5]

Thanks for the update!