Description of problem:
After an update of iiimf-server it starts on boot, even when the
previous version was set to not start on boot. So if iiimf-server is
installed, but not in use, a user who thinks they have it disabled
will have it re-enabled at boot when they upgrade.
Version-Release number of selected component (if applicable):
iiimf-server-12.1-10.FC3.i386.rpm and earlier
Get an older version of iiimf-server, turn it off on boot, upgrade.
Steps to Reproduce:
rpm -U --oldpackage iiimf-server-[older one]
chkconfig --del iiimf
rpm -U iiimf-server-12.1-10.FC3.i386.rpm
chkconfig --list | grep iiim [shows iiim on]
iiim is set to start on boot.
iiim is left at it's previous setting to not start on reboot. Apache,
for example, honors it's previous setting.
This is similar to a cups bug that was fixed a couple days ago:
Sorry, should be using
chkconfig iiim off