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.
Hi Ryan, re: > Steve - executing the hupsyslog did not make a difference. The messages > continued to be written to the rotated log (ldmd.log.1 in this case). Please send us the /etc/syslog.conf file from one of the systems you are seeing the logging problem on (the complete file, not a cut and paste of the its contents). Also, on the same system please send the output from: - uname -a - id ldm - ls -alt ~ldm Also, what is the result of the following: <as 'ldm'> logger -p local0.debug 'test of ldm logging' Which LDM log file does this get written to? Thanks in advance... Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: LSJ-519536 Department: Support LDM Priority: Normal Status: Closed