systemctl command that is the same as chkconfig --level

[Tom H]

On Sat, Jun 18, 2011 at 4:45 PM, Aaron Konstam <akonstam at sbcglobal.net> wrote:
> On Sat, 2011-06-18 at 10:30 -0400, Tom H wrote:
>>
>> Running "systemctl enable nfs" set it up to start in runlevels 2 3 4 5
>> and stop in runlevels 0 1 6 in the same way that "chkconfig nfs on"
>> would (in fact, since the nfs server's a legacy service, there's a
>> message that systemctl's handing over to chkconfig - I've forgotten
>> the actual wording).
>>
>> Since runlevels 2 3 4 are symlinked to multi-user.target, ...
>
> That is certainly useful information.
> But: chkconfig --level 35 nfs on
> would start on entering runlevel 3 and 5 and not on entering runlevel 2
> 4. Are you saying you can't arrange to do that in systemd. Is that
> considered a step up?

If you run "chkconfig --list" on F14 or F15, you'll see that many
services are started on the mostly (completely?) unused runlevels 2
and 4. So, in turning 2, 3, 4 into the same runlevel, systemd's just
turning a common practice into a fact.

If you need a distinct runlevel 2 or 4, you can create it/them. It'll
require more work now than in F14 or in F16/F17/... when all init
daemons will be native systemd daemons.