search for: logevent

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

...;, :force => true do |t| t.column "user_id", :integer t.column "event_at", :datetime t.column "note", :text t.column "type", :string t.column "type1_attr", :integer t.column "type2_attr", :integer end class LogEvent < ActiveRecord::Base class SubType1Event < LogEvent class SubType2Event < LogEvent If not, then how? (keeping it simple!) Since event_at is a datetime, how do I best do a find by only the Date portion? For a Date Range? Should I use REST or SOAP for the API? Is one or the other b...

...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 (reme...

...above Warn to a database table. But the deployment of log4r doesn''t come with a database outputter. Is there any reason for this? Anyway, I''ve written an outputter for log4r that uses Ruby DBI and the ODBC driver for MySQL. I''ve also enhanced the basic formatter and logevent to accept an optional extra field after the message. This eventually gets written to the userid column in the database so that we can find out who''s been wrecking our system :-D. Because the field is optional, Rails is happy to use log4r to output its own messages. I tried contacting t...

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 ...