# Cylc scan and cylc kill

**URL:** <https://cylc.discourse.group/t/cylc-scan-and-cylc-kill/281>\
**Category:** Cylc Support\
**Created:** [October 22, 2020, 1:22pm UTC](https://cylc.discourse.group/t/cylc-scan-and-cylc-kill/281 "2020-10-22T13:22:37Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![hilary.j.oliver](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/hilary.j.oliver/32/4_2.png) [@hilary.j.oliver](https://cylc.discourse.group/u/hilary.j.oliver)\
**Post date:** [October 22, 2020, 10:22pm UTC](https://cylc.discourse.group/t/cylc-scan-and-cylc-kill/281/4 "2020-10-22T22:22:19Z")

</div>

Hi Luciana,

> [@Luciana\_Rocha](#):
>
> luciana@puma:/home/luciana\> **cylc kill -f test-jobsub**

The `cylc kill` command kills selected task jobs in a running suite, it doesn’t kill the scheduler program itself.

To get a suite to shut down cleanly, use `cylc shutdown <suite>` or `cylc stop <suite>`.

That should work fine. In rare occasions where a suite becomes unresponsive, as a last resort you can kill the Linux process as shown by @Rosalyn_Hatcher. (Note you can still do a restart, from wherever the workflow got to, even after a hard kill).

(See `cylc kill --help` etc.)

Regards,  
Hilary

---

_[View the full topic](https://cylc.discourse.group/t/cylc-scan-and-cylc-kill/281)._