From 1250b5d735129c3e04c45484f80f99cdb12f39a1 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Sat, 22 Jan 2011 01:08:36 +0100 Subject: ratelimit: fix log levels of log suppression messages When logging a suppression message do so on the same log level as the suppressed messages. Cherry picked by Colin Guthrie from ec5a7857127a1b3b9c5517c4a70a9b2c8aab35ca with a couple of additional changes due to extra limiting in master that was not present in stable-queue. --- src/modules/module-udev-detect.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/modules/module-udev-detect.c') diff --git a/src/modules/module-udev-detect.c b/src/modules/module-udev-detect.c index 2eecc25a..1eaa84fd 100644 --- a/src/modules/module-udev-detect.c +++ b/src/modules/module-udev-detect.c @@ -324,7 +324,7 @@ static void verify_access(struct userdata *u, struct device *d) { * during opening was canceled by a "try again" * failure or a "fatal" failure. */ - if (pa_ratelimit_test(&d->ratelimit)) { + if (pa_ratelimit_test(&d->ratelimit, PA_LOG_DEBUG)) { pa_log_debug("Loading module-alsa-card with arguments '%s'", d->args); m = pa_module_load(u->core, "module-alsa-card", d->args); -- cgit