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 IPC counters: semaphores used, number of allocated segments in shared
131 IPMI (Intelligent Platform Management Interface) sensors information.
134 Iptables' counters: Number of bytes that were matched by a certain
138 IPVS connection statistics (number of connections, octets and packets
139 for each service and destination).
140 See http://www.linuxvirtualserver.org/software/index.html.
143 IRQ counters: Frequency in which certain interrupts occur.
146 Integrates a `Java Virtual Machine' (JVM) to execute plugins in Java
147 bytecode. See “Configuring with libjvm” below.
150 System load average over the last 1, 5 and 15 minutes.
153 Detailed CPU statistics of the “Logical Partitions” virtualization
154 technique built into IBM's POWER processors.
157 Size of “Logical Volumes” (LV) and “Volume Groups” (VG) of Linux'
158 “Logical Volume Manager” (LVM).
161 Queries very detailed usage statistics from wireless LAN adapters and
162 interfaces that use the Atheros chipset and the MadWifi driver.
165 Motherboard sensors: temperature, fan speed and voltage information,
169 Linux software-RAID device information (number of active, failed, spare
173 Query and parse data from a memcache daemon (memcached).
176 Statistics of the memcached distributed caching system.
177 <http://www.danga.com/memcached/>
180 Memory utilization: Memory occupied by running processes, page cache,
181 buffer cache and free.
184 Collects CPU usage, memory usage, temperatures and power consumption from
185 Intel Many Integrated Core (MIC) CPUs.
188 Reads values from Modbus/TCP enabled devices. Supports reading values
189 from multiple "slaves" so gateway devices can be used.
192 Information provided by serial multimeters, such as the `Metex
196 MySQL server statistics: Commands issued, handlers triggered, thread
197 usage, query cache utilization and traffic/octets sent and received.
200 Plugin to query performance values from a NetApp storage system using the
201 “Manage ONTAP” SDK provided by NetApp.
204 Very detailed Linux network interface and routing statistics. You can get
205 (detailed) information on interfaces, qdiscs, classes, and, if you can
206 make use of it, filters.
209 Receive values that were collected by other hosts. Large setups will
210 want to collect the data on one dedicated machine, and this is the
211 plugin of choice for that.
214 NFS Procedures: Which NFS command were called how often. Only NFSv2 and
218 Collects statistics from `nginx' (speak: engine X), a HTTP and mail
222 NTP daemon statistics: Local clock drift, offset to peers, etc.
225 Information about Non-Uniform Memory Access (NUMA).
228 Network UPS tools: UPS current, voltage, power, charge, utilisation,
229 temperature, etc. See upsd(8).
232 Queries routing information from the “Optimized Link State Routing”
235 - onewire (EXPERIMENTAL!)
236 Read onewire sensors using the owcapu library of the owfs project.
237 Please read in collectd.conf(5) why this plugin is experimental.
240 Read monitoring information from OpenLDAP's cn=Monitor subtree.
243 RX and TX of each client in openvpn-status.log (status-version 2).
244 <http://openvpn.net/index.php/documentation/howto.html>
247 Query data from an Oracle database.
250 The perl plugin implements a Perl-interpreter into collectd. You can
251 write your own plugins in Perl and return arbitrary values using this
252 API. See collectd-perl(5).
255 Query statistics from BSD's packet filter "pf".
258 Receive and dispatch timing values from Pinba, a profiling extension for
262 Network latency: Time to reach the default gateway or another given
266 PostgreSQL database statistics: active server connections, transaction
267 numbers, block IO, table row manipulations.
270 PowerDNS name server statistics.
273 Process counts: Number of running, sleeping, zombie, ... processes.
276 Counts various aspects of network protocols such as IP, TCP, UDP, etc.
279 The python plugin implements a Python interpreter into collectd. This
280 makes it possible to write plugins in Python which are executed by
281 collectd without the need to start a heavy interpreter every interval.
282 See collectd-python(5) for details.
285 The redis plugin gathers information from a Redis server, including:
286 uptime, used memory, total connections etc.
289 Query interface and wireless registration statistics from RouterOS.
292 RRDtool caching daemon (RRDcacheD) statistics.
295 System sensors, accessed using lm_sensors: Voltages, temperatures and
299 RX and TX of serial interfaces. Linux only; needs root privileges.
302 Uses libsigrok as a backend, allowing any sigrok-supported device
303 to have its measurements fed to collectd. This includes multimeters,
304 sound level meters, thermometers, and much more.
307 Collect SMART statistics, notably load cycle count, temperature
311 Read values from SNMP (Simple Network Management Protocol) enabled
312 network devices such as switches, routers, thermometers, rack monitoring
313 servers, etc. See collectd-snmp(5).
316 Acts as a StatsD server, reading values sent over the network from StatsD
317 clients and calculating rates and other aggregates out of these values.
320 Pages swapped out onto hard disk or whatever is called `swap' by the OS..
323 Parse table-like structured files.
326 Follows (tails) log files, parses them by lines and submits matched
330 Follows (tails) files in CSV format, parses each line and submits
334 Bytes and operations read and written on tape devices. Solaris only.
337 Number of TCP connections to specific local and remote ports.
340 TeamSpeak2 server statistics.
343 Plugin to read values from `The Energy Detective' (TED).
346 Linux ACPI thermal zone information.
349 Reads the number of records and file size from a running Tokyo Tyrant
353 Reads CPU frequency and C-state residency on modern Intel
354 turbo-capable processors.
357 System uptime statistics.
360 Users currently logged in.
363 Various statistics from Varnish, an HTTP accelerator.
366 CPU, memory, disk and network I/O statistics from virtual machines.
369 Virtual memory statistics, e. g. the number of page-ins/-outs or the
370 number of pagefaults.
373 System resources used by Linux VServers.
374 See <http://linux-vserver.org/>.
377 Link quality of wireless cards. Linux only.
380 Bitrate and frequency of music played with XMMS.
383 Statistics for ZFS' “Adaptive Replacement Cache” (ARC).
386 Read data from Zookeeper's MNTR command.
388 * Output can be written or sent to various destinations by the following
392 Sends JSON-encoded data to an Advanced Message Queuing Protocol (AMQP)
393 server, such as RabbitMQ.
396 Write to comma separated values (CSV) files. This needs lots of
397 diskspace but is extremely portable and can be analysed with almost
398 every program that can analyse anything. Even Microsoft's Excel..
401 Send the data to a remote host to save the data somehow. This is useful
402 for large setups where the data should be saved by a dedicated machine.
405 Of course the values are propagated to plugins written in Perl, too, so
406 you can easily do weird stuff with the plugins we didn't dare think of
407 ;) See collectd-perl(5).
410 It's possible to implement write plugins in Python using the python
411 plugin. See collectd-python(5) for details.
414 Output to round-robin-database (RRD) files using the RRDtool caching
415 daemon (RRDcacheD) - see rrdcached(1). That daemon provides a general
416 implementation of the caching done by the `rrdtool' plugin.
419 Output to round-robin-database (RRD) files using librrd. See rrdtool(1).
420 This is likely the most popular destination for such values. Since
421 updates to RRD-files are somewhat expensive this plugin can cache
422 updates to the files and write a bunch of updates at once, which lessens
426 One can query the values from the unixsock plugin whenever they're
427 needed. Please read collectd-unixsock(5) for a description on how that's
431 Sends data to Carbon, the storage layer of Graphite using TCP or UDP. It
432 can be configured to avoid logging send errors (especially useful when
436 Sends the values collected by collectd to a web-server using HTTP POST
437 requests. The transmitted data is either in a form understood by the
438 Exec plugin or formatted in JSON.
441 Sends data to Apache Kafka, a distributed queue.
444 Writes data to the log
447 Sends data to MongoDB, a NoSQL database.
450 Sends the values to a Redis key-value database server.
453 Sends data to Riemann, a stream processing and monitoring system.
456 Sends data to Sensu, a stream processing and monitoring system, via the
457 Sensu client local TCP socket.
460 Sends data OpenTSDB, a scalable no master, no shared state time series
463 * Logging is, as everything in collectd, provided by plugins. The following
464 plugins keep up informed about what's going on:
467 Writes log messages to a file or STDOUT/STDERR.
470 Log messages are propagated to plugins written in Perl as well.
471 See collectd-perl(5).
474 It's possible to implement log plugins in Python using the python plugin.
475 See collectd-python(5) for details.
478 Logs to the standard UNIX logging mechanism, syslog.
481 Writes log messages formatted as logstash JSON events.
483 * Notifications can be handled by the following plugins:
486 Send a desktop notification to a notification daemon, as defined in
487 the Desktop Notification Specification. To actually display the
488 notifications, notification-daemon is required.
489 See http://www.galago-project.org/specs/notification/.
492 Send an E-mail with the notification message to the configured
496 Execute a program or script to handle the notification.
497 See collectd-exec(5).
500 Writes the notification message to a file or STDOUT/STDERR.
503 Send the notification to a remote host to handle it somehow.
506 Notifications are propagated to plugins written in Perl as well.
507 See collectd-perl(5).
510 It's possible to implement notification plugins in Python using the
511 python plugin. See collectd-python(5) for details.
513 * Value processing can be controlled using the "filter chain" infrastructure
514 and "matches" and "targets". The following plugins are available:
516 - match_empty_counter
517 Match counter values which are currently zero.
520 Match values using a hash function of the hostname.
523 Match values by their identifier based on regular expressions.
526 Match values with an invalid timestamp.
529 Select values by their data sources' values.
531 - target_notification
532 Create and dispatch a notification.
535 Replace parts of an identifier using regular expressions.
538 Scale (multiply) values by an arbitrary value.
541 Set (overwrite) entire parts of an identifier.
543 * Miscellaneous plugins:
546 Selects multiple value lists based on patterns or regular expressions
547 and creates new aggregated values lists from those.
550 Checks values against configured thresholds and creates notifications if
551 values are out of bounds. See collectd-threshold(5) for details.
554 Sets the hostname to a unique identifier. This is meant for setups
555 where each client may migrate to another physical host, possibly going
556 through one or more name changes in the process.
558 * Performance: Since collectd is running as a daemon it doesn't spend much
559 time starting up again and again. With the exception of the exec plugin no
560 processes are forked. Caching in output plugins, such as the rrdtool and
561 network plugins, makes sure your resources are used efficiently. Also,
562 since collectd is programmed multithreaded it benefits from hyper-threading
563 and multicore processors and makes sure that the daemon isn't idle if only
564 one plugin waits for an IO-operation to complete.
566 * Once set up, hardly any maintenance is necessary. Setup is kept as easy
567 as possible and the default values should be okay for most users.
573 * collectd's configuration file can be found at `sysconfdir'/collectd.conf.
574 Run `collectd -h' for a list of built-in defaults. See `collectd.conf(5)'
575 for a list of options and a syntax description.
577 * When the `csv' or `rrdtool' plugins are loaded they'll write the values to
578 files. The usual place for these files is beneath `/var/lib/collectd'.
580 * When using some of the plugins, collectd needs to run as user root, since
581 only root can do certain things, such as craft ICMP packages needed to ping
582 other hosts. collectd should NOT be installed setuid root since it can be
583 used to overwrite valuable files!
585 * Sample scripts to generate graphs reside in `contrib/' in the source
586 package or somewhere near `/usr/share/doc/collectd' in most distributions.
587 Please be aware that those script are meant as a starting point for your
588 own experiments.. Some of them require the `RRDs' Perl module.
589 (`librrds-perl' on Debian) If you have written a more sophisticated
590 solution please share it with us.
592 * The RRAs of the automatically created RRD files depend on the `step'
593 and `heartbeat' settings given. If change these settings you may need to
594 re-create the files, losing all data. Please be aware of that when changing
595 the values and read the rrdtool(1) manpage thoroughly.
598 collectd and chkrootkit
599 -----------------------
601 If you are using the `dns' plugin chkrootkit(1) will report collectd as a
602 packet sniffer ("<iface>: PACKET SNIFFER(/usr/sbin/collectd[<pid>])"). The
603 plugin captures all UDP packets on port 53 to analyze the DNS traffic. In
604 this case, collectd is a legitimate sniffer and the report should be
605 considered to be a false positive. However, you might want to check that
606 this really is collectd and not some other, illegitimate sniffer.
612 To compile collectd from source you will need:
614 * Usual suspects: C compiler, linker, preprocessor, make, ...
616 * A POSIX-threads (pthread) implementation.
617 Since gathering some statistics is slow (network connections, slow devices,
618 etc) collectd is parallelized. The POSIX threads interface is being
619 used and should be found in various implementations for hopefully all
622 * aerotools-ng (optional)
623 Used by the `aquaero' plugin. Currently, the `libaquaero5' library, which
624 is used by the `aerotools-ng' toolkit, is not compiled as a shared object
625 nor does it feature an installation routine. Therefore, you need to point
626 collectd's configure script at the source directory of the `aerotools-ng'
628 <https://github.com/lynix/aerotools-ng>
630 * CoreFoundation.framework and IOKit.framework (optional)
631 For compiling on Darwin in general and the `apple_sensors' plugin in
633 <http://developer.apple.com/corefoundation/>
635 * libatasmart (optional)
636 Used by the `smart' plugin.
637 <http://git.0pointer.de/?p=libatasmart.git>
639 * libclntsh (optional)
640 Used by the `oracle' plugin.
642 * libhiredis (optional)
643 Used by the redis plugin. Please note that you require a 0.10.0 version
644 or higher. <https://github.com/redis/hiredis>
647 If you want to use the `apache', `ascent', `bind', `curl', `curl_json',
648 `curl_xml', `nginx', or `write_http' plugin.
649 <http://curl.haxx.se/>
652 Used by the `dbi' plugin to connect to various databases.
653 <http://libdbi.sourceforge.net/>
655 * libesmtp (optional)
656 For the `notify_email' plugin.
657 <http://www.stafford.uklinux.net/libesmtp/>
659 * libganglia (optional)
660 Used by the `gmond' plugin to process data received from Ganglia.
661 <http://ganglia.info/>
663 * libgcrypt (optional)
664 Used by the `network' plugin for encryption and authentication.
665 <http://www.gnupg.org/>
668 If present, the `uuid' plugin will check for UUID from HAL.
669 <http://hal.freedesktop.org/>
671 * libi2c-dev (optional)
672 Used for the plugin `barometer', provides just the i2c-dev.h header file
673 for user space i2c development.
676 For querying iptables counters.
677 <http://netfilter.org/>
680 Library that encapsulates the `Java Virtual Machine' (JVM). This library is
681 used by the `java' plugin to execute Java bytecode. See “Configuring with
683 <http://openjdk.java.net/> (and others)
686 Used by the `openldap' plugin.
687 <http://www.openldap.org/>
690 Used by the `lvm' plugin.
691 <ftp://sources.redhat.com/pub/lvm2/>
693 * libmemcached (optional)
694 Used by the `memcachec' plugin to connect to a memcache daemon.
695 <http://tangent.org/552/libmemcached.html>
698 Used by the `netlink' plugin.
699 <http://www.netfilter.org/projects/libmnl/>
701 * libmodbus (optional)
702 Used by the `modbus' plugin to communicate with Modbus/TCP devices. The
703 `modbus' plugin works with version 2.0.3 of the library – due to frequent
704 API changes other versions may or may not compile cleanly.
705 <http://www.libmodbus.org/>
707 * libmysqlclient (optional)
708 Unsurprisingly used by the `mysql' plugin.
709 <http://dev.mysql.com/>
711 * libnetapp (optional)
712 Required for the `netapp' plugin.
713 This library is part of the “Manage ONTAP SDK” published by NetApp.
715 * libnetsnmp (optional)
716 For the `snmp' plugin.
717 <http://www.net-snmp.org/>
719 * libnotify (optional)
720 For the `notify_desktop' plugin.
721 <http://www.galago-project.org/>
723 * libopenipmi (optional)
724 Used by the `ipmi' plugin to prove IPMI devices.
725 <http://openipmi.sourceforge.net/>
727 * liboping (optional)
728 Used by the `ping' plugin to send and receive ICMP packets.
729 <http://octo.it/liboping/>
731 * libowcapi (optional)
732 Used by the `onewire' plugin to read values from onewire sensors (or the
734 <http://www.owfs.org/>
737 Used to capture packets by the `dns' plugin.
738 <http://www.tcpdump.org/>
740 * libperfstat (optional)
741 Used by various plugins to gather statistics under AIX.
744 Obviously used by the `perl' plugin. The library has to be compiled with
745 ithread support (introduced in Perl 5.6.0).
746 <http://www.perl.org/>
749 The PostgreSQL C client library used by the `postgresql' plugin.
750 <http://www.postgresql.org/>
752 * libprotobuf-c, protoc-c (optional)
753 Used by the `pinba' plugin to generate a parser for the network packets
754 sent by the Pinba PHP extension, and by the `write_riemann' plugin to
755 generate events to be sent to a Riemann server.
756 <http://code.google.com/p/protobuf-c/>
758 * libpython (optional)
759 Used by the `python' plugin. Currently, Python 2.3 and later and Python 3
761 <http://www.python.org/>
763 * librabbitmq (optional; also called “rabbitmq-c”)
764 Used by the `amqp' plugin for AMQP connections, for example to RabbitMQ.
765 <http://hg.rabbitmq.com/rabbitmq-c/>
767 * librdkafka (optional; also called “rdkafka”)
768 Used by the `write_kafka' plugin for producing messages and sending them
770 <https://github.com/edenhill/librdkafka>
772 * librouteros (optional)
773 Used by the `routeros' plugin to connect to a device running `RouterOS'.
774 <http://octo.it/librouteros/>
777 Used by the `rrdtool' and `rrdcached' plugins. The latter requires RRDtool
778 client support which was added after version 1.3 of RRDtool. Versions 1.0,
779 1.2 and 1.3 are known to work with the `rrdtool' plugin.
780 <http://oss.oetiker.ch/rrdtool/>
782 * librt, libsocket, libkstat, libdevinfo (optional)
783 Various standard Solaris libraries which provide system functions.
784 <http://developers.sun.com/solaris/>
786 * libsensors (optional)
787 To read from `lm_sensors', see the `sensors' plugin.
788 <http://www.lm-sensors.org/>
790 * libsigrok (optional)
791 Used by the `sigrok' plugin. In addition, libsigrok depends on glib,
792 libzip, and optionally (depending on which drivers are enabled) on
793 libusb, libftdi and libudev.
795 * libstatgrab (optional)
796 Used by various plugins to collect statistics on systems other than Linux
798 <http://www.i-scream.org/libstatgrab/>
800 * libtokyotyrant (optional)
801 Used by the `tokyotyrant' plugin.
802 <http://1978th.net/tokyotyrant/>
804 * libupsclient/nut (optional)
805 For the `nut' plugin which queries nut's `upsd'.
806 <http://networkupstools.org/>
809 Collect statistics from virtual machines.
810 <http://libvirt.org/>
813 Parse XML data. This is needed for the `ascent', `bind', `curl_xml' and
815 <http://xmlsoft.org/>
818 <http://www.xmms.org/>
821 Parse JSON data. This is needed for the `ceph', `curl_json' and
822 `log_logstash' plugins.
823 <http://github.com/lloyd/yajl>
825 * libvarnish (optional)
826 Fetches statistics from a Varnish instance. This is needed for the
828 <http://varnish-cache.org>
830 Configuring / Compiling / Installing
831 ------------------------------------
833 To configure, build and install collectd with the default settings, run
834 `./configure && make && make install'. For detailed, generic instructions
835 see INSTALL. For a complete list of configure options and their description,
836 run `./configure --help'.
838 By default, the configure script will check for all build dependencies and
839 disable all plugins whose requirements cannot be fulfilled (any other plugin
840 will be enabled). To enable a plugin, install missing dependencies (see
841 section `Prerequisites' above) and rerun `configure'. If you specify the
842 `--enable-<plugin>' configure option, the script will fail if the depen-
843 dencies for the specified plugin are not met. In that case you can force the
844 plugin to be built using the `--enable-<plugin>=force' configure option.
845 This will most likely fail though unless you're working in a very unusual
846 setup and you really know what you're doing. If you specify the
847 `--disable-<plugin>' configure option, the plugin will not be built. If you
848 specify the `--enable-all-plugins' or `--disable-all-plugins' configure
849 options, all plugins will be enabled or disabled respectively by default.
850 Explicitly enabling or disabling a plugin overwrites the default for the
851 specified plugin. These options are meant for package maintainers and should
852 not be used in everyday situations.
854 By default, collectd will be installed into `/opt/collectd'. You can adjust
855 this setting by specifying the `--prefix' configure option - see INSTALL for
856 details. If you pass DESTDIR=<path> to `make install', <path> will be
857 prefixed to all installation directories. This might be useful when creating
858 packages for collectd.
860 Configuring with libjvm
861 -----------------------
863 To determine the location of the required files of a Java installation is not
864 an easy task, because the locations vary with your kernel (Linux, SunOS, …)
865 and with your architecture (x86, SPARC, …) and there is no ‘java-config’
866 script we could use. Configuration of the JVM library is therefore a bit
869 The easiest way to use the `--with-java=$JAVA_HOME' option, where
870 `$JAVA_HOME' is usually something like:
871 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14
873 The configure script will then use find(1) to look for the following files:
879 If found, appropriate CPP-flags and LD-flags are set and the following
880 library checks succeed.
882 If this doesn't work for you, you have the possibility to specify CPP-flags,
883 C-flags and LD-flags for the ‘Java’ plugin by hand, using the following three
884 (environment) variables:
890 For example (shortened for demonstration purposes):
892 ./configure JAVA_CPPFLAGS="-I$JAVA_HOME/include -I$JAVA_HOME/include/linux"
894 Adding "-ljvm" to the JAVA_LDFLAGS is done automatically, you don't have to
897 Generating the configure script
898 -------------------------------
900 Collectd ships with a `build.sh' script to generate the `configure'
901 script shipped with releases.
903 To generate the `configure` script, you'll need the following dependencies:
912 The `build.sh' script takes no arguments.
917 To compile correctly collectd needs to be able to initialize static
918 variables to NAN (Not A Number). Some C libraries, especially the GNU
919 libc, have a problem with that.
921 Luckily, with GCC it's possible to work around that problem: One can define
922 NAN as being (0.0 / 0.0) and `isnan' as `f != f'. However, to test this
923 ``implementation'' the configure script needs to compile and run a short
924 test program. Obviously running a test program when doing a cross-
925 compilation is, well, challenging.
927 If you run into this problem, you can use the `--with-nan-emulation'
928 configure option to force the use of this implementation. We can't promise
929 that the compiled binary actually behaves as it should, but since NANs
930 are likely never passed to the libm you have a good chance to be lucky.
932 Likewise, collectd needs to know the layout of doubles in memory, in order
933 to craft uniform network packets over different architectures. For this, it
934 needs to know how to convert doubles into the memory layout used by x86. The
935 configure script tries to figure this out by compiling and running a few
936 small test programs. This is of course not possible when cross-compiling.
937 You can use the `--with-fp-layout' option to tell the configure script which
938 conversion method to assume. Valid arguments are:
940 * `nothing' (12345678 -> 12345678)
941 * `endianflip' (12345678 -> 87654321)
942 * `intswap' (12345678 -> 56781234)
948 For questions, bug reports, development information and basically all other
949 concerns please send an email to collectd's mailing list at
950 <list at collectd.org>.
952 For live discussion and more personal contact visit us in IRC, we're in
953 channel #collectd on freenode.
959 Florian octo Forster <octo at collectd.org>,
960 Sebastian tokkee Harl <sh at tokkee.org>,
961 and many contributors (see `AUTHORS').
963 Please send bug reports and patches to the mailing list, see `Contact'