Created attachment 373329 [details] certmaster init script following current Fedora template The certmaster service defaults to on when installed. I believe that as a network-listening service it should default to off and require the user to enable it. Further, when redhat-lsb is installed (as it is by default), the %post script runs /usr/lib/lsb/install_initd /etc/init.d/certmaster rather than /sbin/chkconfig --add certmaster. Running chkconfig --list certmaster then yields: $ sudo chkconfig --list certmaster service certmaster supports chkconfig, but is not referenced in any runlevel (run 'chkconfig --add certmaster') This is really a bug in redhat-lsb, as it creates /usr/lib/lsb/install_initd as a symlink to chkconfig, but chkconfig requires an --add option to function as intended. Still, the comments in the %post section indicate install_initd usage is "for suse" and chkconfig is "for red hat distros". I think at the least certmaster should default to off. And until such time as the redhat-lsb bug is fixed, certmaster should ensure that it uses chkconfig when installed on Fedora/RHEL/CentOS. I am attaching a certmaster init script that follows the Fedora packaging guidelines¹ a bit closer. This may or may not be appropriate for upstream certmaster, but I think it fits Fedora/RHEL/CentOS a little better. If you'd like, I can provide a patch to the certmaster spec file to follow the Fedora guidelines for installing and removing initscripts more closely. ¹ https://fedoraproject.org/wiki/Packaging:SysVInitScript
agreed. Two relatively short fixes, I think.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This issue is still present in rawhide. It was discussed on the func-list a few months back. It doesn't appear that any fix was submitted/committed upstream though. https://www.redhat.com/archives/func-list/2011-April/msg00028.html
fixed upstream now. thank you.