summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 1c9b59f)
raw | patch | inline | side by side (parent: 1c9b59f)
author | Sebastian Harl <sh@tokkee.org> | |
Sun, 7 Oct 2007 13:02:36 +0000 (15:02 +0200) | ||
committer | Florian Forster <octo@huhu.verplant.org> | |
Tue, 9 Oct 2007 16:02:20 +0000 (18:02 +0200) |
Indent all paragraphs by two spaces and break lines after 79 characters.
Signed-off-by: Sebastian Harl <sh@tokkee.org>
Signed-off-by: Florian Forster <octo@huhu.verplant.org>
Signed-off-by: Sebastian Harl <sh@tokkee.org>
Signed-off-by: Florian Forster <octo@huhu.verplant.org>
README | patch | blob | history |
index f1d78600c2466a5f6f8a0d85d968e1077c93bbad..56dee295733b0459e38051e029b7ba4937abe2a8 100644 (file)
--- a/README
+++ b/README
* When the `csv' or `rrdtool' plugins are loaded they'll write the values to
files. The usual place for these files is beneath `/var/lib/collectd'.
- * When using some of the plugins, collectd needs to run as user root, since only
- root can do certain things, such as craft ICMP packages needed to ping
+ * When using some of the plugins, collectd needs to run as user root, since
+ only root can do certain things, such as craft ICMP packages needed to ping
other hosts. collectd should NOT be installed setuid root since it can be
used to overwrite valuable files!
Crosscompiling
--------------
- To compile correctly collectd needs to be able to initialize static
- variables to NAN (Not A Number). Some C libraries, especially the GNU
- libc, have a problem with that.
+ To compile correctly collectd needs to be able to initialize static
+ variables to NAN (Not A Number). Some C libraries, especially the GNU
+ libc, have a problem with that.
- Luckily, with GCC it's possible to work around that problem: One can define
- NAN as being (0.0 / 0.0) and `isnan' as `f != f'. However, to test this
- ``implementation'' the configure script needs to compile and run a short
- test program. Obviously running a test program when doing a cross-
- compilation is, well, challenging.
+ Luckily, with GCC it's possible to work around that problem: One can define
+ NAN as being (0.0 / 0.0) and `isnan' as `f != f'. However, to test this
+ ``implementation'' the configure script needs to compile and run a short
+ test program. Obviously running a test program when doing a cross-
+ compilation is, well, challenging.
- If you run into this problem, you can use the `--with-nan-emulation'
- configure option to force the use of this implementation. We can't promise
- that the compiled binary actually behaves as it should, but since NANs
- are likely never passed to the libm you have a good chance to be lucky.
+ If you run into this problem, you can use the `--with-nan-emulation'
+ configure option to force the use of this implementation. We can't promise
+ that the compiled binary actually behaves as it should, but since NANs
+ are likely never passed to the libm you have a good chance to be lucky.
Contact