On 9.4.2011, at 1.01, Nick VonHollen wrote: > When I converted the config file, I somehow set vsz_limit to 1k. The child > process tries to load its core libraries, runs out of virtual memory, and is > killed. > > We have a lot of limits set in the config file, and I've seen warnings for > other limits, but not this one. > > Hopefully, someone else sees this and doesn't do the same thing. Would it > make sense to raise some warnings for the vsz_limit itself? At least for > some insanely low number like <= 1M?
There is such a warning! Unfortunately it's for numbers under 1 kB :) Yeah, I guess it could be safely increased quite a lot.
