I just installed this newest iteration of opensuse (coming from 11.3); there is a lot to learn, I have to say
Anyway, what I gathered is, that instead of rc…/init.d service files, there are the new systemd .service files, which lie in “/etc/systemd/system/multi-user.wants” (or something like that).
The problem is: the installed and manually configured named daemon won’t start automatically with the system.
But has no problem starting manually via “systemctl start named”!? (or “rcnamed start” for that matter!)
And I even tried editing/starting the DNS service via yast (which tells me the service is set to start automatically and is started), but that didn’t help either!
What am I missing?
Where is the service file?
How can it be that it won’t start automatically?
I failed to mention that I of course enabled the service via Yast.
And this too should have happened after I configured named via Yast (this I did mention :P)
But you mentioned systemctl enable %service%.
Is there a way to show if it’s already enabled? (like systemctl show %service%) -> ok, of course there already is a “show” command, just not the info I wanted…:X
On 07/30/2016 05:46 PM, tsu2 wrote:
>
> For all systemd services, you can configure any to start by setting
> “enable”
>
> For example the following
>
> Code:
> --------------------
> systemctl enable named.service
> --------------------
>
>
> You can view all the options of systemctl the usual way by “–help” for
> example
>
> Code:
> --------------------
> systemctl --help
> --------------------
>
You can also use <tab><tab> for command completion.
Using:
<code>
systemctl enable <tab><tab>
</code>
will show all of the services that are not enabled but can be enabled.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
This depends on whether it is native systemd unit for named or it is compatibility sysvinit service. For native units “systemctl status named.service” shows whether it is enabled or disabled. For compatibility services you need to use chkconfig; systemctl does not show it. You can distinguish native vs. compat by path which is shown on “Loaded” line. If it is /etc/init.d/named, this is compatibility service,
Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols and provides an openly redistributable reference implementation of the major components of the Domain Name System. This package includes the components to operate a DNS server.
Nscd caches name service lookups and can dramatically improve performance with NIS, NIS+, and LDAP.
Taking another look at BIND, agreed that it’s still a SysVinit service, so the following returns the named service status
chkconfig named
As arvidjaar points out, nscd is a service that exists on all networked openSUSE and performs hostname caching even as a client. In fact, if you need to purge your hostnames cache, restart this nscd service.
Although arvidjaar is correct that “SysVinit compatibility” services can be identified by the stated init.d path, that’s not 100%. In the past, I’ve found a few Unit files with the same executable path (pointing to the init.d script or binary), so YMMV.
That’s interesting that dnsmasq is no longer installed by default (at least on LEAP). I remember years of dnsmasq throwing non-critical errors (in 13.2?) which I never got around to looking into.
Well, I don’t know why or how but named is starting automatically on boot now. And it’s true, this seems to be an older “rc” SysV service. What ever, as long as it’s working
