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

[LDM #FUT-767365]: LDM file logging

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 #FUT-767365]: LDM file logging
  • Date: Tue, 28 Dec 2010 15:11:26 -0700
Daniel,

> I'm looking at  681 and 662

I'm sorry, but I don't know what you mean by "681" and "682". Are those line 
numbers? Version identifiers?

> both fails to implement the -l option.
> 
> in both i can "fix" it by adding
> 
> if (length($log_file)) {
> $cmd_line .= " -l $log_file";
> }
> 
> in the "start_ldm"  sub
> 
> if this option is being deprecated, it would be nice have an option to
> change the syslog facility id without having to recompile ldm

The "start" command was never intended to have a "-l" option. The only command 
for which a "-l" option makes sense is the "newlog" command.

Configuring the log file of an LDM system requires that you explicitly set a 
runtime configuration variable. Prior to LDM 6.9, that variable is $log_file in 
the ldmadmin(1) configuration-file (~/etc/ldmadmin-pl.conf). Version 6.9 uses 
the registry parameter "/log/file".

> thanks
> 
> Daniel Bourque
> Sr. Systems Engineer
> WeatherData Service Inc
> An Accuweather Company
> 
> Office (316) 266-8013
> Office (316) 266-8000 ext. 8013
> Mobile (316) 640-1024

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: FUT-767365
Department: Support LDM
Priority: Normal
Status: Closed