Mlogger: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
Notes | Notes | ||
<span style="color:darkcyan;">''mlogger''</span> creates the [[Logger | <span style="color:darkcyan;">''mlogger''</span> creates the [[/Logger ODB tree]] with default values the first time it is run | ||
The <span style="color:darkcyan;">''mlogger''</span> application requires an existing [[/Equipment tree]] in the ODB | The <span style="color:darkcyan;">''mlogger''</span> application requires an existing [[/Equipment tree]] in the ODB | ||
Once the <span style="color:darkcyan;">''mlogger''</span> is running, you should be able to monitor its state with [[mstat]] or with [[mhttpd]]. | Once the <span style="color:darkcyan;">''mlogger''</span> is running, you should be able to monitor its state with [[mstat]] or with [[mhttpd]]. | ||
Revision as of 12:34, 6 August 2013
mlogger - MIDAS Logger
The MIDAS Logger, mlogger, is the main application that collects data from one or more frontends under certain conditions and stores them onto a physical device such as disk or tape. It also acts as a history event collector and can also store data in a mySQL database. The features and customization of the logger utility are fully described in the section Logging in MIDAS .
Arguments
[-h ] : help
[-e exptname ] : experiment name (see odbedit - ODB Editor and run control utility)
[-D ] : start program as a daemon (UNIX only).
[-s] : Save mode (debugging: protect ODB).
[-v] : Verbose (not to be used in conjunction with -D).
Usage
>mlogger -D
Notes
mlogger creates the /Logger ODB tree with default values the first time it is run The mlogger application requires an existing /Equipment tree in the ODB Once the mlogger is running, you should be able to monitor its state with mstat or with mhttpd.