[LDM #XYB-742568]: ldmadmin-pl.conf

Chris,


> Two quick questions:
> 
> - In the ldmadmin-pl.conf file hostname needs to be a fully qualified
> name, which we do not have on the aircraft by default.  The aircraft
> computer has two hostnames, the internal name which is what you would
> get when you type uname or hostname, and the DynDNS name only know to
> the outside world and is the name used by ldm's trying to access the
> aircraft.

The hostname in the "ldmadmin" configuration-file, ldmadmin-pl.conf,
is used  by 1) the rtstats(1) utility to set the name of the system
from which it's reporting; and 2) by the LDM in setting the "origin"
field of a data-product.  Neither one if these things is mission
critical, so you can set the hostname to whatever you want.  Just be
sure to have a period in the name (otherwise, the ldmadmin(1) script
won't work).

> So which should I hardcode hostname to be in the ldmadmin-pl.conf file
> (rafgv.dyndns.org or acserver.gv.ucar.edu the latter not being a real
> name accessible to anything outside the aircraft)?

Either one will work, as would "gulfstream5.ucar.edu".

> - Can I comment out the stats line in the ldmd.conf file, doesn't seem
> appropriate to have stats going across low bandwidth (2400 baud) links
> (unless the traffic is truely minimal)?

Statistics reporting isn't mission critical, so feel free to not
do that.  We find looking at the plots useful for monitoring the
health of the system.

> Thanks,
> Chris


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: XYB-742568
Department: Support LDM
Priority: Normal
Status: Closed