search for: some_ports

...to do this Expected -- define would either be a straight textual substitution, or would be able to accept a notation appropriate for defining sets, maps, and the like that need to be consistent across multiple uses in rule sets The following fail, in various ways when trying to use elements = { $some_ports } * define some_ports = { 80, 443 } * define some_ports = 80, 443 * define some_ports = http, https * define some_ports = 80 * define some_ports = "{ 80, 443 }" fails when trying to use elements = $some_ports * define no_ports = { } fails, as does directly using * elements = { } Ag...

Hi All, I have a question about Fastagi because I can't get it to work for some reason. Everytime I execute the fastagi command, i get an error: my extensions.conf: .. exten => 1000,1,agi(agi://some_ip_address) .. output from asterisk console: -- Executing AGI("Zap/1-1", "agi://some_ip_address") in new stack -- Launched AGI Script

Our Mephisto install kills Mongrels and causes Apache to pound the CPU. This started when we moved to Apache+mod_proxy_balancer+Mongrel. Here''s what we know: The following things are working OK, except when used in the combination listed above: mongrel, mongrel_rails, MySQL, Apache, mod_proxy_balancer. We believe these are all OK because we moved five other Rails apps to this

I have an Apache 2.2.3 (mod_proxy_balancer) frontend server that does not have mongrel installed. It does proxy requests to several other mongrel-only servers (each running 2 mongrel processes). Each mongrel node has the same rails code-base and it''s working perfectly. However, my question is when I add an upload file form... where is it going to physically put that file? I mean since