DEV Community

Discussion on: Killing many procs at one time

rhymes profile image

It's funny that the example you chose is Slack :D I heard it can become quite a memory hog!

Thanks for the tip!

dskuratovich profile image
Dmitry Author

Honestly I just wanted to check whether it's closed, because Slack has an icon in the tray.

Usually I am facing issues related to closing processes like vpn connections, third-party daemons, because they don't have icons or GUI, so we can't be sure whether it's closed or not!

andreanidouglas profile image
Douglas R Andreani

The problem with daemons is that they are usually controller by the init system (upstart or systemd) generally. So once you kill it, the init system will respawn it. You will have to stop it from the init system

systemctl stop sshd.service