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

[LDM #POI-149293]: LDM log rollover

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 #POI-149293]: LDM log rollover
  • Date: Tue, 30 Jan 2018 17:39:59 -0700
James,

> Ok, here we go:
> 
> ldm@llwxldm2new[247]: ls -l bin/refresh_logging && cat bin/refresh_logging
> 
> -rwxr-xr-x. 1 ldm root 534 Sep 19 19:05 bin/refresh_logging
> #       File: refresh_logging.in
> # Created on: Feb 27, 2016
> #     Author: Steven R. Emmerson
> #
> # This script refreshes LDM logging when the package is built without the
> # "--with-ulog" option. A SIGUSR1 is sent to the LDM process-group if the LDM 
> is
> # running; otherwise, nothing will happen.
> 
> set -e
> pid_pathname="/opt/ldm"/ldmd.pid
> if test -r "$pid_pathname"; then
>     if pid=`cat "$pid_pathname"`; then
>         # NB: Using command(1) avoids non-standard shell built-in kill(1)-s
>         command kill -s USR1 -- -"$pid"
>     fi
> fi
> ldm@llwxldm2new[248]: pwd
> /opt/ldm
> 
> However, I'm starting to see the problem--we have no ldmd.pid file. Is that
> because we start the LDM using our scripts?

The command "ldmadmin start" ensures that the file "$LDMHOME/ldmd.pid" exists 
and contains the PID of the top-level LDM server. Quite a few components depend 
on this.

> Can I make such a file in my scripts?

Yes and you'd better. :-)

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: POI-149293
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.