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.
>From: Mike Trexler <address@hidden> >Organization: NCSU >Keywords: 200005161729.e4GHTY416404 LDM log syslogd Mike, >I had my sys admin go back and stop and restart the syslog. Here's what she >sent me: >---- >sol.ncsc.org:/home/carole% ps -ef |grep syslog |grep -v grep > root 216 1 0 May 06 ? 2:43 /usr/sbin/syslogd > >sol.ncsc.org:/home/carole% /etc/init.d/syslog stop >Stopping the syslog service. > >sol.ncsc.org:/home/carole% ps -ef |grep syslog |grep -v grep > >sol.ncsc.org:/home/carole% /etc/init.d/syslog start >syslog service starting. > >sol.ncsc.org:/home/carole% ps -ef | grep syslog |grep -v grep > root 9550 1 0 08:59:39 ? 0:00 /usr/sbin/syslogd >---- OK, syslogd really has been restarted. Good. >So then I restarted the ldm, but still no cigar. anything else to try?? The only thing left is the configuration of local0.debug in /etc/syslog.conf. I was assuming that this is correct on your machine as I was under the impression that logging was working and then stopped (true?). The online LDM web pages cover setting up the entries in /etc/syslog.conf. >thanks >Mike Let me know if the syslog entry is OK. Tom