 Relationships |
|
| Anonymous | Login | 2024-04-26 11:56 CEST |
| Main | My View | View Issues |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0003633 | [cswclassutils] regular use | minor | have not tried | 2009-04-13 18:23 | 2009-07-01 11:02 | ||
| Reporter | yann | View Status | public | ||||
| Assigned To | bonivart | ||||||
| Priority | normal | Resolution | no change required | ||||
| Status | closed | ||||||
| Summary | 0003633: Service using init scripts should not be configured to at boot time when autoenable_daemons=no | ||||||
| Description |
Hi, It seems cswinitsmf class doesn't perfectly respect the opencsw standard. According to the standard when autoenable_daemons=no, the install scripts whould "skip enabling the demon to run at boot time" [1], that doesn't seem to be the case currently with init scripts, rc links are setup whatever the autoenable setting. I had this bug with the dovecot package, at the first reboot dovecot was launched despite autoenable_daemons being set to no. [1] http://www.opencsw.org/standards/csw.conf [^] |
||||||
| Additional Information | |||||||
| Tags | No tags attached. | ||||||
| Attached Files | |||||||
|
|
|||||||
|
Relationships |
|
|
Notes |
|
|
(0005990) bonivart (developer) 2009-04-21 17:13 |
I have a fix for this in 1.6. Thanks for reporting it. |
|
(0006260) bonivart (developer) 2009-06-04 10:51 |
Confirmed to work by Mike Watters. Closing. |
|
(0006261) bonivart (developer) 2009-06-04 10:52 |
Fix in 1.16 released today. |
|
(0006363) yann (developer) 2009-06-30 00:00 |
Hi Peter, I would like to reopen this bug because I am not quite sure what I asked in the original report was standard compliant. According to the standard, if autoenable_daemons=no, postinstall script should skip enabling the demon to run at boot time. Right now cswclassutils doesn't install the rc links if autoenable_daemons=no so it should be right. However according to the same standard, it is suggested that init script rely on configuration script presence to know whether or not they should start the daemon, if the service doesn't provide its own way to enable/disable it, which is usually the case. This configuration file creation mecanism allow to enable/disable the daemon at boot time: "That way, the user has the option to manually create the config file later on, and thus "manually" enable the demon at boot time (as opposed to "autoenable")." Reading that, if autoenable_daemons=no, I would think I just have to create the configuration file to enable the daemon at boot time but that would not be the case as cswclassutils doesn't create the rc links. I am not sure I understand well this standard. What's your understand on this ? |
|
(0006364) bonivart (developer) 2009-06-30 09:29 |
I think the rc-mechanism is too simple to make this perfect for everyone. The rc-part of cswinitsmf is legacy and we will have to make a choice best suited for most people. Not all init scripts check the presence of config files so if rc-links were to be set up always they would fail in various ways. I think it's cleaner this way. And it should only affect those who have made a choice to use autoenable_daemons=no. To me it's OK but maybe it should be discussed on the maintainers list, the csw.conf page may need to be reworded slightly or something. Take it to the list if you want it further discussed. If you do I'll keep this bug open and fix it the way the list decides. |
|
(0006365) yann (developer) 2009-06-30 09:48 |
I also prefer the way it is handled by cswclassutils. It just lacks a simple tool to easily recreate the symlinks (but maybe I missed it) but this way is cleaner. |
|
(0006372) bonivart (developer) 2009-07-01 11:02 |
Closing again, to change this we need to discuss it on the maintainers list first. |
| Copyright © 2000 - 2008 Mantis Group |  |
