On Sat, 2018-03-03 at 01:31 +0100, Martin Wilck wrote: > So, there's no reason not to block them, right? Is it expected behavior > that a user running 'kill -USR2 $(pidof multipathd)' terminates the > process? Why do you think these signals should interrupt ppoll() > although the uxlsnr can't can't handle them? Isn't it sufficient that > they're handled by the threads that are meant to do that?
Blocking all signals except the ones for which we installed a handler sounds weird to me. I think users expect daemons to process signals instead of blocking all but a specific set of signals. This is a rather philosophical argument and not an argument of which I think that it is strong enough to prevent this patch of being integrated in the upstream multipath-tools repository. Bart. -- dm-devel mailing list dm-devel@redhat.com https://www.redhat.com/mailman/listinfo/dm-devel
