[Users] Problem in 3.3 with shmmax configuration

[Bob Doolittle]

Hi,

I'm setting up Engine for the 2nd time - the first time I answered a 
configuration question wrong. So I did:

engine-setup
engine-cleanup
engine-setup

Things worked, until I rebooted the system. I found that postgresql 
would not startup, and was failing with "could not create shared memory 
segment: Invalid Argument".

I resolved this issue by creating a file /etc/sysctl.d/10-shmmax.conf, 
containing the line:
kernel.shmmax = 1000000000

(I read somewhere that postgresql recommends setting shmmax to 1/4 of 
physical memory, and I have 4GB)

1. Is this a known bug? If not, should I file one? If so, how do I do 
that? :)
2. Is there a better fix than the one I settled on? Does the normal 
configuration wind up increasing shmmax, or reducing postgresql's 
limits? What are the default values for this in a normal engine 
configuration?

Thanks,
     Bob