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

[LDM #YNE-961543]: Configuring ldm for use in user-space

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: [LDM #YNE-961543]: Configuring ldm for use in user-space
  • Date: Tue, 17 Jul 2012 13:36:55 -0600
> One could brute force the logging issue as follows:
> 
> - setup your LDM to write to ~ldm/logs/ldmd.log (which should be a link
> to ~ldm/var/logs/ldmd.log for new versions of the LDM)
> 
> - create a script whose purpose in life is to:
> 
> - stop the LDM
> 
> - rotate the LDM log file; meaning to rename ldmd.log.6 to ldmd.log.7,
> ldmd.log.5 to ldmd.log.6, ... ldmd.log to ldmd.log.1
> 
> This is easily done by 'ldmadmin newlog [-n numlogs] [-l logfile]'.
> 
> - start the LDM
> 
> - run the script from cron at the desired interval (once per day, once every
> other day, etc.)

The problem is that, unless it receives a HUP signal, the system logging daemon 
will continue writing to the old LDM log file -- even if that file's been 
renamed or deleted.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: YNE-961543
Department: Support LDM
Priority: Normal
Status: Closed