Bug 97650
Summary: | chkconfig --add does not work as advertised | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Joseph Tate <jtate> |
Component: | mailman | Assignee: | John Dennis <jdennis> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-19 16:22:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joseph Tate
2003-06-18 20:10:25 UTC
This is deliberate behavior, it is Red Hat policy that you as a user must enable a service, RPM's do not automatically start services upon installation. Perhaps you may have missed the documentation in: /usr/share/doc/mailman-*/INSTALL.REDHAT I've included the relevant excerpt below. - Start the Mailman qrunner daemon As of mailman version 2.1 mailman requires a service (daemon) to be run for mailman to operate. RedHat does not ship RPM's that enable services as part of package installation. You will need to enable the mailman service if you want mailman to run. To enable the mailman service after package installation you may run the "serviceconf" GUI tool, or you may do the following on the command line as root. /sbin/service mailman start To have the mailman service automatically start at certain run levels (replace the runlevel below with your desired run levels, for example to start mailman at run levels 3 and 5 runlevel would be 35: /sbin/chkconfig --level runlevel mailman on The /etc/init.d/mailman script states: # On RedHat, and derivatives, install with "chkconfig --add mailman" # # chkconfig: - 98 12 # description: Mailman is the GNU Mailing List Manager, a program that \ # manages electronic mail discussion groups. For more \ # on GNU Mailman see http://www.list.org # processname: mailmanctl # config: /var/mailman/Mailman/mm_cfg.py # pidfile: /var/mailman/data/qrunner.pid When I run chkconfig --add mailman, then chkconfig --list mailman, it's off for all run levels. This is the case on two of my RH 9 systems. Either fix it so that chkconfig --add works, or change the blurb to say chkconfig --levels 345 mailman on. All you'd have to do is change the line from # chkconfig: - 98 12 to # chkconfig: 345 98 12 After the command "chkconfig --add mailman" it should be off for all levels. BTW, the spec file does this so you don't need to do this manually. The "add" verb does not turn services on at init time, therefore after performing an "add" the fact that --list then says its off is the desired behavior. All that "add" does is inform the init system of a new service init script. It does not enable or turn on the service. It is Red Hat policy that you must manually turn on the service at your desired run levels. Therefore you must issue the "chkconfig --runlevel X mailman on" command to turn on mailman at init time. Perhaps I've misunderstood the problem you are stating, after you've read my explanation do you still believe the behavior is wrong? If so please let me know why and I'll try to fix it for you. Ok, then that was my misunderstanding. chkconfig --add iptables adds the service to run levels 2345, but I notice now that httpd doesn't work that way. |