utilities » spawn-fcgi

i love this patch.

this is crap to cd in the directory before calling spawn-fcgi !!! A binary must be started anywhere and the -d option allows you to do that

icy wrote:

Err, why don't you just cd to the directory before calling spawn-fcgi?

This is not intuitive, because it behaves differently from when the fastcgi daemon is automatically spawned by lighttpd:

• before, I was telling lighttpd to launch the fastcgi daemon automatically, everything was working fine

• then, I began using spawn-fcgi to launch the fastcgi daemon, but it was no longer finding the files it needed

That's why I made this quick patch to have a consistent behavior between the 2 methods of launching the fastcgi daemon.

raphaelh wrote:

This is not intuitive, because it behaves differently from when the fastcgi daemon is automatically spawned by lighttpd:

That's probably because relative paths are used somewhere. Why not use absolute paths?

Olaf-van-der-Spek wrote:

raphaelh wrote:

This is not intuitive, because it behaves differently from when the fastcgi daemon is automatically spawned by lighttpd:

That's probably because relative paths are used somewhere. Why not use absolute paths?

Well yeah, I could just cd before spawning, or use absolute paths

and anyway I use the small patch on my lighttpd, so it's not a problem for me...

But I was just saying that it could save some time for other people when switching from lighttpd autospawn to spawn-fcgi, as this patch was helpful for me I wanted to share :)

raphaelh wrote:

and anyway I use the small patch on my lighttpd, so it's not a problem for me...

I still have no idea what the advantage of this patch over a 'manual' cd is...

icy wrote:

Well, at least it doesn't hurt and some people might find it convenient.

It does increase complexity of code and parameters. That's not a positive thing. ;)

If you want to spawn an application in a chroot and want a specific current directory before spawning, a wrapper script is a little bit overkill (and don't forget you would have to add the interpreter to the chroot...).
And as this option looks easy i just added it :)