Red Hat Bugzilla – Bug 480342
No startup scripts should be in /etc/init.d, all should go to /etc/rc.d/init.d
Last modified: 2009-12-07 07:02:42 EST
Description of problem:
Fedora Packaging says on their page
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
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):
Steps to Reproduce:
1. rpm -ql osad osa-dispatcher spacewalk-search spacewalk-taskomatic | grep '/etc.*/init\.d/'
rhn-search fixed in commit 2c121b5a170763fb86afa902159a59a1857bf2df
Spacewalk 0.7 released.