[bug-notifications] [cswclassutils 0003635]: Support service that can't be autoenabled at first install

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://www.opencsw.org/mantis/view.php?id=3635 
====================================================================== 
Reported By:                yann
Assigned To:                bonivart
====================================================================== 
Project:                    cswclassutils
Issue ID:                   3635
Category:                   regular use
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2009-04-13 19:59 CEST
Last Modified:              2009-04-21 17:17 CEST
====================================================================== 
Summary:                    Support service that can't be autoenabled at first
install
Description: 
Some daemons can't be launched at all at first install without a bit of
manual configuration, that the case of imapproxy which require an imap
server to be given in imapproxy configuration file.

Currently, cswclassutils cswinitsmf will always tries to start the daemon
if autoenable_daemons=yes, for cswimapproxy this would result in a service
in maintenance state that would need to be cleared.

It would be nice to have support for this case, the service can't be
launched at first install, but once it is configured and enabled by the
administrator, it has to be re-launched at each upgrade.
====================================================================== 

---------------------------------------------------------------------- 
 (0005991) bonivart (manager) - 2009-04-21 17:17
 http://www.opencsw.org/mantis/view.php?id=3635#c5991 
---------------------------------------------------------------------- 
Isn't this normally handled by the start script? Something like:

[ -f someconffile ] && startservice 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-13 19:59 yann           New Issue                                    
2009-04-21 17:15 bonivart       Status                   new => assigned     
2009-04-21 17:15 bonivart       Assigned To               => bonivart        
2009-04-21 17:17 bonivart       Note Added: 0005991                          
======================================================================