1 collectd - System information collection daemon
2 =================================================
8 collectd is a small daemon which collects system information periodically
9 and provides mechanisms to store and monitor the values in a variety of
16 * collectd is able to collect the following data:
19 Apache server utilization: Number of bytes transferred, number of
20 requests handled and detailed scoreboard statistics
23 APC UPS Daemon: UPS charge, load, input/output/battery voltage, etc.
26 Sensors in Macs running Mac OS X / Darwin: Temperature, fan speed and
30 Various sensors in the Aquaero 5 water cooling board made by Aquacomputer.
33 Statistics about Ascent, a free server for the game `World of Warcraft'.
36 Reads absolute barometric pressure, air pressure reduced to sea level and
37 temperature. Supported sensors are MPL115A2 and MPL3115 from Freescale
38 and BMP085 from Bosch.
41 Batterycharge, -current and voltage of ACPI and PMU based laptop
45 Name server and resolver statistics from the `statistics-channel'
46 interface of BIND 9.5, 9,6 and later.
49 Statistics from the Ceph distributed storage system.
52 CPU accounting information for process groups under Linux.
55 Number of nf_conntrack entries.
58 Number of context switches done by the operating system.
61 CPU utilization: Time spent in the system, user, nice, idle, and related
65 CPU frequency (For laptops with speed step or a similar technology)
68 Parse statistics from websites using regular expressions.
71 Retrieves JSON data via cURL and parses it according to user
75 Retrieves XML data via cURL and parses it according to user
79 Executes SQL statements on various databases and interprets the returned
83 Mountpoint usage (Basically the values `df(1)' delivers)
86 Disk utilization: Sectors read/written, number of read/write actions,
87 average time an IO-operation took to complete.
90 DNS traffic: Query types, response codes, opcodes and traffic/octets
94 Collect individual drbd resource statistics.
97 Email statistics: Count, traffic, spam scores and checks.
98 See collectd-email(5).
101 Amount of entropy available to the system.
104 Network interface card statistics.
107 Values gathered by a custom program or script.
108 See collectd-exec(5).
111 Count the number of files in directories.
114 Linux file-system based caching framework statistics.
117 Receive multicast traffic from Ganglia instances.
120 Hard disk temperatures using hddtempd.
123 Interface traffic: Number of octets, packets and errors for each
127 Iptables' counters: Number of bytes that were matched by a certain
131 IPMI (Intelligent Platform Management Interface) sensors information.
134 IPVS connection statistics (number of connections, octets and packets
135 for each service and destination).
136 See http://www.linuxvirtualserver.org/software/index.html.
139 IRQ counters: Frequency in which certain interrupts occur.
142 Integrates a `Java Virtual Machine' (JVM) to execute plugins in Java
143 bytecode. See “Configuring with libjvm” below.
146 System load average over the last 1, 5 and 15 minutes.
149 Detailed CPU statistics of the “Logical Partitions” virtualization
150 technique built into IBM's POWER processors.
153 Size of “Logical Volumes” (LV) and “Volume Groups” (VG) of Linux'
154 “Logical Volume Manager” (LVM).
157 Queries very detailed usage statistics from wireless LAN adapters and
158 interfaces that use the Atheros chipset and the MadWifi driver.
161 Motherboard sensors: temperature, fan speed and voltage information,
165 Linux software-RAID device information (number of active, failed, spare
169 Query and parse data from a memcache daemon (memcached).
172 Statistics of the memcached distributed caching system.
173 <http://www.danga.com/memcached/>
176 Memory utilization: Memory occupied by running processes, page cache,
177 buffer cache and free.
180 Collects CPU usage, memory usage, temperatures and power consumption from
181 Intel Many Integrated Core (MIC) CPUs.
184 Reads values from Modbus/TCP enabled devices. Supports reading values
185 from multiple "slaves" so gateway devices can be used.
188 Information provided by serial multimeters, such as the `Metex
192 MySQL server statistics: Commands issued, handlers triggered, thread
193 usage, query cache utilization and traffic/octets sent and received.
196 Plugin to query performance values from a NetApp storage system using the
197 “Manage ONTAP” SDK provided by NetApp.
200 Very detailed Linux network interface and routing statistics. You can get
201 (detailed) information on interfaces, qdiscs, classes, and, if you can
202 make use of it, filters.
205 Receive values that were collected by other hosts. Large setups will
206 want to collect the data on one dedicated machine, and this is the
207 plugin of choice for that.
210 NFS Procedures: Which NFS command were called how often. Only NFSv2 and
214 Collects statistics from `nginx' (speak: engine X), a HTTP and mail
218 NTP daemon statistics: Local clock drift, offset to peers, etc.
221 Network UPS tools: UPS current, voltage, power, charge, utilisation,
222 temperature, etc. See upsd(8).
225 Information about Non-Uniform Memory Access (NUMA).
228 Queries routing information from the “Optimized Link State Routing”
231 - onewire (EXPERIMENTAL!)
232 Read onewire sensors using the owcapu library of the owfs project.
233 Please read in collectd.conf(5) why this plugin is experimental.
236 Read monitoring information from OpenLDAP's cn=Monitor subtree.
239 RX and TX of each client in openvpn-status.log (status-version 2).
240 <http://openvpn.net/index.php/documentation/howto.html>
243 Query data from an Oracle database.
246 The perl plugin implements a Perl-interpreter into collectd. You can
247 write your own plugins in Perl and return arbitrary values using this
248 API. See collectd-perl(5).
251 Query statistics from BSD's packet filter "pf".
254 Receive and dispatch timing values from Pinba, a profiling extension for
258 Network latency: Time to reach the default gateway or another given
262 PostgreSQL database statistics: active server connections, transaction
263 numbers, block IO, table row manipulations.
266 PowerDNS name server statistics.
269 Process counts: Number of running, sleeping, zombie, ... processes.
272 Counts various aspects of network protocols such as IP, TCP, UDP, etc.
275 The python plugin implements a Python interpreter into collectd. This
276 makes it possible to write plugins in Python which are executed by
277 collectd without the need to start a heavy interpreter every interval.
278 See collectd-python(5) for details.
281 The redis plugin gathers information from a Redis server, including:
282 uptime, used memory, total connections etc.
285 Query interface and wireless registration statistics from RouterOS.
288 RRDtool caching daemon (RRDcacheD) statistics.
291 System sensors, accessed using lm_sensors: Voltages, temperatures and
295 RX and TX of serial interfaces. Linux only; needs root privileges.
298 Uses libsigrok as a backend, allowing any sigrok-supported device
299 to have its measurements fed to collectd. This includes multimeters,
300 sound level meters, thermometers, and much more.
303 Collect SMART statistics, notably load cycle count, temperature
307 Read values from SNMP (Simple Network Management Protocol) enabled
308 network devices such as switches, routers, thermometers, rack monitoring
309 servers, etc. See collectd-snmp(5).
312 Acts as a StatsD server, reading values sent over the network from StatsD
313 clients and calculating rates and other aggregates out of these values.
316 Pages swapped out onto hard disk or whatever is called `swap' by the OS..
319 Parse table-like structured files.
322 Follows (tails) log files, parses them by lines and submits matched
326 Follows (tails) files in CSV format, parses each line and submits
330 Bytes and operations read and written on tape devices. Solaris only.
333 Number of TCP connections to specific local and remote ports.
336 TeamSpeak2 server statistics.
339 Plugin to read values from `The Energy Detective' (TED).
342 Linux ACPI thermal zone information.
345 Reads the number of records and file size from a running Tokyo Tyrant
349 System uptime statistics.
352 Users currently logged in.
355 Various statistics from Varnish, an HTTP accelerator.
358 CPU, memory, disk and network I/O statistics from virtual machines.
361 Virtual memory statistics, e. g. the number of page-ins/-outs or the
362 number of pagefaults.
365 System resources used by Linux VServers.
366 See <http://linux-vserver.org/>.
369 Link quality of wireless cards. Linux only.
372 Bitrate and frequency of music played with XMMS.
375 Statistics for ZFS' “Adaptive Replacement Cache” (ARC).
378 Read data from Zookeeper's MNTR command.
380 * Output can be written or sent to various destinations by the following
384 Sends JSON-encoded data to an Advanced Message Queuing Protocol (AMQP)
385 server, such as RabbitMQ.
388 Write to comma separated values (CSV) files. This needs lots of
389 diskspace but is extremely portable and can be analysed with almost
390 every program that can analyse anything. Even Microsoft's Excel..
393 Send the data to a remote host to save the data somehow. This is useful
394 for large setups where the data should be saved by a dedicated machine.
397 Of course the values are propagated to plugins written in Perl, too, so
398 you can easily do weird stuff with the plugins we didn't dare think of
399 ;) See collectd-perl(5).
402 It's possible to implement write plugins in Python using the python
403 plugin. See collectd-python(5) for details.
406 Output to round-robin-database (RRD) files using the RRDtool caching
407 daemon (RRDcacheD) - see rrdcached(1). That daemon provides a general
408 implementation of the caching done by the `rrdtool' plugin.
411 Output to round-robin-database (RRD) files using librrd. See rrdtool(1).
412 This is likely the most popular destination for such values. Since
413 updates to RRD-files are somewhat expensive this plugin can cache
414 updates to the files and write a bunch of updates at once, which lessens
418 One can query the values from the unixsock plugin whenever they're
419 needed. Please read collectd-unixsock(5) for a description on how that's
423 Sends data to Carbon, the storage layer of Graphite using TCP or UDP. It
424 can be configured to avoid logging send errors (especially useful when
428 Sends data OpenTSDB, a scalable no master, no shared state time series
432 Sends the values collected by collectd to a web-server using HTTP POST
433 requests. The transmitted data is either in a form understood by the
434 Exec plugin or formatted in JSON.
437 Sends data to Apache Kafka, a distributed queue.
440 Writes data to the log
443 Sends data to MongoDB, a NoSQL database.
446 Sends the values to a Redis key-value database server.
449 Sends data to Riemann, a stream processing and monitoring system.
452 Sends data to Sensu, a stream processing and monitoring system, via the
453 Sensu client local TCP socket.
455 * Logging is, as everything in collectd, provided by plugins. The following
456 plugins keep up informed about what's going on:
459 Writes log messages to a file or STDOUT/STDERR.
462 Log messages are propagated to plugins written in Perl as well.
463 See collectd-perl(5).
466 It's possible to implement log plugins in Python using the python plugin.
467 See collectd-python(5) for details.
470 Logs to the standard UNIX logging mechanism, syslog.
473 Writes log messages formatted as logstash JSON events.
475 * Notifications can be handled by the following plugins:
478 Send a desktop notification to a notification daemon, as defined in
479 the Desktop Notification Specification. To actually display the
480 notifications, notification-daemon is required.
481 See http://www.galago-project.org/specs/notification/.
484 Send an E-mail with the notification message to the configured
488 Execute a program or script to handle the notification.
489 See collectd-exec(5).
492 Writes the notification message to a file or STDOUT/STDERR.
495 Send the notification to a remote host to handle it somehow.
498 Notifications are propagated to plugins written in Perl as well.
499 See collectd-perl(5).
502 It's possible to implement notification plugins in Python using the
503 python plugin. See collectd-python(5) for details.
505 * Value processing can be controlled using the "filter chain" infrastructure
506 and "matches" and "targets". The following plugins are available:
508 - match_empty_counter
509 Match counter values which are currently zero.
512 Match values using a hash function of the hostname.
515 Match values by their identifier based on regular expressions.
518 Match values with an invalid timestamp.
521 Select values by their data sources' values.
523 - target_notification
524 Create and dispatch a notification.
527 Replace parts of an identifier using regular expressions.
530 Scale (multiply) values by an arbitrary value.
533 Set (overwrite) entire parts of an identifier.
535 * Miscellaneous plugins:
538 Selects multiple value lists based on patterns or regular expressions
539 and creates new aggregated values lists from those.
542 Checks values against configured thresholds and creates notifications if
543 values are out of bounds. See collectd-threshold(5) for details.
546 Sets the hostname to a unique identifier. This is meant for setups
547 where each client may migrate to another physical host, possibly going
548 through one or more name changes in the process.
550 * Performance: Since collectd is running as a daemon it doesn't spend much
551 time starting up again and again. With the exception of the exec plugin no
552 processes are forked. Caching in output plugins, such as the rrdtool and
553 network plugins, makes sure your resources are used efficiently. Also,
554 since collectd is programmed multithreaded it benefits from hyper-threading
555 and multicore processors and makes sure that the daemon isn't idle if only
556 one plugin waits for an IO-operation to complete.
558 * Once set up, hardly any maintenance is necessary. Setup is kept as easy
559 as possible and the default values should be okay for most users.
565 * collectd's configuration file can be found at `sysconfdir'/collectd.conf.
566 Run `collectd -h' for a list of built-in defaults. See `collectd.conf(5)'
567 for a list of options and a syntax description.
569 * When the `csv' or `rrdtool' plugins are loaded they'll write the values to
570 files. The usual place for these files is beneath `/var/lib/collectd'.
572 * When using some of the plugins, collectd needs to run as user root, since
573 only root can do certain things, such as craft ICMP packages needed to ping
574 other hosts. collectd should NOT be installed setuid root since it can be
575 used to overwrite valuable files!
577 * Sample scripts to generate graphs reside in `contrib/' in the source
578 package or somewhere near `/usr/share/doc/collectd' in most distributions.
579 Please be aware that those script are meant as a starting point for your
580 own experiments.. Some of them require the `RRDs' Perl module.
581 (`librrds-perl' on Debian) If you have written a more sophisticated
582 solution please share it with us.
584 * The RRAs of the automatically created RRD files depend on the `step'
585 and `heartbeat' settings given. If change these settings you may need to
586 re-create the files, losing all data. Please be aware of that when changing
587 the values and read the rrdtool(1) manpage thoroughly.
590 collectd and chkrootkit
591 -----------------------
593 If you are using the `dns' plugin chkrootkit(1) will report collectd as a
594 packet sniffer ("<iface>: PACKET SNIFFER(/usr/sbin/collectd[<pid>])"). The
595 plugin captures all UDP packets on port 53 to analyze the DNS traffic. In
596 this case, collectd is a legitimate sniffer and the report should be
597 considered to be a false positive. However, you might want to check that
598 this really is collectd and not some other, illegitimate sniffer.
604 To compile collectd from source you will need:
606 * Usual suspects: C compiler, linker, preprocessor, make, ...
608 * A POSIX-threads (pthread) implementation.
609 Since gathering some statistics is slow (network connections, slow devices,
610 etc) collectd is parallelized. The POSIX threads interface is being
611 used and should be found in various implementations for hopefully all
614 * aerotools-ng (optional)
615 Used by the `aquaero' plugin. Currently, the `libaquaero5' library, which
616 is used by the `aerotools-ng' toolkit, is not compiled as a shared object
617 nor does it feature an installation routine. Therefore, you need to point
618 collectd's configure script at the source directory of the `aerotools-ng'
620 <https://github.com/lynix/aerotools-ng>
622 * CoreFoundation.framework and IOKit.framework (optional)
623 For compiling on Darwin in general and the `apple_sensors' plugin in
625 <http://developer.apple.com/corefoundation/>
627 * libatasmart (optional)
628 Used by the `smart' plugin.
629 <http://git.0pointer.de/?p=libatasmart.git>
631 * libclntsh (optional)
632 Used by the `oracle' plugin.
634 * libhiredis (optional)
635 Used by the redis plugin. Please note that you require a 0.10.0 version
636 or higher. <https://github.com/redis/hiredis>
639 If you want to use the `apache', `ascent', `bind', `curl', `curl_json',
640 `curl_xml', `nginx', or `write_http' plugin.
641 <http://curl.haxx.se/>
644 Used by the `dbi' plugin to connect to various databases.
645 <http://libdbi.sourceforge.net/>
647 * libesmtp (optional)
648 For the `notify_email' plugin.
649 <http://www.stafford.uklinux.net/libesmtp/>
651 * libganglia (optional)
652 Used by the `gmond' plugin to process data received from Ganglia.
653 <http://ganglia.info/>
655 * libgcrypt (optional)
656 Used by the `network' plugin for encryption and authentication.
657 <http://www.gnupg.org/>
660 If present, the `uuid' plugin will check for UUID from HAL.
661 <http://hal.freedesktop.org/>
663 * libi2c-dev (optional)
664 Used for the plugin `barometer', provides just the i2c-dev.h header file
665 for user space i2c development.
668 For querying iptables counters.
669 <http://netfilter.org/>
672 Library that encapsulates the `Java Virtual Machine' (JVM). This library is
673 used by the `java' plugin to execute Java bytecode. See “Configuring with
675 <http://openjdk.java.net/> (and others)
678 Used by the `openldap' plugin.
679 <http://www.openldap.org/>
682 Used by the `lvm' plugin.
683 <ftp://sources.redhat.com/pub/lvm2/>
685 * libmemcached (optional)
686 Used by the `memcachec' plugin to connect to a memcache daemon.
687 <http://tangent.org/552/libmemcached.html>
690 Used by the `netlink' plugin.
691 <http://www.netfilter.org/projects/libmnl/>
693 * libmodbus (optional)
694 Used by the `modbus' plugin to communicate with Modbus/TCP devices. The
695 `modbus' plugin works with version 2.0.3 of the library – due to frequent
696 API changes other versions may or may not compile cleanly.
697 <http://www.libmodbus.org/>
699 * libmysqlclient (optional)
700 Unsurprisingly used by the `mysql' plugin.
701 <http://dev.mysql.com/>
703 * libnetapp (optional)
704 Required for the `netapp' plugin.
705 This library is part of the “Manage ONTAP SDK” published by NetApp.
707 * libnetsnmp (optional)
708 For the `snmp' plugin.
709 <http://www.net-snmp.org/>
711 * libnotify (optional)
712 For the `notify_desktop' plugin.
713 <http://www.galago-project.org/>
715 * libopenipmi (optional)
716 Used by the `ipmi' plugin to prove IPMI devices.
717 <http://openipmi.sourceforge.net/>
719 * liboping (optional)
720 Used by the `ping' plugin to send and receive ICMP packets.
721 <http://octo.it/liboping/>
723 * libowcapi (optional)
724 Used by the `onewire' plugin to read values from onewire sensors (or the
726 <http://www.owfs.org/>
729 Used to capture packets by the `dns' plugin.
730 <http://www.tcpdump.org/>
732 * libperfstat (optional)
733 Used by various plugins to gather statistics under AIX.
736 Obviously used by the `perl' plugin. The library has to be compiled with
737 ithread support (introduced in Perl 5.6.0).
738 <http://www.perl.org/>
741 The PostgreSQL C client library used by the `postgresql' plugin.
742 <http://www.postgresql.org/>
744 * libprotobuf-c, protoc-c (optional)
745 Used by the `pinba' plugin to generate a parser for the network packets
746 sent by the Pinba PHP extension, and by the `write_riemann' plugin to
747 generate events to be sent to a Riemann server.
748 <http://code.google.com/p/protobuf-c/>
750 * libpython (optional)
751 Used by the `python' plugin. Currently, Python 2.3 and later and Python 3
753 <http://www.python.org/>
755 * librabbitmq (optional; also called “rabbitmq-c”)
756 Used by the `amqp' plugin for AMQP connections, for example to RabbitMQ.
757 <http://hg.rabbitmq.com/rabbitmq-c/>
759 * librdkafka (optional; also called “rdkafka”)
760 Used by the `write_kafka' plugin for producing messages and sending them
762 <https://github.com/edenhill/librdkafka>
764 * librouteros (optional)
765 Used by the `routeros' plugin to connect to a device running `RouterOS'.
766 <http://octo.it/librouteros/>
769 Used by the `rrdtool' and `rrdcached' plugins. The latter requires RRDtool
770 client support which was added after version 1.3 of RRDtool. Versions 1.0,
771 1.2 and 1.3 are known to work with the `rrdtool' plugin.
772 <http://oss.oetiker.ch/rrdtool/>
774 * librt, libsocket, libkstat, libdevinfo (optional)
775 Various standard Solaris libraries which provide system functions.
776 <http://developers.sun.com/solaris/>
778 * libsensors (optional)
779 To read from `lm_sensors', see the `sensors' plugin.
780 <http://www.lm-sensors.org/>
782 * libsigrok (optional)
783 Used by the `sigrok' plugin. In addition, libsigrok depends on glib,
784 libzip, and optionally (depending on which drivers are enabled) on
785 libusb, libftdi and libudev.
787 * libstatgrab (optional)
788 Used by various plugins to collect statistics on systems other than Linux
790 <http://www.i-scream.org/libstatgrab/>
792 * libtokyotyrant (optional)
793 Used by the `tokyotyrant' plugin.
794 <http://1978th.net/tokyotyrant/>
796 * libupsclient/nut (optional)
797 For the `nut' plugin which queries nut's `upsd'.
798 <http://networkupstools.org/>
801 Collect statistics from virtual machines.
802 <http://libvirt.org/>
805 Parse XML data. This is needed for the `ascent', `bind', `curl_xml' and
807 <http://xmlsoft.org/>
810 <http://www.xmms.org/>
813 Parse JSON data. This is needed for the `ceph', `curl_json' and
814 `log_logstash' plugins.
815 <http://github.com/lloyd/yajl>
817 * libvarnish (optional)
818 Fetches statistics from a Varnish instance. This is needed for the
820 <http://varnish-cache.org>
822 Configuring / Compiling / Installing
823 ------------------------------------
825 To configure, build and install collectd with the default settings, run
826 `./configure && make && make install'. For detailed, generic instructions
827 see INSTALL. For a complete list of configure options and their description,
828 run `./configure --help'.
830 By default, the configure script will check for all build dependencies and
831 disable all plugins whose requirements cannot be fulfilled (any other plugin
832 will be enabled). To enable a plugin, install missing dependencies (see
833 section `Prerequisites' above) and rerun `configure'. If you specify the
834 `--enable-<plugin>' configure option, the script will fail if the depen-
835 dencies for the specified plugin are not met. In that case you can force the
836 plugin to be built using the `--enable-<plugin>=force' configure option.
837 This will most likely fail though unless you're working in a very unusual
838 setup and you really know what you're doing. If you specify the
839 `--disable-<plugin>' configure option, the plugin will not be built. If you
840 specify the `--enable-all-plugins' or `--disable-all-plugins' configure
841 options, all plugins will be enabled or disabled respectively by default.
842 Explicitly enabling or disabling a plugin overwrites the default for the
843 specified plugin. These options are meant for package maintainers and should
844 not be used in everyday situations.
846 By default, collectd will be installed into `/opt/collectd'. You can adjust
847 this setting by specifying the `--prefix' configure option - see INSTALL for
848 details. If you pass DESTDIR=<path> to `make install', <path> will be
849 prefixed to all installation directories. This might be useful when creating
850 packages for collectd.
852 Configuring with libjvm
853 -----------------------
855 To determine the location of the required files of a Java installation is not
856 an easy task, because the locations vary with your kernel (Linux, SunOS, …)
857 and with your architecture (x86, SPARC, …) and there is no ‘java-config’
858 script we could use. Configuration of the JVM library is therefore a bit
861 The easiest way to use the `--with-java=$JAVA_HOME' option, where
862 `$JAVA_HOME' is usually something like:
863 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14
865 The configure script will then use find(1) to look for the following files:
871 If found, appropriate CPP-flags and LD-flags are set and the following
872 library checks succeed.
874 If this doesn't work for you, you have the possibility to specify CPP-flags,
875 C-flags and LD-flags for the ‘Java’ plugin by hand, using the following three
876 (environment) variables:
882 For example (shortened for demonstration purposes):
884 ./configure JAVA_CPPFLAGS="-I$JAVA_HOME/include -I$JAVA_HOME/include/linux"
886 Adding "-ljvm" to the JAVA_LDFLAGS is done automatically, you don't have to
889 Generating the configure script
890 -------------------------------
892 Collectd ships with a `build.sh' script to generate the `configure'
893 script shipped with releases.
895 To generate the `configure` script, you'll need the following dependencies:
904 The `build.sh' script takes no arguments.
909 To compile correctly collectd needs to be able to initialize static
910 variables to NAN (Not A Number). Some C libraries, especially the GNU
911 libc, have a problem with that.
913 Luckily, with GCC it's possible to work around that problem: One can define
914 NAN as being (0.0 / 0.0) and `isnan' as `f != f'. However, to test this
915 ``implementation'' the configure script needs to compile and run a short
916 test program. Obviously running a test program when doing a cross-
917 compilation is, well, challenging.
919 If you run into this problem, you can use the `--with-nan-emulation'
920 configure option to force the use of this implementation. We can't promise
921 that the compiled binary actually behaves as it should, but since NANs
922 are likely never passed to the libm you have a good chance to be lucky.
924 Likewise, collectd needs to know the layout of doubles in memory, in order
925 to craft uniform network packets over different architectures. For this, it
926 needs to know how to convert doubles into the memory layout used by x86. The
927 configure script tries to figure this out by compiling and running a few
928 small test programs. This is of course not possible when cross-compiling.
929 You can use the `--with-fp-layout' option to tell the configure script which
930 conversion method to assume. Valid arguments are:
932 * `nothing' (12345678 -> 12345678)
933 * `endianflip' (12345678 -> 87654321)
934 * `intswap' (12345678 -> 56781234)
940 For questions, bug reports, development information and basically all other
941 concerns please send an email to collectd's mailing list at
942 <list at collectd.org>.
944 For live discussion and more personal contact visit us in IRC, we're in
945 channel #collectd on freenode.
951 Florian octo Forster <octo at collectd.org>,
952 Sebastian tokkee Harl <sh at tokkee.org>,
953 and many contributors (see `AUTHORS').
955 Please send bug reports and patches to the mailing list, see `Contact'