Read and write to TCP or UDP sockets with common bash tools
What do you think?
Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?
You must be signed in to comment.
What's this?
commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
Similar Commands
Stay in the loop…
- Follow the Tweets.
-
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10 - Subscribe to the feeds.
-
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)
while :; do ... done. Next, you read stdin using 'read' and echoing it. 'cat' does that (a non-useless use of cat :-)while :; do cat; done. Also you may want to expand you description to explain HOW it works. What the 'exec' statement is doing. Why you need the trap on EXIT. . Finally the examples you give are a bit misleading. If you use the command on google.com you get a redirect to https page (OK, so it works, but it's not a great example). Also, you can't test FTP because IIRC you make an outgoing call on port 20 and FTP makes an incoming call on port 21.