diff options
author | Rainer Gerhards <rgerhards@adiscon.com> | 2009-05-13 16:00:15 +0200 |
---|---|---|
committer | Rainer Gerhards <rgerhards@adiscon.com> | 2009-05-13 16:00:15 +0200 |
commit | 4a8c02870a55e19c1bebfae5cb70d1ec5aa7c203 (patch) | |
tree | 66fe9e8b60474eee66d4dfbd50e8c50529713544 /runtime/msg.h | |
parent | 73b16a5d7703078a46d960bd8922d2ae3a662769 (diff) | |
download | rsyslog-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 'runtime/msg.h')
-rw-r--r-- | runtime/msg.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/runtime/msg.h b/runtime/msg.h index c8350626..14148441 100644 --- a/runtime/msg.h +++ b/runtime/msg.h @@ -51,7 +51,7 @@ struct msg { BEGINobjInstance; /* Data to implement generic object - MUST be the first data element! */ pthread_mutexattr_t mutAttr; -short bDoLock; /* use the mutex? */ + short bDoLock; /* use the mutex? */ pthread_mutex_t mut; flowControl_t flowCtlType; /**< type of flow control we can apply, for enqueueing, needs not to be persisted because once data has entered the queue, this property is no longer needed. */ |