StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10629259
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2012-05-17T02:54:42.140
FavoriteCount
0
LastActivityDate
2013-07-20T05:08:44.590
LastEditDate
2013-07-20T05:08:44.590
LastEditorUserId
269073
OwnerUserId
368630
ParentId
10628972
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
I'm looking at the output of my <code>netstat</code> command, and see this: <pre><code>tcp4 0 0 10.0.1.10.56941 64.34.119.101.80 ESTABLISHED tcp4 0 0 10.0.1.10.56936 64.34.119.101.80 ESTABLISHED tcp4 0 0 10.0.1.10.56932 64.34.119.101.80 ESTABLISHED tcp4 0 0 10.0.1.10.56929 64.34.119.101.80 ESTABLISHED tcp4 0 0 10.0.1.10.56922 64.34.119.101.80 ESTABLISHED tcp4 0 0 10.0.1.10.56914 64.34.119.101.80 ESTABLISHED tcp4 0 0 *.* *.* CLOSED tcp46 0 0 *.80 *.* LISTEN tcp4 0 0 127.0.0.1.49153 *.* LISTEN tcp4 0 0 127.0.0.1.49152 *.* LISTEN tcp4 0 0 *.631 *.* LISTEN tcp6 0 0 *.631 *.* LISTEN </code></pre> I take it that the port is the last number in the five part dotted output. That means that <pre><code>grep "\.80 " </code></pre> will pick up only port 80. The <code>\.</code> says to pick up the period. (Normally the period means any character in regular expressions). And, by putting a space after the <code>80</code>, you'll guarantee that you're not going to pick up port 8080. In fact, you're guaranteed that you're not going to pick up IP addresses that have <code>.80</code> in them. In fact, I'd recommend to use <code>awk</code> instead of <code>grep</code>. With <code>awk</code>, you can specify fields and do a bit more processing: <pre><code>$ netstat -ant | awk '$6 == "LISTEN" && $4 ~ /\.80$/' | wc -l </code></pre> With <code>awk</code> each column automatically becomes a separate field. Field #6 ($6 in awk) is the one that says <code>ESTABLISHED</code>, <code>CLOSED</code>, <code>LISTEN</code> in it. Field <code>$4</code> is the first column IP address one. In the above, I'm looking for lines that have the word LISTEN in the sixth field, and where field #4 matches the regular expression <code>\.80$</code>. The <code>$</code> is an anchor to the end of the string, and the <code>\.</code> is picking up a decimal point and not representing any character. The <code>awk</code> command automatically prints out each line that matches, so I don't have to specify that. Awk is really a programming language. It assumes a read loop for each line in the file. You can have a <code>BEGIN</code> clause that gets executed before the file is read and an <code>END</code> clause that executes after the file has been read. The various fields are numbered and represented with a dollar sign. The special <code>$0</code> variable represents the whole line. Special variables like like NF gives you the number of fields in a line and NR gives you the number of lines read in. You also have a whole slew of functions to help parse text, etc. Here's a full blown version of the <code>awk</code> script that basically lays out everything for you, and does its own line counting, so you don't have to pipe to <code>wc -l</code>.: <pre><code>$ netstat -ant | awk ' BEGIN {total = 0} END {print "There are " total " lines I found"} { if ($6 == "LISTEN" && $4 ~ /\.80$/) { total = total + 1 } }' </code></pre> <hr> <h1>Appendage</h1> OP gets the following output: <pre><code>tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN </code></pre> In this case, try either: <pre><code>$ netstat -ant | awk '$6 == "LISTEN" && $4 ~ /:80$/' | wc -l </code></pre> Where the <code>\.</code> is replaced by a <code>:</code> or... <pre><code>$ netstat -ant | awk '$6 == "LISTEN" && $4 ~ /[\.:]80$/' | wc -l </code></pre> Which uses <code>[\.:]</code> which will get it whether it's a colon or a period. Heck, might as well go all the way... <pre><code>$ netstat -ant | awk '$6 == "LISTEN" && $4 ~ /[^0-9]80$/' | wc -l </code></pre> The <code>[^0-9]</code> means not a numeric character. You can't go wrong with that. This way, whether it's a period, a colon, a semi-colon, a comma, or whatever separator your version of <code>netstat</code> uses, it will work.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POhow to grep listening on port 80 that can also filter other port contain 80 such as 8080 8088 ...?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDavid L
UserOwnerUserId
1. USDavid W.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POhow to grep listening on port 80 that can also filter other port contain 80 such as 8080 8088 ...?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.