Juan Eliseo Carrasco Diaz wrote: > module_loader.c/226: ERROR: > dlopen(/usr/lib/cherokee/libplugin_read_config.so): > /usr/lib/cherokee/libplugin_read_config.so: undefined symbol: > cherokee_fcgi_server_free module_loader.c/378: ERROR: Can't open > "read_config" module Couldn't read the config file > > I have tried to repair it without success :(
Damn it! It is because the changes we have made to add the FastCGI support. I will upload a fixed version as soon as possible. > I can't fix this error, so I disable tls support. I wonder if u-cherokee > can be compiled with tls support. It could? Umm.. I haven't thought of compiling u-Cherokee with TLS before. I'm gonna check it out, and I will let you know. > u-cherokee seems to work ok but it's not usable due to the default > embedded configuration. How can I set and change it? Are there some > documentation that explain this? I only have seen something about to > edit the read_config_embedded.c file to set the static > configuration. Should u-cherokee works with the dynamic > configuration? It seems that it doesn't work. Actually, it is up to you. In my opinion this is something that depends on each case. If you work with a really tiny system and you only want it to send files, the only thing you have to do in read_config_embedded.c is to set the file handler system wide. If you want to have some more complex configuration, you should modify read_config_embedded.c more heavily, either coding the configuration with the Cherokee API, or writing a little configuration reader in it. Finally, you would want to use the default configuration grammar.. it is quite big though, so it first look it doesn't seem to be the best choice of an embedded system. In this case, it doesn't make much sense for me to use u-Cherokee instead the default Cherokee version. By the way, the default version loads the configuration parser dynamically, and when the server is properly configured, it frees all the memory (including the parsers code!) used by it. About the documentation. There is no documentation on this topic yet. I would like to write down something about it, but I haven't had time. (If you are planning to do the research to work with it, any kind of help [1] is more than welcome!!) :-) [1] http://www.0x50.org/wiki/ -- Greetings, alo. http://www.alobbs.com _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
