search for: stats_config

I have a server which I haven't installed that I have to maintain. This server uses MySQL, it has an asterisk database and in there some mysterious tables: stats_action, stats_agent, stats_callid, stats_config, stats_estados, stats_qstats, stats_queue, stats_queuexagent. I say mysterious because I don't have a clue about who is generating them. I did a grep for their names in /var, /root and /etc with no luck. Does anybody have any ideas what might be generating them, and populating them? Thanks....

I like this change. I think we were overloading the config_complete method before to do two different things (complete configuration; do any allocation/housekeeping necessary before we can start serving). The only questions in my mind are whether we want this before 1.18, and whether the name ("get_ready") is a good one. Rich.

...s_cache (struct nbdkit_next_ops *next_ops, void *nxdata, static struct nbdkit_filter filter = { .name = "stats", .longname = "nbdkit stats filter", - .version = PACKAGE_VERSION, .unload = stats_unload, .config = stats_config, .config_complete = stats_config_complete, diff --git a/filters/truncate/truncate.c b/filters/truncate/truncate.c index 93d8f074..ae1f8624 100644 --- a/filters/truncate/truncate.c +++ b/filters/truncate/truncate.c @@ -385,7 +385,6 @@ truncate_cache (struct nbdkit_next_ops *next_ops, void *nxda...

There's enough here to need a review; some of it probably needs backporting to stable-1.12. This probably breaks tests on Haiku or other platforms that have not been as on-the-ball about atomic CLOEXEC; feel free to report issues that arise, and I'll help come up with workarounds (even if we end up leaving a rare fd leak on less-capable systems). Meanwhile, I'm still working on my

This is a major rewrite compared to my v1 series, where I've tried a lot harder to ensure that we still accommodate building on Haiku (although I have not actually yet fired up a Haiku VM to try it for myself). I also managed to make the sh plugin fully parallel, on capable platforms. See also my question on patch 10 on whether I've picked the best naming convention. Eric Blake (17):