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.
Neil, > Got it. Thanks. > Re logging, the upstream reports his ldm isn't logging to ldmd.log. > Rings a bell for me but I don't quite remember -- what did he miss > during the ldm build and config? The upstream LDM might not log for several reasons: 1) the system logging daemon isn't running; 2) SELINUX is not disabled; 3) the files "~/bin/hupsyslog" and "~/bin/ldmd" aren't owned by root and setuid; 4) the O/S doesn't honor the setuid bit for root-owned files on the disk partition that contains "~/bin"; 5) the directory "~/logs" doesn't exist; and 6) the file "~/logs/ldmd.log" can't be created by the LDM user. > Neil R. Smith address@hidden 979-845-6272 > Senior IT Specialist, Dept. Atmospheric Sciences, Texas A&M Univ. Regards, Steve Emmerson Ticket Details =================== Ticket ID: CWN-205523 Department: Support LDM Priority: Normal Status: Closed