# different behaviour for --stop between pt-kill and pt-heartbeat?

**URL:** <https://forums.percona.com/t/different-behaviour-for-stop-between-pt-kill-and-pt-heartbeat/4381>\
**Category:** Percona Toolkit\
**Created:** [September 3, 2015, 9:33am UTC](https://forums.percona.com/t/different-behaviour-for-stop-between-pt-kill-and-pt-heartbeat/4381 "2015-09-03T09:33:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexh](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@alexh](https://forums.percona.com/u/alexh)\
**Post date:** [September 3, 2015, 9:33am UTC](https://forums.percona.com/t/different-behaviour-for-stop-between-pt-kill-and-pt-heartbeat/4381/1 "2015-09-03T09:33:57Z")

</div>

Hi,

it seems that pt-kill and pt-heartbeat behave differently in regards to the --stop and --sentinel options.

I can easily put something like this into a cron for pt-heartbeat to restart it regularly:  
30 \* \* \* \* root /usr/bin/pt-heartbeat --utc --update --interval 1 --host XXX --database percona --table heartbeat --stop --sentinel /tmp/pt-heartbeat-hourly\>/dev/null

I couldn’t find a way to easily achieve the same for pt-kill.

Am I missing something or is there a difference between these two tools?

Thanks  
Alex