I could generate a second /bin/sh script to run "ruby .../webrick.rb" This would assume that 'ruby' was in the user's $PATH, but that seems like a reasonable expectation. The drawback is that we'd be generating TWO scripts, one ruby script to invoke the server, and one shell script to run the ruby script. This seems a little ... circuitous. Another idea is to hack the $httpd variable to contain a command string like "ruby .../webrick.rb", with the drawback then being a lack of obviousness, since the convention is that the variable contains the same command as the --httpd argument, and is named the same as the <webserver>_conf() functions. On 9/17/07, Florian Weimer <fweimer@xxxxxx> wrote: > * Thomas Adam: > > > This is what /usr/bin/env is useful for, but it's not that portable. > > Yeah, it's /bin/env exclusively on some systems. 8-( > > -- > Florian Weimer <fweimer@xxxxxx> > BFK edv-consulting GmbH http://www.bfk.de/ > Kriegsstraße 100 tel: +49-721-96201-1 > D-76133 Karlsruhe fax: +49-721-96201-99 > -- mike dalessio mike@xxxxxxx - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
