gracefully shut down fastcgi backends we need to delete the events associated with the backends, otherwise the server process won't ever quit. Here, we add a pending counter to every backend and shut down immediately if they aren't handling any client; otherwise we try to close them as soon as possible (i.e. when they close the connection to the last connected client.)

reset fcgi array in free_config otherwise path, port and/or prog could become an invalid pointer.

add -D to define macros from the cmd line

sync the usage; while there also change order and capitalize

define GMID_STRING and reuse-it GMID_VERSION follows the CGI/FastCGI style, i.e. project_name/version. Define GMID_STRING with a more "human" variant "project_name version", and reuse that in the --help and --version codepath.

add version in usage

use getprogname() in usage()

use getopt_long, add --help as synonym of -h and -V/--version

allow sending fd to log on to the logger process the logger process now can receive a file descriptor to write logs to. At the moment the logic is simple, if it receives a file it logs there, otherwise it logs to syslog. This will allow to log on custom log files.

free fastcgi param list

TAILQ_REMOVE env and aliases during config_free it's not technically required, since a couple of lines below we free whole host struct, and we don't have code that may use h->{env,aliases} afterwards, but it's nice not to have invalid pointers around. it may bite in the future.

fastcgi: a first implementation Not production-ready yet, but it's a start. This adds a third ``backend'' for gmid: until now there it served local files or CGI scripts, now FastCGI applications too. FastCGI is meant to be an improvement over CGI: instead of exec'ing a script for every request, it allows to open a single connection to an ``application'' and send the requests/receive the responses over that socket using a simple binary protocol. At the moment gmid supports three different methods of opening a fastcgi connection: - local unix sockets, with: fastcgi "/path/to/sock" - network sockets, with: fastcgi tcp "host" [port] port defaults to 9000 and can be either a string or a number - subprocess, with: fastcgi spawn "/path/to/program" the fastcgi protocol is done over the executed program stdin of these, the last is only for testing and may be removed in the future. P.S.: the fastcgi rule is per-location of course :)

move pidfile & cgi to global vars

allow ``root'' rule to be specified per-location block

added ``alias'' option to define hostname aliases for a server