Evan, > Here are answers to your questions below:<br> > <br> > 1)� I made the changes to the /etc/syslog.conf file as given on the > LDM > website under the "Preinstallation steps".� <br> > <br> > 2)� I have not checked if the "syslogd" daemon is running.� I > have not > dealt with this before.� How would I do this on Fedora Core 6?<br> What is the output of the command "ps -ef | grep syslog"? > 3)� The LDM programs "bin/hupsyslog" and "bin/roc.ldmd" are setuid and > owned by "root".<br> > <br> > 4)� The LDM log file "logs/ldmd.log" file exists and is writable.<br> > <br> > 5)� The command "logger -p local0.debug LDM Test" does not out a > message in the LDM logfile.<br> > <br> > 6)� 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
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.