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

RE: 19990919: I want to keep LDM messages out of my 'messages' file! (fwd)

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: RE: 19990919: I want to keep LDM messages out of my 'messages' file! (fwd)
  • Date: Mon, 20 Sep 1999 10:21:17 -0600 (MDT)

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Mon, 20 Sep 99 09:44:49 -0400
From: address@hidden
To: address@hidden
Subject: RE:  19990919: I want to keep LDM messages out of my 'messages' file! 

Using LDM 5.0.5 on a RH Linux 4.2 system, LDM messages
have always been written to /var/log/messages even with the local0.none
line present in my syslog.conf.  This version of the LDM was
built using Rob Cermak's fix for ulog.c to enable logging
on Linux systems.

Wondering if anyone out there who is using a later version of the LDM
and/or RH Linux has had success excluding the ldm messages from the
messages file?

Thanks,

Kevin Tyle <address@hidden>
MESO, Inc.

Steve Chiswell wrote:
>Gilbert,
>
>You should have the local0.none log command on your
>/var/log/messages line in your syslog.conf file. This should
>be shown in the LDM setup information.
>
>Use local0.debug for your ldm logging to ldmd.log. Since your
>/var/adm/messages and/or /dev/console lines in /etc/syslog.conf
>probably have a *.err or *.warn, you need to tell syslog
>to exclude the local0 logging with the local0.none entry.
>
>Steve Chiswell
>Unidata User Support