[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20030519: LDM not logging on Sun Solaris 5.8 (cont.)

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.

  • Subject: 20030519: LDM not logging on Sun Solaris 5.8 (cont.)
  • Date: Mon, 19 May 2003 13:53:44 -0600
>From: Chris Novy - Systems <address@hidden>
>Organization: SIU
>Keywords: 200305160023.h4G0NBLd007554 LDM-6 ldmadmin stop

Hi Chris,

re: LDM entries in /etc/syslog.conf

>It *was* there once but is not there now!  I wonder if the sysadmin
>removed it.

Could be...

>syslogd *is* running, however.

OK.

>So where can I find a fresh template for the my missing syslog.conf file?

http://my.unidata.ucar.edu/content/software/ldm/ldm-6.0.11/install/preinstall-steps.html

Follow through the directions of all preinstallation configurations.
Also, after making changes to /etc/syslog.conf, you have to send the
syslogd a SIGHUP signal to tell it to reread its configuration file.
This can be done as 'root' after finding out the process ID of
syslogd, or as 'ldm' using the 'hupsyslog' command that is part of
the LDM binaries.

I have sometimes found that it is a good idea to exit the LDM while
doing the /etc/syslog.conf mods.

Tom