![]() You should only use killall if you with to kill multiple processes at once. I find that a lot of linux newbies often end up calling killall btsync if they wish to kill the process called btsync, but this isn't the proper way to do it, as there could be multiple instances of the btsync process. This unique PID can be used to kill or restart a process. These are unique identifiers for a single process. The number that is in the PID column is obviously the PID. USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND Have you ever run top or ps aux on your system? If so, you've probably seen a list with rows like this If you're unsure what a PID is and why it's important, read on otherwise, skip the next section and get into the meat of this tutorial. In order to overcome this, I figured the wisest approach would be to write a wrapper for the btsync program that would enable stop/start. There were multiple apparent walls that I was going to run into, as BitTorrent sync wasn't exactly written to be placed on a web server, so it lacks a few things like PID logging and the ability to start/stop the service. If you've gone through some of my other posts, you might remember a guide that I wrote about settings up BitTorrent Sync on a remote server, well today I'm going to expand on that a bit and add BitTorrent sync into my monit checks! I added in a few process checks for nginx, php-fpm, and postgres and it instantly was able to start tracking those processes for me. I was able to install it and get it up and running pretty hassle-free. ![]() Most recently I wanted to give monit a try, as I've heard some good things about it. Lots of setting up server monitoring, security, and automation. Over the past few days, I've been doing tons of DevOps work.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |