Command line app to do common netstat stuff written in Crystal
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Braydon Kains 83be1848c7 Fixed folder structure in spec 5 years ago
modules Structural refactor, defers responsibility for actions to operators, organizing code differently 5 years ago
operators It wasn't working right now it is 5 years ago
records Structural refactor, defers responsibility for actions to operators, organizing code differently 5 years ago
spec Fixed folder structure in spec 5 years ago
.editorconfig Using files from crystal init and reformatting everything to new editorconfig 5 years ago
.gitignore Using files from crystal init and reformatting everything to new editorconfig 5 years ago
.travis.yml Using files from crystal init and reformatting everything to new editorconfig 5 years ago
LICENSE Initial commit 5 years ago
README.md README update with searching process by name 5 years ago
main.cr Forgot to change a path 5 years ago
shard.yml Putting the right license in the shard file 5 years ago

README.md

eznet-cli: A command line application with netstat shortcuts

Have you ever needed to remember how to check what process is on a port and forgotten how to do it? There are loads of netstat commands that can be tricky to remember. This is a work in progress command line application to give direct shortcuts to those netstat operations.

Options

-v, --version

Show application version.

-h, --help

Show help menu.

-c PORT, --check-port=PORT

Get the name and process ID of the process running on a given port

-p PNAME, --find-process=PNAME

Find the port and ID of a process by name

-k PORT, --kill-port=PORT

Check the process running on a given port with the option to kill it if you'd like.

TODO

  • Add the ability to kill process on port
  • Add the ability to search for process by name
  • Maybe look into other cli operations? (getting IP?)
  • Come up with other useful stuff
  • Write up contributors guide
  • Decide how to do documentation (probably Github wiki?)
  • Write man page (figure out how to do that lol)
  • Figure out distribution/release
  • Set up CI (probably Travis)

Contributing

I don't know that I'm ready for contributors yet because I don't have a good contributors guide. I do plan to eventually open this up to contributors. If you have any ideas for future operations, please feel free to open an issue, I am happy to discuss ideas!