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.
Xiang, > This is our LDM version: 6.11.6. in UVA FDT. That version won't work with syslog-ng(8). > And this is the current configuration in syslog-ng.conf: > > destination d_loghost { tcp("141.211.43.110" port(5140)); }; > destination d_cons { file("/dev/console"); }; > destination d_mesg { file("/var/log/messages"); }; > destination d_auth { file("/var/log/secure"); }; > destination d_mail { file("/var/log/maillog" sync(10)); }; > destination d_spol { file("/var/log/spooler"); }; > destination d_boot { file("/var/log/boot.log"); }; > destination d_cron { file("/var/log/cron"); }; > destination d_ipt { file("/var/log/iptables"); }; > destination d_mlal { usertty("*"); }; > destination d_drops { file("/var/log/dropped_messages.log"); }; > > Should I add new entry to append LDM log messages to the LDM log file? Or > should I update the LDM? If you know how, then I would appropriately modify the syslog-ng(8) configuration-file to have it log messages from "local0" to the LDM log file. You will also have to change the value of the SYSLOG_PIDFILE macro in the file "src/config.h" to "/var/run/syslog-ng.pid" and rebuild the hupsyslog(1) utility: cd hupsyslog make install cd .. su make root-actions Regards, Steve Emmerson Ticket Details =================== Ticket ID: EYZ-451528 Department: Support LDM Priority: Normal Status: Closed