[lsb-discuss] potential lsb-apache FVT problem and /etc/services
Wichmann, Mats D
mats.d.wichmann at intel.com
Tue Aug 22 05:34:52 PDT 2006
>From: lsb-discuss-bounces at lists.freestandards.org
>[mailto:lsb-discuss-bounces at lists.freestandards.org] On Behalf
>Of Matt Taggart
>Sent: Tuesday, August 22, 2006 4:24 AM
>To: lsb-discuss at freestandards.org
>Subject: [lsb-discuss] potential lsb-apache FVT problem and
>On IRC liqm ran into a problem when following the FVT for
>The instructions ask you to run "netstat -a | grep http". liqm
>was having problem testing on Ubuntu because while the server
>was clearly running, that command returned nothing.
>The problem was due to the fact that netstat uses
>/etc/services to map port to name, and Ubuntu (and Debian)
>have the following entries for web stuff,
>www 80/tcp http # WorldWideWeb HTTP
>www 80/udp # HyperText Transfer
>https 443/tcp # http
>protocol over TLS/SSL
>So while http works as a synomyn, since www is listed first
>that's what netstat prints, so the grep doesn't work. The
>instructions tell you to add http lines to /etc/services,
>but if they are added after the lines already in there it
>won't help. Maybe something like "netstat -an |grep :80"
>could be used instead?
Without saying anything (in this message) about the
broader topic, let me say about the apache "functional
verification test"... the idea was to write a set
of steps that a tester can follow that gives reasonable
confidence the application installed correctly, in
case of a daemon it is actually running, and performs
enough basic functions we can feel it's not just
In the case of apache, it's easy enough to provide
a different test for whether it's running since
apache itself provides a way to test: "apachectl status".
I'll make sure that works reasonably and update the
docs if Marvin doesn't beat me to it.
More information about the lsb-discuss