summaryrefslogtreecommitdiffstats
path: root/action.c
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2009-05-13 16:00:15 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2009-05-13 16:00:15 +0200
commit4a8c02870a55e19c1bebfae5cb70d1ec5aa7c203 (patch)
tree66fe9e8b60474eee66d4dfbd50e8c50529713544 /action.c
parent73b16a5d7703078a46d960bd8922d2ae3a662769 (diff)
downloadrsyslog-4a8c02870a55e19c1bebfae5cb70d1ec5aa7c203.tar.gz
rsyslog-4a8c02870a55e19c1bebfae5cb70d1ec5aa7c203.tar.xz
rsyslog-4a8c02870a55e19c1bebfae5cb70d1ec5aa7c203.zip
moved user object destruction to queue itself
So far, the consumer was responsible for destroying objects. However, this does not work well with ultra-reliable queues. This is the first move to support them.
Diffstat (limited to 'action.c')
-rw-r--r--action.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/action.c b/action.c
index 0253e1b6..424cb00b 100644
--- a/action.c
+++ b/action.c
@@ -905,7 +905,6 @@ processAction(action_t *pAction, batch_t *pBatch)
/* this must be moved away - up into the dequeue part of the queue, I guess, but that's for another day */
for(i = 0 ; i < pBatch->nElem ; i++) {
pMsg = (msg_t*) pBatch->pElem[i].pUsrp;
- msgDestruct(&pMsg); /* TODO: change: we are now finished with the message */
}
iRet = finishBatch(pAction);