-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Roland McGrath wrote:
No. chkconfig service on will only set it for the current runlevel,
no, this is not true...
chkconfig cups off
Will result in
[root@localhost ~]# chkconfig cups off [root@localhost ~]# chkconfig cups --list cups 0:off 1:off 2:off 3:off 4:off 5:off 6:off
Enabling the service via
chkconfig cups on
results in:
[root@localhost ~]# chkconfig cups --list cups 0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@localhost ~]# chkconfig cups on [root@localhost ~]# chkconfig cups --list cups 0:off 1:off 2:on 3:on 4:on 5:on 6:off
In other word, if you do NOT specify the run levels to change, chkconfig will, by default, "on" or "off" runlevels 2,3,4,5
although the man page doesn't make this obvious.
And in fact, this behaviour *IS* stated in the man page:
By default, the on and off options affect only runlevels 2, 3, 4, and 5, while reset and resetpriorities affects all of the runlevels. The --level option may be used to specify which runlevels are affected.
In fact, it's thoroughly non-obvious, counter-intuitive and makes one wonder what chkconfig is supposed to be good for.
Seems pretty clear to me... Perhaps you haven't read the man page?
All the best,
- -Greg
- -- +---------------------------------------------------------------------+
Please also check the log file at "/dev/null" for additional information. (from /var/log/Xorg.setup.log)
| Greg Hosler ghosler@redhat.com | +---------------------------------------------------------------------+