Hi, here are know the first steps for a better integration with nginx (http://nginx.net/) and lighty (http://www.lighttpd.net/). They are able to connect to fast-cgi (fcgi) backends and the fcgi can behave like a apache with mod_perl ;-) The files are: index_new.fpl => the starting point it forks 5 (n_processes), write a pidfile (pid_fname). In this file depending on the request uri ($ENV{'REQUEST_URI'}) the different interfaces will be called. fcgi-startup.pl => is mainly a copy from apache2-httpd-new.include.conf otrs-2.2.4.diff => I have changed some small parts in the otrs System an this are the diffs. otrs.nginx.conf => nginx configfile. Please pay attention that the socket (fastcgi_pass && FCGI_SOCKET_PATH) is rw for both users (otrs && nginx). TODOs: I have only tested it with a small setup. Better and bigger testing. Documentation. start/stop script. I try to decide which process managment system to us, please can somebody help to find a 'good' way which you can go. POE::Component::Pool::Thread (http://search.cpan.org/~tag/POE-Component-Pool-Thread-0.015/Thread.pm) PTools::Proc::NWay http://search.cpan.org/~ccobb/PTools-Proc-NWay-0.09/lib/PTools/Proc/NWay.pm Daemon::Generic http://search.cpan.org/~muir/Daemon-Generic-0.51/lib/Daemon/Generic.pod Generic POE solution e.g. http://poe.perl.org/?POE_Cookbook/Web_Server_With_Forking DJB's Daemontools http://cr.yp.to/daemontools.html Other Ideas ;-) Please tell me what you think and if this is the way otrs is able to go ;-) Thanks & greetings Aleks