search for: logevents

This patch introduces support for two new parameters in libxl: smbios_firmware=<path_to_smbios_structures_file> acpi_firmware=<path_to_acpi_tables_file> The changes are primarily in the domain building code where the firmware files are read and passed to libxc for loading into the new guest. After the domain building call to libxc, the addresses for the loaded blobs are returned and

Hello! So, I''m fairly new to Rails and I have a question that pertains to how to best model something that is typically addressed via inheritance. Here''s the situation: I need to maintain an EventLog There are several different "types" (eight at this point) of Events All Events have a couple of attributes in common (user_id, event_at, note, summary, type, etc.)

...h I would like to retrieve some aggregated data, with an ordering. Something like: Entry.calculate(''avg'', ''thevalue'', { :order=> ''avg_thevalue DESC'' }) which generates the following (Postgres) query: SELECT avg(subject) AS avg_subject FROM logevents ORDER BY avg_subject This works, but the :order option depends on what I think are implementation details of the function calculate: namely the generation of the "AS avg_subject" alias in the query. This becomes painful if I need more complex SQL expressions to get to the data (remem...

I recently had a look at Log4Net before we decided to go with Ruby On Rails. As part of evaluating Ruby and Rails, I had a look at Log4r as well. We want to use Log4r, and we would have a logger that output all levels to console and stdout, and everything above Warn to a database table. But the deployment of log4r doesn''t come with a database outputter. Is there any reason for this?

This patch series adds support for network buffering in the Remus codebase in libxl. Changes in V3: [1/5] Fix redundant checks in configure scripts (based on Ian Campbell''s suggestions) [2/5] Introduce locking in the script, during IFB setup. Add xenstore paths used by netbuf scripts to xenstore-paths.markdown [3/5] Hotplug scripts setup/teardown invocations are now

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...