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 Chrony daemon statistics: Local clock drift, offset to peers, etc.
58 Number of nf_conntrack entries.
61 Number of context switches done by the operating system.
64 CPU utilization: Time spent in the system, user, nice, idle, and related
68 CPU frequency (For laptops with speed step or a similar technology)
71 Parse statistics from websites using regular expressions.
74 Retrieves JSON data via cURL and parses it according to user
78 Retrieves XML data via cURL and parses it according to user
82 Executes SQL statements on various databases and interprets the returned
86 Mountpoint usage (Basically the values `df(1)' delivers)
89 Disk utilization: Sectors read/written, number of read/write actions,
90 average time an IO-operation took to complete.
93 DNS traffic: Query types, response codes, opcodes and traffic/octets
97 Collect individual drbd resource statistics.
100 Email statistics: Count, traffic, spam scores and checks.
101 See collectd-email(5).
104 Amount of entropy available to the system.
107 Network interface card statistics.
110 Values gathered by a custom program or script.
111 See collectd-exec(5).
114 File handles statistics.
117 Count the number of files in directories.
120 Linux file-system based caching framework statistics.
123 Receive multicast traffic from Ganglia instances.
126 Receive values over the network using the gRPC framework.
129 Hard disk temperatures using hddtempd.
132 Interface traffic: Number of octets, packets and errors for each
136 IPC counters: semaphores used, number of allocated segments in shared
140 IPMI (Intelligent Platform Management Interface) sensors information.
143 Iptables' counters: Number of bytes that were matched by a certain
147 IPVS connection statistics (number of connections, octets and packets
148 for each service and destination).
149 See http://www.linuxvirtualserver.org/software/index.html.
152 IRQ counters: Frequency in which certain interrupts occur.
155 Integrates a `Java Virtual Machine' (JVM) to execute plugins in Java
156 bytecode. See “Configuring with libjvm” below.
159 System load average over the last 1, 5 and 15 minutes.
162 Detailed CPU statistics of the “Logical Partitions” virtualization
163 technique built into IBM's POWER processors.
166 Size of “Logical Volumes” (LV) and “Volume Groups” (VG) of Linux'
167 “Logical Volume Manager” (LVM).
170 Queries very detailed usage statistics from wireless LAN adapters and
171 interfaces that use the Atheros chipset and the MadWifi driver.
174 Motherboard sensors: temperature, fan speed and voltage information,
178 Linux software-RAID device information (number of active, failed, spare
182 Query and parse data from a memcache daemon (memcached).
185 Statistics of the memcached distributed caching system.
186 <http://www.danga.com/memcached/>
189 Memory utilization: Memory occupied by running processes, page cache,
190 buffer cache and free.
193 Collects CPU usage, memory usage, temperatures and power consumption from
194 Intel Many Integrated Core (MIC) CPUs.
197 Reads values from Modbus/TCP enabled devices. Supports reading values
198 from multiple "slaves" so gateway devices can be used.
201 Publishes and subscribes to MQTT topics.
204 Information provided by serial multimeters, such as the `Metex
208 MySQL server statistics: Commands issued, handlers triggered, thread
209 usage, query cache utilization and traffic/octets sent and received.
212 Plugin to query performance values from a NetApp storage system using the
213 “Manage ONTAP” SDK provided by NetApp.
216 Very detailed Linux network interface and routing statistics. You can get
217 (detailed) information on interfaces, qdiscs, classes, and, if you can
218 make use of it, filters.
221 Receive values that were collected by other hosts. Large setups will
222 want to collect the data on one dedicated machine, and this is the
223 plugin of choice for that.
226 NFS Procedures: Which NFS command were called how often. Only NFSv2 and
230 Collects statistics from `nginx' (speak: engine X), a HTTP and mail
234 NTP daemon statistics: Local clock drift, offset to peers, etc.
237 Information about Non-Uniform Memory Access (NUMA).
240 Network UPS tools: UPS current, voltage, power, charge, utilisation,
241 temperature, etc. See upsd(8).
244 Queries routing information from the “Optimized Link State Routing”
247 - onewire (EXPERIMENTAL!)
248 Read onewire sensors using the owcapu library of the owfs project.
249 Please read in collectd.conf(5) why this plugin is experimental.
252 Read monitoring information from OpenLDAP's cn=Monitor subtree.
255 RX and TX of each client in openvpn-status.log (status-version 2).
256 <http://openvpn.net/index.php/documentation/howto.html>
259 Query data from an Oracle database.
262 The perl plugin implements a Perl-interpreter into collectd. You can
263 write your own plugins in Perl and return arbitrary values using this
264 API. See collectd-perl(5).
267 Query statistics from BSD's packet filter "pf".
270 Receive and dispatch timing values from Pinba, a profiling extension for
274 Network latency: Time to reach the default gateway or another given
278 PostgreSQL database statistics: active server connections, transaction
279 numbers, block IO, table row manipulations.
282 PowerDNS name server statistics.
285 Process counts: Number of running, sleeping, zombie, ... processes.
288 Counts various aspects of network protocols such as IP, TCP, UDP, etc.
291 The python plugin implements a Python interpreter into collectd. This
292 makes it possible to write plugins in Python which are executed by
293 collectd without the need to start a heavy interpreter every interval.
294 See collectd-python(5) for details.
297 The redis plugin gathers information from a Redis server, including:
298 uptime, used memory, total connections etc.
301 Query interface and wireless registration statistics from RouterOS.
304 RRDtool caching daemon (RRDcacheD) statistics.
307 System sensors, accessed using lm_sensors: Voltages, temperatures and
311 RX and TX of serial interfaces. Linux only; needs root privileges.
314 Uses libsigrok as a backend, allowing any sigrok-supported device
315 to have its measurements fed to collectd. This includes multimeters,
316 sound level meters, thermometers, and much more.
319 Collect SMART statistics, notably load cycle count, temperature
323 Read values from SNMP (Simple Network Management Protocol) enabled
324 network devices such as switches, routers, thermometers, rack monitoring
325 servers, etc. See collectd-snmp(5).
328 Acts as a StatsD server, reading values sent over the network from StatsD
329 clients and calculating rates and other aggregates out of these values.
332 Pages swapped out onto hard disk or whatever is called `swap' by the OS..
335 Parse table-like structured files.
338 Follows (tails) log files, parses them by lines and submits matched
342 Follows (tails) files in CSV format, parses each line and submits
346 Bytes and operations read and written on tape devices. Solaris only.
349 Number of TCP connections to specific local and remote ports.
352 TeamSpeak2 server statistics.
355 Plugin to read values from `The Energy Detective' (TED).
358 Linux ACPI thermal zone information.
361 Reads the number of records and file size from a running Tokyo Tyrant
365 Reads CPU frequency and C-state residency on modern Intel
366 turbo-capable processors.
369 System uptime statistics.
372 Users currently logged in.
375 Various statistics from Varnish, an HTTP accelerator.
378 CPU, memory, disk and network I/O statistics from virtual machines.
381 Virtual memory statistics, e. g. the number of page-ins/-outs or the
382 number of pagefaults.
385 System resources used by Linux VServers.
386 See <http://linux-vserver.org/>.
389 Link quality of wireless cards. Linux only.
392 XEN Hypervisor CPU stats.
395 Bitrate and frequency of music played with XMMS.
398 Statistics for ZFS' “Adaptive Replacement Cache” (ARC).
401 Measures the percentage of cpu load per container (zone) under Solaris 10
405 Read data from Zookeeper's MNTR command.
407 * Output can be written or sent to various destinations by the following
411 Sends JSON-encoded data to an Advanced Message Queuing Protocol (AMQP)
412 server, such as RabbitMQ.
415 Write to comma separated values (CSV) files. This needs lots of
416 diskspace but is extremely portable and can be analysed with almost
417 every program that can analyse anything. Even Microsoft's Excel..
420 Send the data to a remote host to save the data somehow. This is useful
421 for large setups where the data should be saved by a dedicated machine.
424 Of course the values are propagated to plugins written in Perl, too, so
425 you can easily do weird stuff with the plugins we didn't dare think of
426 ;) See collectd-perl(5).
429 It's possible to implement write plugins in Python using the python
430 plugin. See collectd-python(5) for details.
433 Output to round-robin-database (RRD) files using the RRDtool caching
434 daemon (RRDcacheD) - see rrdcached(1). That daemon provides a general
435 implementation of the caching done by the `rrdtool' plugin.
438 Output to round-robin-database (RRD) files using librrd. See rrdtool(1).
439 This is likely the most popular destination for such values. Since
440 updates to RRD-files are somewhat expensive this plugin can cache
441 updates to the files and write a bunch of updates at once, which lessens
445 One can query the values from the unixsock plugin whenever they're
446 needed. Please read collectd-unixsock(5) for a description on how that's
450 Sends data to Carbon, the storage layer of Graphite using TCP or UDP. It
451 can be configured to avoid logging send errors (especially useful when
455 Sends the values collected by collectd to a web-server using HTTP POST
456 requests. The transmitted data is either in a form understood by the
457 Exec plugin or formatted in JSON.
460 Sends data to Apache Kafka, a distributed queue.
463 Writes data to the log
466 Sends data to MongoDB, a NoSQL database.
469 Sends the values to a Redis key-value database server.
472 Sends data to Riemann, a stream processing and monitoring system.
475 Sends data to Sensu, a stream processing and monitoring system, via the
476 Sensu client local TCP socket.
479 Sends data OpenTSDB, a scalable no master, no shared state time series
482 * Logging is, as everything in collectd, provided by plugins. The following
483 plugins keep us informed about what's going on:
486 Writes log messages to a file or STDOUT/STDERR.
489 Log messages are propagated to plugins written in Perl as well.
490 See collectd-perl(5).
493 It's possible to implement log plugins in Python using the python plugin.
494 See collectd-python(5) for details.
497 Logs to the standard UNIX logging mechanism, syslog.
500 Writes log messages formatted as logstash JSON events.
502 * Notifications can be handled by the following plugins:
505 Send a desktop notification to a notification daemon, as defined in
506 the Desktop Notification Specification. To actually display the
507 notifications, notification-daemon is required.
508 See http://www.galago-project.org/specs/notification/.
511 Send an E-mail with the notification message to the configured
515 Submit notifications as passive check results to a local nagios instance.
518 Execute a program or script to handle the notification.
519 See collectd-exec(5).
522 Writes the notification message to a file or STDOUT/STDERR.
525 Send the notification to a remote host to handle it somehow.
528 Notifications are propagated to plugins written in Perl as well.
529 See collectd-perl(5).
532 It's possible to implement notification plugins in Python using the
533 python plugin. See collectd-python(5) for details.
535 * Value processing can be controlled using the "filter chain" infrastructure
536 and "matches" and "targets". The following plugins are available:
538 - match_empty_counter
539 Match counter values which are currently zero.
542 Match values using a hash function of the hostname.
545 Match values by their identifier based on regular expressions.
548 Match values with an invalid timestamp.
551 Select values by their data sources' values.
553 - target_notification
554 Create and dispatch a notification.
557 Replace parts of an identifier using regular expressions.
560 Scale (multiply) values by an arbitrary value.
563 Set (overwrite) entire parts of an identifier.
565 * Miscellaneous plugins:
568 Selects multiple value lists based on patterns or regular expressions
569 and creates new aggregated values lists from those.
572 Checks values against configured thresholds and creates notifications if
573 values are out of bounds. See collectd-threshold(5) for details.
576 Sets the hostname to a unique identifier. This is meant for setups
577 where each client may migrate to another physical host, possibly going
578 through one or more name changes in the process.
580 * Performance: Since collectd is running as a daemon it doesn't spend much
581 time starting up again and again. With the exception of the exec plugin no
582 processes are forked. Caching in output plugins, such as the rrdtool and
583 network plugins, makes sure your resources are used efficiently. Also,
584 since collectd is programmed multithreaded it benefits from hyper-threading
585 and multicore processors and makes sure that the daemon isn't idle if only
586 one plugin waits for an IO-operation to complete.
588 * Once set up, hardly any maintenance is necessary. Setup is kept as easy
589 as possible and the default values should be okay for most users.
595 * collectd's configuration file can be found at `sysconfdir'/collectd.conf.
596 Run `collectd -h' for a list of built-in defaults. See `collectd.conf(5)'
597 for a list of options and a syntax description.
599 * When the `csv' or `rrdtool' plugins are loaded they'll write the values to
600 files. The usual place for these files is beneath `/var/lib/collectd'.
602 * When using some of the plugins, collectd needs to run as user root, since
603 only root can do certain things, such as craft ICMP packages needed to ping
604 other hosts. collectd should NOT be installed setuid root since it can be
605 used to overwrite valuable files!
607 * Sample scripts to generate graphs reside in `contrib/' in the source
608 package or somewhere near `/usr/share/doc/collectd' in most distributions.
609 Please be aware that those script are meant as a starting point for your
610 own experiments.. Some of them require the `RRDs' Perl module.
611 (`librrds-perl' on Debian) If you have written a more sophisticated
612 solution please share it with us.
614 * The RRAs of the automatically created RRD files depend on the `step'
615 and `heartbeat' settings given. If change these settings you may need to
616 re-create the files, losing all data. Please be aware of that when changing
617 the values and read the rrdtool(1) manpage thoroughly.
620 collectd and chkrootkit
621 -----------------------
623 If you are using the `dns' plugin chkrootkit(1) will report collectd as a
624 packet sniffer ("<iface>: PACKET SNIFFER(/usr/sbin/collectd[<pid>])"). The
625 plugin captures all UDP packets on port 53 to analyze the DNS traffic. In
626 this case, collectd is a legitimate sniffer and the report should be
627 considered to be a false positive. However, you might want to check that
628 this really is collectd and not some other, illegitimate sniffer.
634 To compile collectd from source you will need:
636 * Usual suspects: C compiler, linker, preprocessor, make, ...
638 * A POSIX-threads (pthread) implementation.
639 Since gathering some statistics is slow (network connections, slow devices,
640 etc) collectd is parallelized. The POSIX threads interface is being
641 used and should be found in various implementations for hopefully all
644 * aerotools-ng (optional)
645 Used by the `aquaero' plugin. Currently, the `libaquaero5' library, which
646 is used by the `aerotools-ng' toolkit, is not compiled as a shared object
647 nor does it feature an installation routine. Therefore, you need to point
648 collectd's configure script at the source directory of the `aerotools-ng'
650 <https://github.com/lynix/aerotools-ng>
652 * CoreFoundation.framework and IOKit.framework (optional)
653 For compiling on Darwin in general and the `apple_sensors' plugin in
655 <http://developer.apple.com/corefoundation/>
657 * libatasmart (optional)
658 Used by the `smart' plugin.
659 <http://git.0pointer.de/?p=libatasmart.git>
662 The `turbostat' plugin can optionally build Linux Capabilities support,
663 which avoids full privileges requirement (aka. running as root) to read
665 <http://sites.google.com/site/fullycapable/>
667 * libclntsh (optional)
668 Used by the `oracle' plugin.
670 * libhiredis (optional)
671 Used by the redis plugin. Please note that you require a 0.10.0 version
672 or higher. <https://github.com/redis/hiredis>
675 If you want to use the `apache', `ascent', `bind', `curl', `curl_json',
676 `curl_xml', `nginx', or `write_http' plugin.
677 <http://curl.haxx.se/>
680 Used by the `dbi' plugin to connect to various databases.
681 <http://libdbi.sourceforge.net/>
683 * libesmtp (optional)
684 For the `notify_email' plugin.
685 <http://www.stafford.uklinux.net/libesmtp/>
687 * libganglia (optional)
688 Used by the `gmond' plugin to process data received from Ganglia.
689 <http://ganglia.info/>
692 Used by the `grpc' plugin. gRPC requires a C++ compiler supporting the
696 * libgcrypt (optional)
697 Used by the `network' plugin for encryption and authentication.
698 <http://www.gnupg.org/>
701 If present, the `uuid' plugin will check for UUID from HAL.
702 <http://hal.freedesktop.org/>
704 * libi2c-dev (optional)
705 Used for the plugin `barometer', provides just the i2c-dev.h header file
706 for user space i2c development.
709 For querying iptables counters.
710 <http://netfilter.org/>
713 Library that encapsulates the `Java Virtual Machine' (JVM). This library is
714 used by the `java' plugin to execute Java bytecode. See “Configuring with
716 <http://openjdk.java.net/> (and others)
719 Used by the `openldap' plugin.
720 <http://www.openldap.org/>
723 Used by the `lvm' plugin.
724 <ftp://sources.redhat.com/pub/lvm2/>
726 * libmemcached (optional)
727 Used by the `memcachec' plugin to connect to a memcache daemon.
728 <http://tangent.org/552/libmemcached.html>
731 Used by the `netlink' plugin.
732 <http://www.netfilter.org/projects/libmnl/>
734 * libmodbus (optional)
735 Used by the `modbus' plugin to communicate with Modbus/TCP devices. The
736 `modbus' plugin works with version 2.0.3 of the library – due to frequent
737 API changes other versions may or may not compile cleanly.
738 <http://www.libmodbus.org/>
740 * libmysqlclient (optional)
741 Unsurprisingly used by the `mysql' plugin.
742 <http://dev.mysql.com/>
744 * libnetapp (optional)
745 Required for the `netapp' plugin.
746 This library is part of the “Manage ONTAP SDK” published by NetApp.
748 * libnetsnmp (optional)
749 For the `snmp' plugin.
750 <http://www.net-snmp.org/>
752 * libnotify (optional)
753 For the `notify_desktop' plugin.
754 <http://www.galago-project.org/>
756 * libopenipmi (optional)
757 Used by the `ipmi' plugin to prove IPMI devices.
758 <http://openipmi.sourceforge.net/>
760 * liboping (optional)
761 Used by the `ping' plugin to send and receive ICMP packets.
762 <http://octo.it/liboping/>
764 * libowcapi (optional)
765 Used by the `onewire' plugin to read values from onewire sensors (or the
767 <http://www.owfs.org/>
770 Used to capture packets by the `dns' plugin.
771 <http://www.tcpdump.org/>
773 * libperfstat (optional)
774 Used by various plugins to gather statistics under AIX.
777 Obviously used by the `perl' plugin. The library has to be compiled with
778 ithread support (introduced in Perl 5.6.0).
779 <http://www.perl.org/>
782 The PostgreSQL C client library used by the `postgresql' plugin.
783 <http://www.postgresql.org/>
785 * libprotobuf, protoc 3.0+ (optional)
786 Used by the `grpc' plugin to generate service stubs and code to handle
787 network packets of collectd's protobuf-based network protocol.
788 <https://developers.google.com/protocol-buffers/>
790 * libprotobuf-c, protoc-c (optional)
791 Used by the `pinba' plugin to generate a parser for the network packets
792 sent by the Pinba PHP extension.
793 <http://code.google.com/p/protobuf-c/>
795 * libpython (optional)
796 Used by the `python' plugin. Currently, Python 2.3 and later and Python 3
798 <http://www.python.org/>
800 * librabbitmq (optional; also called “rabbitmq-c”)
801 Used by the `amqp' plugin for AMQP connections, for example to RabbitMQ.
802 <http://hg.rabbitmq.com/rabbitmq-c/>
804 * librdkafka (optional; also called “rdkafka”)
805 Used by the `write_kafka' plugin for producing messages and sending them
807 <https://github.com/edenhill/librdkafka>
809 * librouteros (optional)
810 Used by the `routeros' plugin to connect to a device running `RouterOS'.
811 <http://octo.it/librouteros/>
814 Used by the `rrdtool' and `rrdcached' plugins. The latter requires RRDtool
815 client support which was added after version 1.3 of RRDtool. Versions 1.0,
816 1.2 and 1.3 are known to work with the `rrdtool' plugin.
817 <http://oss.oetiker.ch/rrdtool/>
819 * librt, libsocket, libkstat, libdevinfo (optional)
820 Various standard Solaris libraries which provide system functions.
821 <http://developers.sun.com/solaris/>
823 * libsensors (optional)
824 To read from `lm_sensors', see the `sensors' plugin.
825 <http://www.lm-sensors.org/>
827 * libsigrok (optional)
828 Used by the `sigrok' plugin. In addition, libsigrok depends on glib,
829 libzip, and optionally (depending on which drivers are enabled) on
830 libusb, libftdi and libudev.
832 * libstatgrab (optional)
833 Used by various plugins to collect statistics on systems other than Linux
835 <http://www.i-scream.org/libstatgrab/>
837 * libtokyotyrant (optional)
838 Used by the `tokyotyrant' plugin.
839 <http://1978th.net/tokyotyrant/>
841 * libupsclient/nut (optional)
842 For the `nut' plugin which queries nut's `upsd'.
843 <http://networkupstools.org/>
846 Collect statistics from virtual machines.
847 <http://libvirt.org/>
850 Parse XML data. This is needed for the `ascent', `bind', `curl_xml' and
852 <http://xmlsoft.org/>
855 Used by the `xencpu' plugin.
856 <http://xenbits.xensource.com/>
859 <http://www.xmms.org/>
862 Parse JSON data. This is needed for the `ceph', `curl_json' and
863 `log_logstash' plugins.
864 <http://github.com/lloyd/yajl>
866 * libvarnish (optional)
867 Fetches statistics from a Varnish instance. This is needed for the
869 <http://varnish-cache.org>
871 * riemann-c-client (optional)
872 For the `write_riemann' plugin.
873 <https://github.com/algernon/riemann-c-client>
875 Configuring / Compiling / Installing
876 ------------------------------------
878 To configure, build and install collectd with the default settings, run
879 `./configure && make && make install'. For detailed, generic instructions
880 see INSTALL. For a complete list of configure options and their description,
881 run `./configure --help'.
883 By default, the configure script will check for all build dependencies and
884 disable all plugins whose requirements cannot be fulfilled (any other plugin
885 will be enabled). To enable a plugin, install missing dependencies (see
886 section `Prerequisites' above) and rerun `configure'. If you specify the
887 `--enable-<plugin>' configure option, the script will fail if the depen-
888 dencies for the specified plugin are not met. In that case you can force the
889 plugin to be built using the `--enable-<plugin>=force' configure option.
890 This will most likely fail though unless you're working in a very unusual
891 setup and you really know what you're doing. If you specify the
892 `--disable-<plugin>' configure option, the plugin will not be built. If you
893 specify the `--enable-all-plugins' or `--disable-all-plugins' configure
894 options, all plugins will be enabled or disabled respectively by default.
895 Explicitly enabling or disabling a plugin overwrites the default for the
896 specified plugin. These options are meant for package maintainers and should
897 not be used in everyday situations.
899 By default, collectd will be installed into `/opt/collectd'. You can adjust
900 this setting by specifying the `--prefix' configure option - see INSTALL for
901 details. If you pass DESTDIR=<path> to `make install', <path> will be
902 prefixed to all installation directories. This might be useful when creating
903 packages for collectd.
905 Configuring with libjvm
906 -----------------------
908 To determine the location of the required files of a Java installation is not
909 an easy task, because the locations vary with your kernel (Linux, SunOS, …)
910 and with your architecture (x86, SPARC, …) and there is no ‘java-config’
911 script we could use. Configuration of the JVM library is therefore a bit
914 The easiest way to use the `--with-java=$JAVA_HOME' option, where
915 `$JAVA_HOME' is usually something like:
916 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14
918 The configure script will then use find(1) to look for the following files:
924 If found, appropriate CPP-flags and LD-flags are set and the following
925 library checks succeed.
927 If this doesn't work for you, you have the possibility to specify CPP-flags,
928 C-flags, LD-flags and LIBS for the ‘Java’ plugin by hand, using the
929 following environment variables:
936 For example (shortened for demonstration purposes):
938 ./configure JAVA_CPPFLAGS="-I$JAVA_HOME/include -I$JAVA_HOME/include/linux"
940 Adding "-ljvm" to JAVA_LIBS is done automatically, you don't have to
943 Generating the configure script
944 -------------------------------
946 Collectd ships with a `build.sh' script to generate the `configure'
947 script shipped with releases.
949 To generate the `configure` script, you'll need the following dependencies:
959 The `build.sh' script takes no arguments.
964 To compile correctly collectd needs to be able to initialize static
965 variables to NAN (Not A Number). Some C libraries, especially the GNU
966 libc, have a problem with that.
968 Luckily, with GCC it's possible to work around that problem: One can define
969 NAN as being (0.0 / 0.0) and `isnan' as `f != f'. However, to test this
970 ``implementation'' the configure script needs to compile and run a short
971 test program. Obviously running a test program when doing a cross-
972 compilation is, well, challenging.
974 If you run into this problem, you can use the `--with-nan-emulation'
975 configure option to force the use of this implementation. We can't promise
976 that the compiled binary actually behaves as it should, but since NANs
977 are likely never passed to the libm you have a good chance to be lucky.
979 Likewise, collectd needs to know the layout of doubles in memory, in order
980 to craft uniform network packets over different architectures. For this, it
981 needs to know how to convert doubles into the memory layout used by x86. The
982 configure script tries to figure this out by compiling and running a few
983 small test programs. This is of course not possible when cross-compiling.
984 You can use the `--with-fp-layout' option to tell the configure script which
985 conversion method to assume. Valid arguments are:
987 * `nothing' (12345678 -> 12345678)
988 * `endianflip' (12345678 -> 87654321)
989 * `intswap' (12345678 -> 56781234)
995 For questions, bug reports, development information and basically all other
996 concerns please send an email to collectd's mailing list at
997 <list at collectd.org>.
999 For live discussion and more personal contact visit us in IRC, we're in
1000 channel #collectd on freenode.
1006 Florian octo Forster <octo at collectd.org>,
1007 Sebastian tokkee Harl <sh at tokkee.org>,
1008 and many contributors (see `AUTHORS').
1010 Please send bug reports and patches to the mailing list, see `Contact'
projects / collectd.git / blob