> I'm not sure how to do that in packaging except to try to guide the user into somehow not following the broken installation flow.
Maybe, *if* it's never useful to use corosync with the default shipped corosync.conf, we should just not ship it, and add a ConditionPathExists=/etc/corosync/corosync.conf to corosync.service?
> I'm not sure how to do that in packaging except to try to guide the user into somehow not following the broken installation flow.
Maybe, *if* it's never useful to use corosync with the default shipped corosync.conf, we should just not ship it, and add a ConditionPathEx ists=/etc/ corosync/ corosync. conf to corosync.service?