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

[Fwd: ldmadmin (-o , -m)]

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: [Fwd: ldmadmin (-o , -m)]
  • Date: Mon, 16 Jul 2001 16:38:58 -0600
Teresa Van Hove wrote:
> 
> Jeff,
> 
> Well, I'll play with adding a -o 1209600 to the /bin/ldmadmin script
> without any -m flag on one of the ldm5.12 version cpu's.  We got an
> error message at ldmadmin startup on the vs 5.08 machine until we also
> added -m and set it larger than the -o flag.
> 
> Actually just tried this on the ldm 5.12 version that collects the
> suominet data for processing and again get this error message (right to
> the screen at ldmadmin start) :
> rpc.ldmd: invalid toffset 1209800 > max_latency 3600Usage: rpc.ldmd
> [options] [conf_filename]
> 
> So regardless of the theory, in practice I seem to need to use both
> flags, with -m set a bit bigger than -o, to get the -o (toffset) value
> that I want.
> 
> Thanks,
> Teresa
> 

Hi Jeff,

Well, I saw the bit of code that generates this message - it certainly
seems to conflict with the man page.  I scanned the cvs log - Glen
messed with this back in 1995 - maybe he didn't update the man page, I
can't tell.  

So, the software wants toffset to be strictly less than max latency. 
Time to graciously backpedal...

Welcome to support! :-)

Anne  

p.s. I'm cc'ing this to support-ldm so there's a record of what we found
in the archives.  Tommorrow lets talk about support-ldm.