<div dir="ltr"><div>I think the behaviour is correct, chkconfig --add is kinda sysv equivalent of systemctl preset. </div>systemctl enable should be the same as chkconfig on.<div><br></div><div>Lukas<br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">čt 23. 5. 2019 v 20:40 odesílatel Lennart Poettering <<a href="mailto:lennart@poettering.net">lennart@poettering.net</a>> napsal:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Do, 23.05.19 10:29, Roger Pack (<a href="mailto:rogerdpack2@gmail.com" target="_blank">rogerdpack2@gmail.com</a>) wrote:<br>
<br>
> As a note, if I have a sysV /etc/init.d/name service that is "turned<br>
> on" by "chkconfig --add name" it seems that it adds it to *different<br>
> targets* than what "systemctl enable name" does (which appears to run<br>
> "chkconfig name on" enabling it for all runlevels). This seems a bit<br>
> confusing? is it expected? Or perhaps my systemd version is just<br>
> old?<br>
<br>
It's probably a question to ask the chkconfig community, I am not sure<br>
what the difference is, and the man page is not particularly<br>
enlightening.<br>
<br>
Note that systemd is not invoking chkconfig directly but instead<br>
/usr/lib/systemd/systemd-sysv-install which is supposed to do the<br>
right thing, and it's up to the distros to make that a shell script or<br>
so that does the right thing. hence it's entirely within the domain of<br>
the distro/chkconfig to do the right thing, we don't control that from<br>
systemd's side.<br>
<br>
Lennart<br>
<br>
--<br>
Lennart Poettering, Berlin<br>
_______________________________________________<br>
systemd-devel mailing list<br>
<a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a></blockquote></div></div></div>