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.
Frank, > Here are the results. > > [ldm@UMLGempak ~]$ uname -a > Linux UMLGempak 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 > x86_64 x86_64 x86_64 GNU/Linux > [ldm@UMLGempak ~]$ uname -a > Linux UMLGempak 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 > x86_64 x86_64 x86_64 GNU/Linux > [ldm@UMLGempak ~]$ cd > [ldm@UMLGempak ~]$ ls -l bin/hupsyslog > -rwsr-xr-x. 1 root ldm 11199 Nov 20 15:41 bin/hupsyslog > [ldm@UMLGempak ~]$ ls -l var/logs/ldmd.log > -rw-rw-r--. 1 ldm ldm 0 Nov 20 15:44 var/logs/ldmd.log > [ldm@UMLGempak ~]$ ps -ef | grep syslog > root 1653 1 0 Nov19 ? 00:00:00 /sbin/rsyslogd -i > /var/run/syslogd.pid -c 5 > ldm 5192 1 0 Nov19 ? 00:00:00 /usr/bin/pulseaudio --start > --log-target=syslog > ldm 29584 20208 0 17:48 pts/1 00:00:00 grep syslog > [ldm@UMLGempak ~]$ fgrep local0 /etc/*syslog*.conf > local0.none /var/log/messages > local0.* /home/ldm/var/logs/ldmd.log Those results look good. > I just checked and selinux was enabled. I've disabled it, but probably > need to restart for that to take effect. > Would that have prevented the logging? Yup. (I keep forgetting about SELINUX.) You'll either need to reboot or set SELINUX to "permissive", in which case you'll also get a message in the system log file for every message in the LDM log file. > Frank Regards, Steve Emmerson Ticket Details =================== Ticket ID: YLA-231641 Department: Support LDM Priority: Normal Status: Closed