Description of problem: Fedora Packaging says on their page https://fedoraproject.org/wiki/Packaging/SysVInitScript Packages with SysV-style initscripts must put any them into /etc/rc.d/init.d. A rpm macro exists for this directory, %_initrddir. In the past, some packages were putting files in /etc/init.d instead of /etc/rc.d/init.d. (/etc/init.d is a symlink to /etc/rc.d/init.d) This split made it more difficult to use yum install against the initscript filename and path. Since /etc/init.d is the symlink (and because the Filesystem Hierarchy Standard does not mandate a location), Fedora requires that all SysV-style initscripts must go into the full /etc/rc.d/init.d directory. The packages osad, osa-dispatcher, spacewalk-search and spacewalk-taskomatic put their initscripts to /etc/init.d. Version-Release number of selected component (if applicable): On server: osa-dispatcher-5.9.2-1.el5 spacewalk-search-0.4.10-1.el5 spacewalk-taskomatic-0.4.16-1.el5 On client: osad-5.9.2-1.el5 How reproducible: Deterministic. Steps to Reproduce: 1. rpm -ql osad osa-dispatcher spacewalk-search spacewalk-taskomatic | grep '/etc.*/init\.d/' Actual results: /etc/init.d/osad /etc/init.d/osa-dispatcher /etc/init.d/rhn-search /etc/init.d/taskomatic Expected results: /etc/rc.d/init.d/osad /etc/rc.d/init.d/osa-dispatcher /etc/rc.d/init.d/rhn-search /etc/rc.d/init.d/taskomatic Additional info:
taskomatic fixed
rhn-search fixed in commit 2c121b5a170763fb86afa902159a59a1857bf2df
Spacewalk 0.7 released.