--- author: email: ash@firemirror.com keyid: bfc7465ebdca5337 name: Ash Berlin categories: [] date: 2007-10-01T08:11:30Z guid: EAB847AE-6FF5-11DC-AAA7-B7CF8A320E61 modified: 2007-10-01T08:11:30Z raw: "-----BEGIN PGP SIGNED MESSAGE-----\r\nHash: SHA1\r\n\r\nI use daemontools as described in the 2006 Catalyst Advent Calendar [FastCGI Deployment with Bells on][day4]\r\n\r\nBasically I have\r\n\r\n lang:bash\r\n /service/myapp-fcgi1\r\n /service/myapp-fcgi2\r\n\r\nEach `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)\r\n\r\nPretty straight forward from then on.\r\n\r\n[day4]: http://www.catalystframework.org/calendar/2006/4\r\n-----BEGIN PGP SIGNATURE-----\r\nVersion: GnuPG v1.4.7 (Darwin)\r\n\r\niD8DBQFHAKtuv8dGXr3KUzcRAp1yAJ9BfRcDO1jIwdYy7MkkBzcmnrooxQCcDfRi\r\ncufzklQdedPSbnPw35sP48s=\r\n=ehLU\r\n-----END PGP SIGNATURE-----\n" signed: 1 summary: " I use daemontools as described in the 2006 Catalyst …" tags: [] text: "\nI use daemontools as described in the 2006 Catalyst Advent Calendar\nFastCGI Deployment with Bells on [1]\n\nBasically I have\n\nEach run script is the same bar the port number it listens on. I tried\nto find a way to have the same service directory symlinked into /service\ntwice and have the script detect which one it was invoked as, but it\nseems that daemontools does not provide this info (as it follows the\nsymlinks properly before executing the run script)\n\nPretty straight forward from then on.\n\n-- \n [1] http://www.catalystframework.org/calendar/2006/4\n" title: "Re: Re: Catalyst with Lighttpd" type: markdown uri: http://perlitist.com/comments/E6ABD362-6EB3-11DC-8EA1-D6A1BB7FECD7/A4A95C28-6F67-11DC-AD2E-FCF13CDAA5CE/EAB847AE-6FF5-11DC-AAA7-B7CF8A320E61 xhtml: "

I use daemontools as described in the 2006 Catalyst Advent Calendar FastCGI Deployment with Bells on

Basically I have

/service/myapp-fcgi1\n/service/myapp-fcgi2\n

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)

Pretty straight forward from then on.

" --- author: email: '' keyid: 0 name: Anonymous Coward categories: [] date: 2007-09-30T15:13:04Z guid: A4A95C28-6F67-11DC-AD2E-FCF13CDAA5CE modified: 2007-09-30T15:13:04Z raw: "

\r\nSince 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?\r\n

\r\n

\r\nI 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.\r\n

\n" signed: 0 summary: " Since you aren't spawning the fastcgi instances with lighttpd, …" tags: [] text: "\n 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? \n\n 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. \n" title: "Re: Catalyst with Lighttpd" type: html uri: http://perlitist.com/comments/E6ABD362-6EB3-11DC-8EA1-D6A1BB7FECD7/A4A95C28-6F67-11DC-AD2E-FCF13CDAA5CE xhtml:

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.