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

[Support #KGJ-163844]: Request for upstream LDM

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: [Support #KGJ-163844]: Request for upstream LDM
  • Date: Fri, 01 Jun 2007 09:04:33 -0600
Evan,

> Here are answers to your questions below:<br>
> <br>
> 1)&#65533;  I made the changes to the /etc/syslog.conf file as given on the 
> LDM
> website under the "Preinstallation steps".&#65533;  <br>
> <br>
> 2)&#65533;  I have not checked if the "syslogd" daemon is running.&#65533;  I 
> have not
> dealt with this before.&#65533;  How would I do this on Fedora Core 6?<br>

What is the output of the command "ps -ef | grep syslog"?

> 3)&#65533;  The LDM programs "bin/hupsyslog" and "bin/roc.ldmd" are setuid and
> owned by "root".<br>
> <br>
> 4)&#65533;  The LDM log file "logs/ldmd.log" file exists and is writable.<br>
> <br>
> 5)&#65533;  The command "logger -p local0.debug LDM Test" does not out a
> message in the LDM logfile.<br>
> <br>
> 6)&#65533;  The file /etc/selinux/config exists and the SELINUX variable is 
> set
> to disabled.<br>

Does the timestamp on the file "/etc/selinux/config" indicate that
it was modified after the latest reboot?  If so, then the computer
will need to be rebooted in order for the modification to take
effect.  Even if it doesn't appear necessary, I've seen a reboot
fix LDM logging problems.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: KGJ-163844
Department: Support LDM
Priority: Normal
Status: On Hold