Looking at the contents of
/proc/net/tcp it appears
to be a formatted report. Personally I would first do a
sanity check that I know what the header line is (makes
porting the code later easier) then just extract
substrings using
substr or
unpack and do hash lookups
for the action. Much more efficient than looping.
#! /usr/bin/perl -w
use strict;
@tcp_status = `cat /proc/net/tcp`;
unless (" st " eq substr($tcp_status[0], 33, 4) and
" rem_address " eq substr($tcp_status[0],19, 15)) {
die "/proc/net/tcp has an unexpected format";
}
my %service = qw(
0050 www
0016 ssh
1A0B irc
0015 ftp
);
my %count = map {($_, 0)} values %service;
foreach my $line (@tcp_status) {
if ("01" eq substr($line, 34, 2)) {
my $serv_code = substr($line, 29, 4);
if (exists $service{$serv_code}) {
++$count{$service{$serv_code}};
}
}
}
# Finish as Tye did
(These numbers are for a 2.0 series Linux kernel.)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.