Comment # 51 on bug 905639 from Joe Morris

Reference https://bugzilla.novell.com/show_bug.cgi?id=905639#c19

In openSUSE 13.1, with systemd-210 from Baseystem repository, fix.service
creates a boot conflict with named so that bind will not start on boot.

2015-02-28T19:54:05.551911+08:00 jmorris systemd[1]: Found dependency on
named.service/stop
2015-02-28T19:54:05.552938+08:00 jmorris systemd[1]: Found dependency on
fix.service/stop
2015-02-28T19:54:05.553528+08:00 jmorris systemd[1]: Found dependency on
nss-lookup.target/stop
2015-02-28T19:54:05.554081+08:00 jmorris systemd[1]: Breaking ordering cycle by
deleting job named.service/stop
2015-02-28T19:54:05.554659+08:00 jmorris systemd[1]: Job named.service/stop
deleted to break ordering cycle starting with nss-lookup.target/stop

Disabling fix.service doesn't fix it. Only renaming fix.service (or deleting)
allows bind to start on boot. I don't use autofs or nfs anyway. I installed
systemd-210 after the problematic patches for systemd-208 were causing daily
crashes. systemd-210 works well, except for this one problem with fix.service.