https://bugzilla.novell.com/show_bug.cgi?id=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c0 Summary: After installing bind9 (named) no menue entry for service manager (YaST) to activate named at boot Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: hfischer@eschkitai.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 After installing bind9/named there is no menue entry in service manager/YaST to get named starting at system boot. Trying 'systemctl enable [TAB,TAB] does not list a named.service oder a bind.service. Trying 'systemctl enable named.service' I got following message: named.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig named on The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). But: Now named is listed in YaST's service manager. Named can be started using the service manager. This setting remains a reboot. Looking at /etc/init.d there was listed an initscript for named. I think, starting named uses the old way over the initd way. It would be very fine, to get an service script for systemd and an entry for the service manager/YaST to enable the service. It was a lucky idea to try 'systemctl enable named.service'. But this can't be a regular solution. Reproducible: Always Steps to Reproduce: 1. Installing bind9/named with the software manager/YaST 2. Try to start/enable named for starting at boot with service manager => no named or bind 3. And now? User/admin can try /etc/init.d/named start and have to search a method for starting the named service at systemboot. (I think, an experience admin look for chkconfig, but using the systemd way is better). Expected Results: After installing bind9/named there should appear the service in the list of YaST's service manager to activate/deactivate and start/stop the service. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.