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
napsal:
> On Do, 23.05.19 10:29, Roger Pack (rogerdpa...@gmail.com) wrote:
>
> > As a no
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
Am 23.05.19 um 18:29 schrieb Roger Pack:
> 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
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 ex
