On Thu, Mar 24, 2022 at 10:19:27PM +0100, mwi...@suse.com wrote:
> From: Martin Wilck <mwi...@suse.com>
>
> The "reset log" message isn't very important, and the others will
> be followed by more meaningful messages when multipathd actually
> exits, or reconfigures itself.
>
> Signed-off-by: Martin Wilck <mwi...@suse.com>
Reviewed-by: Benjamin Marzinski <bmarz...@redhat.com>
> ---
> multipathd/main.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/multipathd/main.c b/multipathd/main.c
> index aee0953..1406251 100644
> --- a/multipathd/main.c
> +++ b/multipathd/main.c
> @@ -2927,18 +2927,18 @@ void
> handle_signals(bool nonfatal)
> {
> if (exit_sig) {
> - condlog(2, "exit (signal)");
> + condlog(3, "exit (signal)");
> exit_sig = 0;
> exit_daemon();
> }
> if (!nonfatal)
> return;
> if (reconfig_sig) {
> - condlog(2, "reconfigure (signal)");
> + condlog(3, "reconfigure (signal)");
> schedule_reconfigure(FORCE_RELOAD_WEAK);
> }
> if (log_reset_sig) {
> - condlog(2, "reset log (signal)");
> + condlog(3, "reset log (signal)");
> if (logsink == LOGSINK_SYSLOG)
> log_thread_reset();
> }
> --
> 2.35.1
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
