Bug ID 979850
Summary named cannot be started directly after installation
Classification openSUSE
Product openSUSE Distribution
Version Leap 42.1
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Other
Assignee bnc-team-screening@forge.provo.novell.com
Reporter wolfgang@rosenauer.org
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

named cannot be started directly after installation.

zypper in bind
ds9:~ # rcnamed start
redirecting to systemctl start named.service
Failed to start named.service: Unit named.service failed to load: No such file
or directory.

I had to manually execute
systemctl daemon-reload
before it worked.

The facts I found:
bind still has no unit file but still an old LSB sysV one.
It calls fillup_and_insserv in %post

According to the manpage "insserv" is supposed to control systemd on 42.1.

Therefore my expectation is that it should work although the package does not
obey https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines

As I'm confused what is supposed to work how I have no idea if the bug is in
the %post of bind or in insserv or anywhere else.


You are receiving this mail because: