[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
20000310: Plymouth NOAAPORT receivers and GINI imagery (cont.)
- Subject: 20000310: Plymouth NOAAPORT receivers and GINI imagery (cont.)
- Date: Fri, 10 Mar 2000 08:30:41 -0700
>From: Jim Koermer <address@hidden>
>Organization: Unidata Program Center
>Keywords: Plymouth NOAAPORT GINI ADDE
Jim,
>I finished setting up the web access to the GINI satellite data using
>McIDAS as the display package. I still need to add some items, such as,
>choice of projections and enhancements, but it really works well. The
>main problem with the setup was getting the McIDAS environment working
>from a web cgi script.
>
>It can be accessed at
>
> http://snow.plymouth.edu/mcidas_sat.html
Very nice! I went to the page from my home machine right after reading
your message and put up a 1 km VIS centered over Boston. Everything went
very smoothly AND quickly.
>I have a few ADDE questions:
>
> (1) Have you finished with the TCP wrappers on snow?
No. I started the TCP wrapper setup on Wednesday evening, but I
couldn't find the 'tcpd' module that is needed (at least this is what
is needed on other systems). I was going to wait and ask Mike Schmidt,
our system administrator, about this, but I was not in at work
yesterday (out skiing no less) and Mike will not be in today. Perhaps
you can answer the mystery of where 'tcpd' is, or what should be used
in its place.
I listed out man pages on snow that seem to indicate that tcpd should
exist:
% man -k tcp
tcp(4) - Internet Transmission Control Protocol
tcpdchk(8) - tcp wrapper configuration checker
tcpdmatch(8) - tcp wrapper oracle
tcpdump(1) - dump traffic on a network
tcpslice(1) - extract pieces of and/or glue together tcpdump files
ttcp(4) - Transmission Control Protocol Extensions for
Transactions
%man tcpdchk
TCPDCHK(8) TCPDCHK(8)
NAME
tcpdchk - tcp wrapper configuration checker
SYNOPSYS
tcpdchk [-a] [-d] [-i inet_conf] [-v]
DESCRIPTION
tcpdchk examines your tcp wrapper configuration and
reports all potential and real problems it can find. The
program examines the tcpd access control files (by
default, these are /etc/hosts.allow and /etc/hosts.deny),
and compares the entries in these files against entries in
the inetd or tlid network configuration files.
...
The paragraph under DESCRIPTION mentions 'tcpd' specifically, but I
can not find it on your system.
> (2) Is there anything from here that I have to administer? e.g.
> host entry table for ADDE access, etc.
I fully intended to give you a blow-by-blow description of the ADDE
setup for your GINI imagery when all the Ts have been crossed and Is
dotted. Can I still wait on this, or should I fill you in now?
What I have left to do is:
o install some newly reworked code for the servers: I mentioned before that
the headers in your GINI images looks a little different than the
ones in ours. I want to rework my code so that it can correctly
interpret the header no matter what (the issue is not in the GINI image
header, but, rather, in the transmission header. I should be able
to put in some logic that handles variable length transmission headers
seamlessly)
o get the TCP wrappers working
o send you a detailed document on how things work and how you can modify
the GINI configuration file to specify who you want to allow data
access
Tom