diff options
author | Rainer Gerhards <rgerhards@adiscon.com> | 2005-07-25 08:47:28 +0000 |
---|---|---|
committer | Rainer Gerhards <rgerhards@adiscon.com> | 2005-07-25 08:47:28 +0000 |
commit | 40c0e4e009ba32369e668aaa548259232b2a06bf (patch) | |
tree | 3badaf8c23dd9f30e2636671c664ce84d5e4a6d3 /BUGS | |
parent | 7fd623f9cdce82e7e3659ccc2a32702a8d396af0 (diff) | |
download | rsyslog-40c0e4e009ba32369e668aaa548259232b2a06bf.tar.gz rsyslog-40c0e4e009ba32369e668aaa548259232b2a06bf.tar.bz2 rsyslog-40c0e4e009ba32369e668aaa548259232b2a06bf.zip |
some minor cleanup (mostly doc) in preparation for 0.9.4
Diffstat (limited to 'BUGS')
-rw-r--r-- | BUGS | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -40,6 +40,20 @@ BUILDING WITH MYSQL and such. Building with MySQL is currently not as straightforward as it should be ;) +CALLS to exit() + I have removed all calls to exit() I have introduced. However, there are + still some left from the original code. Most of them are OK, being done + on initial startup when a severe error happens. There are some, I think, + that might happen during runtime when a memory shortag is detected. We + should look into this issues. Finding some smarter code would allow + rsyslog to become even more fault-tolerant (but obviously, there is always + a cost, in this case most probably the loss of at least on message). + +SIGPIPE HANDLING + Currently, SIGPIPE is ignored. This is necessary to handle broken TCP + connections. We should further look into this issue and see which other + ways exist to handle the situation. + Updates to the bug lists (and potential fixes...) can be found at the official home page at |