Issue #1809 has been updated by lutter.
We can either fix that by patching upstream when we build the RHEL4 tarball, or keep a different init script in puppet's git for RHEL4 .. any preferences ? For client.init, the fix is obvious: remove the -p from the status command, thus breaking #1646 on RHEL4. For server.init, there shouldn't be an issue unless you use the multi-mongrel setup; in that case, I don't see a way to make this work on RHEL4. It would really require a separate init script for each mongrel instance. ---------------------------------------- Bug #1809: "status -p" in init scripts not available before Red Hat Server 5 http://projects.reductivelabs.com/issues/show/1809 Author: stevev Status: Accepted Priority: Normal Assigned to: lutter Category: Red Hat Target version: unplanned Complexity: Unknown Affected version: 0.24.6 Keywords: conf/redhat/client.init and conf/redhat/server.init use "status -p pidfile" in their "status" method, which is available in Red Hat Server 5 but not earlier Red Hat versions. "status -p pidfile" fails on Red Hat 4 and earlier in such a way that the init script always thinks puppetd is not running. 0.24.5 simply used "status $puppetd" which seemed to work, although maybe it had other problems. ---------------------------------------- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
