On Mon, 2020-11-02 at 16:40 -0600, Benjamin Marzinski wrote: > > I do believe that syslog is allowed to block the caller, but I agree > that we've mostly moved on to a systemd world where multipathd is > writing to stderr. Removing this will make multipathd run a real risk > of > hanging on logging when not run through systemd. I just don't know > how > likely that scenario is anymore. So, you really think that journald is doing a better job at not blocking clients than syslogd? Wouldn't syslogd be truly optimized for exactly this use case? Being "allowed" to block clients is one thing, actually doing it is another. Martin -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
