Written by
Anonymous Coward(0)
on
Sun Sep 30 16:13:04 2007
Since you aren't spawning the fastcgi instances with lighttpd, how do you manage taking down just one of the running fastcgi processes? Do you just manually kill it?
I normally just spawn the processes from lighttpd (with the bin-path fastcgi option), but I guess that wouldn't work too well in your situation.
Re: Re: Catalyst with Lighttpd
Written by
Ash Berlin(bfc7465ebdca5337)
on
Mon Oct 1 09:11:30 2007
Each run script is the same bar the port number it listens on. I tried to find a way to have the same service directory symlinked into /service twice and have the script detect which one it was invoked as, but it seems that daemontools does not provide this info (as it follows the symlinks properly before executing the run script)
Comments on Catalyst with Lighttpd | 5 comments | Post a comment
Re: Catalyst with Lighttpd
Written by Anonymous Coward (0) on Sun Sep 30 16:13:04 2007
Since you aren't spawning the fastcgi instances with lighttpd, how do you manage taking down just one of the running fastcgi processes? Do you just manually kill it?
I normally just spawn the processes from lighttpd (with the bin-path fastcgi option), but I guess that wouldn't work too well in your situation.
[ Link | XML | YAML | Reply... ]
Re: Re: Catalyst with Lighttpd
Written by Ash Berlin (bfc7465ebdca5337)![[SIGNED]](/static/common/images/lock.png)
on
Mon Oct 1 09:11:30 2007
I use daemontools as described in the 2006 Catalyst Advent Calendar FastCGI Deployment with Bells on
Basically I have
Each
runscript is the same bar the port number it listens on. I tried to find a way to have the same service directory symlinked into/servicetwice and have the script detect which one it was invoked as, but it seems that daemontools does not provide this info (as it follows the symlinks properly before executing therunscript)Pretty straight forward from then on.
[ Parent | Link | XML | YAML | Reply... ]