Description of problem: It takes no effect when using "setup" to disable sshd and other system services, but chkconfig can (by chkconfig somethingd off). Version-Release number of selected component (if applicable): setuptool-1.19.11-3.fc15.x86_64 chkconfig-1.3.52-1.fc15.x86_64 How reproducible: Everytime Steps to Reproduce: 1. $ sudo setup 2. Enter "System services" and uncheck the sshd service; 3. quit setup and reboot. Actual results: sshd still starts after rebooting. Expected results: sshd should not starts automatically after rebooting. Additional info: "chkconfig sshd off" works well.
Cannot reproduce. Is rebooting strictly required? If you run the following as root user runlevel chkconfig --list sshd ntsysv # <-- here disable sshd chkconfig --list sshd does the ntsysv tool fail to disable sshd for you? (Or does it get re-enabled after a reboot only?)
Actually, if a service is still "on" for any runlevel, systemd will happily start it because of its different runlevel concept. "systemctl disable sshd" also runs a full "chkconfig sshd off" instead of giving it just the current runlevel. ntsysv would need to do the same for compatibility.
Hm, that would be a rather abrupt behavior change, but I can see how that would make sense.
(In reply to comment #1) > Cannot reproduce. Is rebooting strictly required? > > If you run the following as root user > > runlevel > chkconfig --list sshd > ntsysv # <-- here disable sshd > chkconfig --list sshd > > does the ntsysv tool fail to disable sshd for you? (Or does it get re-enabled > after a reboot only?) The ntsysv only disabled sshd on runlevel 5.
http://git.fedorahosted.org/git/?p=chkconfig.git;a=commitdiff;h=5c0e515fdd19c89ab45f6b5d0e5587c3ca21804e This will be in Fedora 16; it will not be backported to Fedora 15.