Hello Sherwin, Yes, it's Linux. I didn't want to set LD_LIBRARY_PATH in the script that starts lighttpd because I didn't want to affect lighttpd's library path. Instead, "export LD_LIBRARY_PATH=..." was added to the script that's used to start Python. If I run the script outside lighttpd, it works fine. However, in my set up, lighttpd starts web.py app (or this script to start web.py app) and lighttpd complains that the fcgi server exits.
Thanks, > How do you start lighttpd? It sounds like you run a UNIX-like system; > Linux? What flavor? If your system uses an /etc/init.d/ script to > start the lighttpd server, then you should add a line to that script > to set the variable when the server is started up: > #!/bin/sh > export LD_LIBRARY_PATH=.... > # rest of script > Otherwise, if you start lighttpd from a different script (that > automatically starts Python for you as well), then do the same song > and dance for that script. If you start lighttpd by running the binary > (why, I can't imagine), then you should wrap that process in a shell > script and execute that. > However you do it, setting the environment variable will ensure that > the correct path is used when the interpreter starts. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
