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

[Support #GIL-635869]: Re: LDM configuration for Syslog-ng

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: [Support #GIL-635869]: Re: LDM configuration for Syslog-ng
  • Date: Fri, 02 Mar 2007 15:00:02 -0700
Marcus,

> I'm changed the script HUPSYSLOG in order to work with syslog-ng on Open
> Suse 10.2.
> I finally have success. But one thing is bothering me. When I run the
> "ldmadmin stop", the LDM logs its messages on the "ldmd.conf". But when
> I do "ldmadmin start" the syslog-ng logs the start message into the
> "ldmd.log.1". The messages that come after that, seems to logging into
> the correct file (ldmd.log). My question is this: when the ldmadmin
> rename the logs, it create the ldmd.log after or before to restart the
> syslog daemon? To me looks that it does this after to create the file.
> 
> Any hint?

The command "ldmadmin start" renames the log files, creates an empty
new log file, and then sends a HUP signal to the syslog daemon --
in that order.

I suspect that the HUP signal that you're sending to the syslog-ng
process doesn't do anything and that the log messages are going
into the new file only after the syslog-ng process times-out on
the log file and reopens it.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: GIL-635869
Department: Support LDM
Priority: Normal
Status: Closed