diff options
| author | Rainer Gerhards <rgerhards@adiscon.com> | 2009-05-18 18:39:52 +0200 |
|---|---|---|
| committer | Rainer Gerhards <rgerhards@adiscon.com> | 2009-05-18 18:39:52 +0200 |
| commit | fe5bea77ac2533faab3b7b73bc253c4dc7d702bc (patch) | |
| tree | 66df98c9369b733b023bfadcac3c52bafccaa676 /doc/design.tex | |
| parent | 93f873277bfe5ebb309ff5e92f5dc7244ebd9f1a (diff) | |
| download | rsyslog-fe5bea77ac2533faab3b7b73bc253c4dc7d702bc.tar.gz rsyslog-fe5bea77ac2533faab3b7b73bc253c4dc7d702bc.tar.xz rsyslog-fe5bea77ac2533faab3b7b73bc253c4dc7d702bc.zip | |
removed queue's UngetObj() call
... which is no longer needed thanks to the new queue design.
Diffstat (limited to 'doc/design.tex')
| -rw-r--r-- | doc/design.tex | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/design.tex b/doc/design.tex index c03e1fab..53d25313 100644 --- a/doc/design.tex +++ b/doc/design.tex @@ -433,11 +433,11 @@ message-caused. This is under the assumption that any reasonable responsive admin will hopefully test his configuration at least once before turning it into production. And config SQL errors should manifest immediately, so I expect these to be fixed before a configuration runs in production. So it is -the chore of the output module to interpret the return code it received from -its API and decide whether this is more likely action-caused or +the duty of the output module to interpret the return code it received from +the API call and decide whether the failure is more likely action-caused or message-caused. For database outputs, I would assume that it is always easy -to classify failures that can only be action-caused, especially in the -dominating case of a failed network connection or a failed server. +to classify failures that must be action-caused, especially in the +dominating cases of failed network connections or failed servers. For other outputs it may not be as easy. But, for example, all stream network outputs can detect a broken connection, so this also is a sure fit. |