+++ This bug was initially created as a clone of Bug #508213 +++ (applies to rawhide too accordingly bug #522041) Description of problem: When an initscript contains a 'Required-Start:' tag, install_initd fails silently with exit code 1. E.g. /etc/init.d/foo contains --- #! /bin/sh # ### BEGIN INIT INFO # Provides: foo # Short-Description: foo # Description: foo # Required-Start: $network ### END INIT INFO # # chkconfig: - 99 1 --- Then # /usr/lib/lsb/install_initd /etc/init.d/foo ; echo $? 1 and links are not created. Version-Release number of selected component (if applicable): redhat-lsb-3.2-3.fc11.x86_64 chkconfig-1.3.42-1.x86_64 How reproducible: 100% --- Additional comment from enrico.scholz.de on 2009-07-19 04:10:05 EDT --- *** Bug 512547 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I saw this issue while updating RHEL 5.4 on a x86 system with EPEL installed. Updating the tor-lsb package from EPEL triggered it. My packages are (now): redhat-lsb-3.1-12.3.EL.i386 chkconfig-1.3.30.1-2.i386 I'm not sure if I can report this against RHEL since I am on a 30-day evaluation number, and I don't even know for sure if I'm supposed to.
(In reply to comment #2) > I'm not sure if I can report this against RHEL since I am on a 30-day > evaluation number, and I don't even know for sure if I'm supposed to. Feel free to file bug but note that it the bug is in tor-* package, then it's not a RHEL issue but EPEL, which is Fedora project, because tor is not in RHEL, IMHO.
Bug is in redhat-lsb, tor triggers it only.
I was pointed to this bug report by upgrade.log (installation from F11 to F12 via preupgrade): > Upgrading tor-lsb-0.2.1.19-2.fc12.noarch > oouch... redhat-lsb is still broken. See the report > https://bugzilla.redhat.com/show_bug.cgi?id=522053 > for details. Not sure if that's any useful information but I wanted to point it out before I delete upgrade.log.
This works for me fine in F-13. *** This bug has been marked as a duplicate of bug 474223 ***
Though this bug has been fixed, tor may still point you to this page due to a yum bug. I had redhat-lsb.i586-4.0-4.fc11 on my system and yum didn't bother upgrading me to redhat-lsb.i686-4.0-2.fc13 because it thought 4.0-4.fc11 was newer than 4.0-2.fc13. Use the command "yum list redhat-lsb" to make sure you are actually running the current version.