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