I am doing some info retrieving about which hosts are making requests when
from our main ldm site.
There are two dates in an entry (as printed below).
I know the "Apr 14 11:20:35" is a datetime of when the entry was logged.
What is the "20150414152033.872" date and time? This is the
"creation-time"? Most of the time, these two date-time stamps are within
seconds of each other. But not in this example
Mar 31 00:54:25 ldm1 208.180.46.165(noti)[24576] NOTE: Starting
> Up(6.11.7/5): 20150312170024.533 TS_ENDT {{CONDUIT,
> "^data/nccf/com/gfs/prod/gfs.+/gfs.t..z.pgrbf.+grib2.+"}}
>
Should I consider the "*start*" time (20150312170024.533) as an out-of-sync
clock on the downstream host?
Just wondering,
Donna
According to the documentation, I am looking at:
*MMM* *DD* *hh:mm:ss*
, *localhost*
,
*util*[*pid*]
,*level*
, "Starting Up" *(*maj.min.bug):
* criteria *(which is in the form:)
* start stop* {{*feedtype* "*pattern*"} [,...]}
where:
* start*
Is the start-time in the form *YYYYMMDDhhmmss.sss* or the string TS_ZERO.
The data-product creation-time must be equal-to or greater than this. The
string TS_ZERO is, effectively, the beginning of time.
* stop*
Is the stop-time in the form *YYYYMMDDhhmmss.sss* or the string TS_ENDT.
The data-product creation-time must be less-than or equal-to this. The
string TS_ENDT is, effectively, the end of time.
* pattern*
Is the ERE for matching the data-product identifier.
Re:
http://www.unidata.ucar.edu/software/ldm/ldm-6.10.1/basics/logfile-format.html
