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

20031027: LDM - Current Status, 20031023

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: 20031027: LDM - Current Status, 20031023
  • Date: Mon, 27 Oct 2003 09:30:12 -0700
Mark,

> From: "Mark Ziemer" <address@hidden>
> To: "Andy Miller" <address@hidden>,
>        "Holly Reckel" <address@hidden>,
>        "Lipinski Dan" <address@hidden>
> Cc: "Robert Wavrin" <address@hidden>,
>        "Bruce Aslesen" <address@hidden>,
>        "Daniel Luna" <address@hidden>,
>        "John Halquist" <address@hidden>,
>        "Mike Deweese" <address@hidden>
> Subject: LDM - Current Status, 20031023
> Date: Thu, 23 Oct 2003 14:07:30 -0500

The above message contained the following:

> 1.    The major problems with data transfer between the USGS ND and us via
> ldm has been found.  For your info, the problem was that when RedHat Linux
> as installed, the firewall option was included at the "high" level.  To make
> things worse, they are having problems turning the firewall off.  But, this
> is being fixed now and we do know what the work around is.  Run the ldmd
> process as root.

Just FYI, I just finished conducting a training workshop on the LDM
using Red Hat 9 systems for the workshop computers.  The security
configuration on every system was the "high" level default.  The
workshop went well -- in particular we did not need to execute the LDM
as root.  Having the LDM daemon program-file, rpc.ldmd, be owned by root
and setuid-owner was sufficient.

There were no independent firewalls between the workshop computers.

Regards,
Steve Emmerson
LDM Developer