systemctl command that is the same as chkconfig --level

[Mike Wright]

On 06/19/2011 06:11 AM, Aaron Konstam wrote:
> On Sat, 2011-06-18 at 15:02 -0600, Petrus de Calguarium wrote:
>> Aaron Konstam wrote:
>>
>>> 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?
>>
>> As I understand it (could be inaccurate :-) ), there are no run levels 0, 1,
>> 2, 3, 4, 5&c, so you are trying to impose a legacy paradigm onto the current
>> one. The computer does not go into run levels 3 or 5, because they don't
>> exist. It goes into multi-user or graphical target.
>>
>> AIUI, when you want nfs.service to come on in multi-user and graphical
>> targets, you issue the command systemctl enable nfs.service as root.
>>
>> Perhaps you could be more specific (or restate, in case you already did
>> earlier) about what you wish to do and someone else can try to give a more
>> specific answer to help you get the setup you are seeking to achieve.
>>
>
> You have made it clear that I have been using and old an useless
> paradigm. I had thought of that before. One never goes into runlevel 2
> or 4.

I've been running a fedora 4 xen box since 2006 and use runlevel 4 
exclusively for xen.  Xen is off in all other levels.  Having a user 
runlevel allows for extremely granular control of services.

  Although there is still is a type of runlevel 1. It is called:
> rescue.target.
> Thanks for setting me straight. Sometimes it takes longer to see the
> obvious.