OK ...
So I had a mini-revelation about how to do max unshared RAM
for Apache::SizeLimit ... couldn't you register a
child_init handler that calculated the processes size
post fork, then the unshared size would be
UNSHARED_SIZE = CURRENT_SIZE - CHILD_INIT_SIZE
Voila!
OK, so what happen if other things happen in ChildInit
phase that bloat your process, like an Apache::DBI connect,
before your Apache::SizeLimit can try to calculate
current size? I guess you just have to make sure it
runs first, is this too hard from Apache::SizeLimit's
perspective?
-- Josh
