similar to: [PATCH matahari] Moves the CPU properties into the Host API space.

Refactoring the previous patch ended up creating two deltas. This patch pushes them both together into a single commit.

Created a new class to represent network interface devices, named NetworkDeviceAgent. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- src/Makefile.am | 9 +- src/host.cpp | 26 +++-- src/host.h | 4 +- src/linux_platform.cpp | 70 +++++++++++ src/linux_platform.h | 4 + src/networkdevice.cpp | 49 ++++++++ src/networkdevice.h |

It provides an initial implementation, LinuxPlatform, which is by default included in the build. Later code will refactor the build process to include the appropriate implementation depending on the target platform. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- src/Makefile.am | 4 ++ src/linux_platform.cpp | 117 ++++++++++++++++++++++++++++++++++++++++++++++++

This is the first step towards separating the APIs from the means by which they are carried between the remote and local system. Added a few new classes and types: * HostTransport - defines a type for talking to the Host * Host - the public contract for the host APIs * HostAgent - the QMF transport layer Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- .gitignore

Replaced the previous HostWrapper class with the new HostAgent class, which more closely resembles the style of the ProcessorsAgent class. Deleted the HostWrapper class entirely. Refactored the daemon entry point to reduce the number of methods invoked in order to start or stop the HostAgent instance. Moved the NICWrapper's setupQMFObject method from private to public so that it can be

In looking at the code I realized that the last of the HAL depenencies were removed with this patch. So, I'm pushing an updated patch that contains none of the HAL code in it.

The Multiplexer lets Matahari register APIs and then call them by that registered name. APIs are function pointers in the form of: const char* function(const char *); where the API takes as input a descriptor containing any arguments, and returns an array containing the response or result. Also adds a testing directory and unit tests to validate the Multiplexer. The new directory, src/tests,

The previous patch, for whatever reason, fails to apply on top of tip. This patch is reimplemented and, hopefully, fixed.

The Processors agent reports details regarding the processing power for the managed node. Defined the agent within schema.xml. Wrote the wrapper code to create and populate an instance of the agent. The properties for the Processors agent have also been trimmed back to what is readily available via HAL. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- src/Makefile.am | 26

Stripped out the HAL support code and replaced with calls to udev. The remainder of the code to extract CPU details parses through the /proc/cpuinfo file since udev/sysfs will not return such information. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- configure.ac | 3 +- src/Makefile.am | 4 +- src/processors.cpp | 94

This class has been replaced by the ProcessorsAgent. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- src/Makefile.am | 4 - src/cpu.cpp | 216 ------------------------------------------------------- src/cpu.h | 111 ---------------------------- src/host.cpp | 24 ------ src/host.h | 3 - src/schema.xml | 16 ---- 6 files changed, 0 insertions(+),

This patch includes one small change: the Processors::get_load_average() method is now const since it does not change the object's state.

After some feedback from Slow, mainly about the load_average API being a method rather than an ongoing statistic. So I've converted the code over to instead update the load average statistic on a regular basis.

dear all, i'm just about to do some straightforward contingency tables using ftables (and ctab() for percents). the problem: factor "a" are regions, factor "b" are subregions. every region "a" consists of some subregions "b", but obviously not every subregion "b" is part of every region "a". if i use the ftable() function, the

Dear r-devel members, I encountered a C stack limit issue, when I tried to embed R 2.5 into my application. In the R-exts document, it says:"Note that R's own front ends use a stack size of 10Mb". I desire to know: is it possible to decrease this stack size by modifying R's source code? If it's possible, which part of the source code is responsible for the issue? Thank

Dear All: I am stuck with this issue: I have a button on a TK window, once click it, it pops up a individual plot device: individual_plot <- function() { tkconfigure(overlay.button, state="normal") options(locatorBell = FALSE) plotfuntype() trellis.focus("panel", 1, 1,highlight=FALSE) panel.identify(labels=colnames(dataplot)) } Now I have

What's the first rule of investing? Buy low sell high! Yesterday, market forces caused our top pick (EGLY) to close down on the day. This gives our members the perfect opportunity to pick some up on the cheap before the big information! Ever-Glory International (EGLY) Current: 0.63 Projected: 1.30 Rating: 5/5 Here's the latest news: LOS ANGELES, CALIFORNIA-(MARKET WIRE)-Nov 6,

The Asterisk Development Team has announced security releases for Certified Asterisk 11.6 and 13.1 and Asterisk 11 and 13. The available security releases are released as versions 11.6-cert12, 11.21.1, 13.1-cert3, and 13.7.1. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/releases The release of these versions resolves the following

What's the first rule of investing? Buy low sell high! Yesterday, market forces caused our top pick (EGLY) to close down on the day. This gives our members the perfect opportunity to pick some up on the cheap before the big information! Ever-Glory International (EGLY) Current: 0.63 Projected: 1.30 Rating: 5/5 Here's the latest news: LOS ANGELES, CALIFORNIA-(MARKET WIRE)-Nov 6,

Hi all, I have taken my family in hostage and setup an asterisk environment at home... I am using a x100p fxo card, a Iaxy and X-ten softphones. Works ok with local calls. There is a strange behavior, when we do long distance calls, it keeps ringing on our end, remote callee answers the call but hear nothing. It is great for one thing, they called us back and we save the long distance fees