#1196: Service commands should use /sbin/service on Red Hat-based systems, not
/etc/init.d/foo
-------------------+--------------------------------------------------------
Reporter: init | Owner: community
Type: defect | Status: new
Priority: normal | Component: client
Version: 0.24.4 | Severity: normal
Keywords: | Stage: Unreviewed
Patch: None | Complexity: Unknown
-------------------+--------------------------------------------------------
When system services like httpd and sshd are stopped, started, etc, on a
Red Hat-based system (RHEL, CentOS, Fedora, etc), the /etc/init.d/foo
script should not be accessed directly. The proper way is to use the
/sbin/service command, since it e.g. ensures that the /etc/init.d/foo
script, and thus the service, is run in the proper SELinux context. This
does not happen if the /etc/init.d/foo script is executed directly by
puppet.
In other words, replace service management commands like this:
* /etc/init.d/foo start => /sbin/service foo start
* /etc/init.d/foo stop => /sbin/service foo stop
* /etc/init.d/foo restart => /sbin/service foo restart
* /etc/init.d/foo status => /sbin/service foo status
--
Ticket URL: <http://reductivelabs.com/trac/puppet/ticket/1196>
puppet <http://reductivelabs.com>
Puppet - Portable System Automation
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
