Hi, Can anyone tell me how I can use awk to print out iport in this list?

24.232.133.87:8080 elite proxy Argentina (Munro)
62.178.214.128:7212 elite proxy Austria (Vienna)
201.24.189.149:6588 elite proxy Brazil (Brasília)
201.36.157.84:6588 elite proxy Brazil (Fortaleza)
200.159.255.70:3128 elite proxy Brazil (Rio De Janeiro)
200.244.50.206:6588 elite proxy Brazil (Rio De Janeiro)

For some reason awk -F: '{print $1,$2}' iplist spits out the entire thing.

Thanks

Don't set separator as :, there no : after the port, so awk will output the rest of the line as $2.

You could use default output separator blank and just print out $1.

There may be a better way, but this should do the job.
[EDIT] Ah, you want both the IP address and port. Then yes, vbisis's suggestions should work:

Why use heavy awk for this, when a simple "cut" is all you need?

Pipe output of that into:
to get resp. the IP and the port separately.

cut is a choice I often overlook because I learned about awk 1st.

A problem w/ cut for step 1: is the "IP:port" separated from the rest of the line by a space or a tab? awk doesn't care, cut does.

Also, if I am interpreting the orig. Q correctly, the desired output form is:
IP port
IP port
...

Using awk:
W/ cut:
To me, awk is easier to use when the output needs any formatting at all.

Agreed that awk is very handy and often useful to do a bunch of stuff (like formatting) all at once.
Downside, for me at least, is that, since awk is so powerful, it can be a little tricky to master.
And cut's failure to work well with regex's is indeed a downside.

However, I recommend using the commands for what they were originally designed. So I prefer not forcing "cut" to alter it's output (it wasn't designed for output formatting, unlike awk or sed). Instead, use a simple tool like sed (stream editing) or tr (transliteration) to do the formatting. Advantage of using sed or tr is, that

So,
then becomes something like

Thanks for the reminder about tr, another one I forget because I jumped right into sed & awk. (Literally -- a friend gave the O'Reilly book.)

While we're discussing string processing tools, let's not forget cat's options, it can do much more than just concatenate (RTFM cat).


This reminds me of quotation I ran into recently, which I paraphrase here:

Never use awk when cut will do.
Never use cut when sed will do.
Never use sed when tr will do.
Never use tr when cat will do.
Avoid cat at all costs.

Best I can manage from memory. If someone knows the original, please post a reference.

I would modernize this by adding
"Never use perl when awk will do."
at the beginning.