Bugzilla – Bug 3478
Sorcery must not stop/start init.d services automatically
Last modified: 2005-02-04 18:50:40 UTC
My suggestion in an SM-Discuss e-mail of Sat, 31 May 2003, was supported: BTW, another side of this is not attempting to start/stop a service on recast. Sorcery shouldn't do this IMO. I'm assigning this to myself. What needs to be done is: a) Code to start/stop/restart a service removed b) Sorcery must somehow notify the administrator that a restart is needed c) The spells that have a "good to start" function (like `httpd -t') must declare and use it in a standard way (maybe through an init.d script or a separate file)
I think that the start and stop is often done in the spells themselves.... PRE_REMOVE for example.... I don't think this is in the sorcery code itself? Eric
Moved to Feature Request as part of cleanup... erics
Hasn't this been done (with the possible exception of some spells which may be circumventing the Sorcery builtin init.d process)?
the only start and stopping in sorcery itself that I am aware of is the xinetd init scripts for spells... I have now coded it to ask if it should restart the xinetd deamon, up to the user. It happens before the spell builds as that is when the scripts are installed. erics
The only starting and stopping is the xinetd and this has been taken care of... the xinetd is only restarted if any scripts are installed or removed, which is required. Please verify sergey, and we can close this... erics