The handling of signal when using threads can be complicated. When
ring buffer is used for query, this means ulogd will have to follow
some sort of mutex. Thus, it is easier and better performance wise
to disable the reload via SIGHUP when the ring buffer is used.
Signed-off-by: Eric Leblond <eric@xxxxxxxxx>
---
util/db.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/util/db.c b/util/db.c
index 4050f0f..c23c362 100644
--- a/util/db.c
+++ b/util/db.c
@@ -607,11 +607,16 @@ static void *__inject_thread(void *gdi)
void ulogd_db_signal(struct ulogd_pluginstance *upi, int signal)
{
+ struct db_instance *di = (struct db_instance *) &upi->private;
switch (signal) {
case SIGHUP:
- /* reopen database connection */
- ulogd_db_instance_stop(upi);
- ulogd_db_start(upi);
+ if (!di->ring.size) {
+ /* reopen database connection */
+ ulogd_db_instance_stop(upi);
+ ulogd_db_start(upi);
+ } else
+ ulogd_log(ULOGD_ERROR,
+ "No SIGHUP handling if ring buffer is used\n");
break;
default:
break;
--
1.7.10.4
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
