On 18-may-09, at 19:30, Antonio Ognio wrote:

>>> I'm also playing with how to generate start/stop scripts correctly
>>> taking other daemons as examples.
>>>
>>> I hope to make some more progress in the following days and share  
>>> the
>>> portfiles / patches / whatever asap.
>>
>> Great. The init script is something that we ought to commit  
>> upstream (as the
>> SMF service description file that have been shipped for months).
>
> I'll have to research into that since I don't get much of what you're
> mentioning :/
>
> I was thinking we could include a pre-configured cherokee.conf so the
> server can start inmediately without using cherokee-admin.


I don't think I get it.

The Cherokee source package includes a cherokee.conf.sample file that  
is installed as /etc/cherokee/cherokee.conf in case there isn't a  
previous configuration file already installed.

Any binary package should do the same, so the server can be launched  
right away. Or even better, as we were talking, the new HTTP service  
could be activated as soon as the server is installed.

Cherokee has been shipping a SMF file for the last couple of years.  
That's the OpenSolaris equivalent of a service definition file for  
launchd on OSX. If we had a launchd service file, it'd be good to  
commit it upstream, so people installing Cherokee from the sources on  
MacOS X can also use it easily.

--
Greetings, alo
http://www.alobbs.com/

_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to