goose's questions

Take the following internal round robin dns setup

mymta.com. IN A 172.31.1.1
mymta.com. IN A 172.31.1.2
mymta.com. IN A 172.31.1.3
mymta.com. IN A 172.31.1.4
mymta.com. IN A 172.31.1.5
mymta.com. IN A 172.31.1.6
mymta.com. IN A 172.31.1.7
mymta.com. IN A 172.31.1.8
mymta.com. IN A 172.31.1.9
mymta.com. IN A 172.31.1.10

Now assume the following postfix setup (assume these are the only tweaks from defaults in debian package)

main.cf:

smtp_connection_cache_destinations = mymta.com
smtp_connection_cache_reuse_limit = 750
smtp_destination_concurrency_limit = 75

transport

* :[mymta.com]

I would expect 75 concurrent connections spread across the 10 A records I've set in DNS. However I'm seeing more than a few hundred connections to mymta.com and I'm wondering if Postfix is "smart" enough to set up 75 concurrent connections for each IP address.

Thoughts?

Currently I have a redundant pfSense firewall system set up for our corporate server farm. The main router IPs are sharing an IP address through Carp. Our two public /27 networks are assigned as proxy arp addresses to the wan interfaces and are routed to the shared Carp address.

IE: 
public carp: 10.10.10.10
firewall 1: 10.10.10.11
firewall 2: 10.10.10.12
network 172.31.1.0/27 routed to 10.10.10.10 
   (proxy arp network assigned to WAN in firewall)
network 172.31.2.0/27 routed to 10.10.10.10
   (proxy arp network assigned to WAN in firewall)

My question is, would it be a better practice to use Carp for those /27 networks? I'm reading a decent amount of warnings that proxy arps can screw up traffic.

My redundancy lies in the firewall, so I dont think that Carp is necessary for the other networks. Any advice that is out there would be helpful?

I have a need to analyze logs generated by Apache2 webserver. I'm considering either piping the log to a script that will just wait on the stdin for input, or analyzing the logs nightly with a batch job.

One of my requirements involve writing some of the information to a database (ie, execution time, size, URI, remote IP). For that reason I'm apprehensive about piping to a script and keeping a database connection open. So I'm leaning towards a nightly analysis.

Anyone using a setup like this in a production environment or have any thoughts?