[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20030206: McIDAS - Tru64 - ptlist not listing CMAN stations (cont.)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20030206: McIDAS - Tru64 - ptlist not listing CMAN stations (cont.)
  • Date: Thu, 06 Feb 2003 18:28:19 -0700
>From: "Angel Li" <address@hidden>
>Organization: University of Miami
>Keywords: 200301211600.h0LG0gD13023 McIDAS-XCD CMAN

Angel,

re: installed updates to the ship/buoy data monitor

>I was killing dmsyn (or something like that) processes every so often that
>went compute bound. Is this the same problem?

Yes, this is the same problem.  The executable you were killing was
dmsyn.k.  I watched the newly built version several times after I did
the update, and have not seen it misbehave.  Please let me know if you
see something different.

>sapodilla has been sitting outside our campus firewall but will end up behind
>it sooner or later. Which ports do I need to leave open for the LDM to
>function properly?

You should leave port 388 open for the LDM.  This relies on the
installation done by our recommendations where rpc.ldmd and hupsyslog
have setuid root privilege.  If this is not done, the LDM has to
connect using the port mapper.  We feel that the port mapper is much
more insecure than the LDM.

>Thanks for repointing the DATALOC for RTPTSRC.

No problem.  Like I said, the situation you were in is a classic ADDE
gotcha.

Tom