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 Massoud, re: > I have attached the following files you have asked for. > > Here's also the ouput. > > [ldm@wimden etc]$ ps -eaf | grep syslog > root 1979 1 0 09:03 ? 00:00:00 syslogd -m 0 > ldm 5619 5016 0 16:09 pts/2 00:00:00 grep syslog OK, the output from 'ps' shows that syslogd is running... good. I have attached a revised copy of syslog.conf that you should put in your /etc directory. Please make sure that the new file has the same permissions as the one it replaces! After copying the revised syslog.conf file to /etc, do the following: <as 'ldm'> cd ~ldm/logs rm ldmd.log touch ldmd.log hupsyslog logger -p local0.debug 'test of LDM logging' Your ~ldm/logs/ldmd.log file should now contain 'test of LDM logging'. If it doesn't, we still have a problem. If it does, then restart your LDM and take a look at the log messages being written to the log file: <as 'ldm'> ldmadmin restart ldmadmin tail > Thanks again. > > Massoud > > 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: VJN-743814 Department: Support IDD Priority: Normal Status: Closed