killport

I am absolutely installing this and starting to use it daily! For the even less patient there's also this (not mine): https://github.com/jkfran/killport

I love how there's a special case behavior for the hardcoded process name "docker." Just incredible: https://github.com/jkfran/killport/blob/main/src/linux.rs#L9... But seriously kids, take the time to learn Unix tools so you can save yourself from needing to write hundreds of lines of Rust when one shell command will do the same thing.

Looking at https://github.com/jkfran/killport/blob/3a43d037c08ab3aec730... , it will match on all four.

Curious about the following lines [1] [2]: let processes = procfs::process::all_processes().unwrap(); ... let process = p.unwrap(); Doesn't this use of unwrap cancel out one of the advantages of Rust which is to handle errors quite comprehensively? Here process could be null, and we try to access it the line after. edit: actually process won't be null, unwrap will panic. Got it. I still think a good error message would be better than exposing the user to a crash, but that's a matter of opinion. It seems like the whole point of using Rust, and also of such a tool, is to be robust and user-friendly (since it implements an UNIX one liner), and an unhandled crash could lower the confidence of the user in the tool. [1] https://github.com/jkfran/killport/blob/3a43d037c08ab3aec730... [2] https://github.com/jkfran/killport/blob/3a43d

Holy smokes: https://github.com/jkfran/killport/blob/main/src/linux.rs#L8...