Overview
| Comment: | Added a troubleshooting section to the README about C11 atomics and broken versions of gcc |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
afddda9b5db8382c4e5576fe6652ec25 |
| User & Date: | rkeene on 2016-02-23 05:24:47 |
| Other Links: | manifest | tags |
Context
|
2016-03-03
| ||
| 04:21 | Fixed bugs related to not using C11 atomics check-in: 4ce6697da8 user: rkeene tags: trunk | |
|
2016-02-23
| ||
| 05:24 | Added a troubleshooting section to the README about C11 atomics and broken versions of gcc check-in: afddda9b5d user: rkeene tags: trunk | |
|
2016-02-22
| ||
| 23:25 | Updated man page version to be in-sync with the rest of the source check-in: 8f1b3e35fb user: rkeene tags: trunk | |
Changes
Modified README from [4a3d6cb02a] to [d62e07fe87].
| ︙ | ︙ | |||
90 91 92 93 94 95 96 | Because "filed" relies on chroot(2) and setuid(2), log files cannot reliably be re-opened. If you need log rotation then a second process, which can close and re-open log files, must be used. Any process may be used for writing logs but if the process does not support log rotation then it will not provide that benefit. For example, if you wish to write logs to syslogd(8) you can use logger(1), such as: # ./filed --root /www --user nobody --log '|logger -t filed' --daemon | > > > > > > > > > > > > > > > | 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 |
Because "filed" relies on chroot(2) and setuid(2), log files cannot reliably
be re-opened. If you need log rotation then a second process, which can close
and re-open log files, must be used. Any process may be used for writing logs
but if the process does not support log rotation then it will not provide that
benefit. For example, if you wish to write logs to syslogd(8) you can use
logger(1), such as:
# ./filed --root /www --user nobody --log '|logger -t filed' --daemon
Troubleshooting
---------------
1. It won't compile, something about stdatomic.h not found or _Atomic not
a valid type.
=> This is a bug in your compiler:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58016
GCC 4.7.x and 4.8.x define the macro indicating that they have C11
support and do not define the macro that C11 requires to indicate
that C11 atomics are not available. They should define that macro.
You can disable the features in "filed" that require C11 atomics by
defining FILED_DONT_TIMEOUT in the Makefile.
|