On 04/16/2013 11:25 PM, Marcos Felipe Rasia de Mello wrote:
Thanks for the analysis! Should I report a bug?
This is certainly a misbehaviour, what I am not convinced is what to do about it if anything. In this case systemd is just doing what it is told to do by the rpm macros.. there are a few alternatives to address this: - make systemctl to ignore --no-reload on case disable when the service or alias to service to be disabled is bound to a socket unit, the ramifications of doing this are not clear to me at the moment. - add a new macro service_del_preun_with_reload just for the few packages that use socket activation. - do nothing unless it causes a permanent functionality loss, other system component to go crazy or breaks update/upgrade even after reboot. Also consider that this happends in the time window between rpm %preun where /usr/bin/systemctl --no-reload disable .. is called,,, and %postun (where systemctl daemon-reload is executed and therefore knows the system configuration has changed) Frederic ..what you think about this? none of the options sound appealing to me at this stage.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org