Bug #1284
Syslog does not work with CLOG disabled
| Status: | Resolved | Start date: | 02/15/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jim P |
% Done: | 100% |
|
| Category: | - | |||
| Target version: | 2.1 | |||
| Affected version: | Affected Architecture: |
Description
I put the tag disablesyslogclog on my config.xml to disable clog, since I have free disk space and want to keep all log history.
After rebooting the system the log files were created, but they have no data. Then I realized that syslogd was not running, it was returning the following error:
syslogd: child pid 34576 exited on signal 11
pfsense_syslog.diff
(1.7 kB)
Associated revisions
Resolves #1284. Merge patch submitted a bit differentely
History
#1
Updated by Vinícius Coque over 2 years ago
- File pfsense_syslog.diff added
Maybe I found the problem.
On system boot, it checks if disablesyslogclog tag exists on config.xml, then create regular files for logs. But the PHP function system_syslogd_start() isn't checking if disablesyslogclog is set and aways set clog of fifolog on syslog.conf. When syslogd open a regular log file and tries to read it as a clog or fifolog file occurs a segmentation fault.
I think the patch attached can solve this.
#3
Updated by Ermal Luçi 3 months ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 100f3e7191a0c720857316c4ba0cac0890fe8177.
