Benjamin Allan

add log_level integration test and reduce order dependence between load and log_level

30

fixes #1343 (excess order dependence between load and log_level). updates the header documentation for ovis_log_set_level_by_name. Make the ovis_log_t pointer opaque outside ovis_log.c illustrates #1342 (excess reordering of log_level statements breaks...

The log_level command for a subsystem does not work before the subsystem is registered (plugin loaded), which makes it impossible to create prolog scripts setting subsystem log levels that are...

reordering of subsystem log statements defeats log_level commands for debugging

2

For the input ``` log_level level=WARNING load name=${plugname} log_level name=sampler.dstat level=INFO config name=${plugname} producer=localhost${i} schema=${plugname} instance=localhost${i}/${plugname} component_id=${i} start name=${plugname} interval=1000000 offset=0 log_level name=sampler.dstat level=DEBUG ``` the driver reorders the statements...

Has anyone run into an error like the following? Can't run ldmsd_controller. ldd doesn't turn up an unsatisfied libraries. Traceback (most recent call last): File "/opt/X/current/bin/ldmsd_controller", line 66, in from...

return test_slps to installcheck-local with time,zap io limits

4

this checks the return code and wraps test_slps in 'timeout' so it cannot hang forever, should a transport hang occur. also fixes #1095

tx2mon on OVIS-4 references sampler base log pointer

2

``` CC tx2mon.lo ../../../../../ldms/src/sampler/tx2mon/tx2mon.c: In function 'create_metric_set': ../../../../../ldms/src/sampler/tx2mon/tx2mon.c:417:8: error: 'struct base_data_s' has no member named 'log' base->log(OVIS_LERROR,"base_set_new: ldms_set_publish failed for %s\n", ```

transient sets aggregated with push=onchange not leaving L1 after deletion on L0

14

The pid sampler (linux-proc-sampler) creates sets for pids it's notified of and clears these sets when the pid monitored goes away. It appears that ~1/3 of these sets (388/1200) never...

feature proposed to control prdcr overhead

2

At present we cannot limit the result of ``` prdcr_add name=X host=X type=active xprt=sock auth=ovis port=411 interval=20000000 prdcr_start name=X ``` to transport only sets or only streams; currently we always...

use-after-free in xprt/stream

1

For the teardown script prdcr_del step in: ``` updtr_stop name=allhosts updtr_prdcr_del name=allhosts regex=.* updtr_del name=allhosts prdcr_stop name=localhost1 prdcr_unsubscribe regex=.* stream=slurm prdcr_del name=localhost1 ``` I get the following use after free...

it's very difficult (and ugly) to correctly configure a daemon with both pull and push sets. Example of unhappiness: # pull updtr_add auto_interval=true name=all_admin1 interval=1000000 offset=230000 updtr_prdcr_add name=all_admin1 regex=.* updtr_match_add...