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.

Go to file

Braydon Kains d48d331e81 Putting the exit where it belongs		5 years ago
ltnp	Can check for process by name	5 years ago
modules	Added ability to kill process found on port	5 years ago
spec	Putting the exit where it belongs	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 updated	5 years ago
main.cr	Putting the exit where it belongs	5 years ago
shard.yml	Using files from crystal init and reformatting everything to new editorconfig	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

-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
[] 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!