On Tue, Mar 9, 2010 at 12:44 PM, Gregory Smith <[email protected]> wrote: > Raise the ulimit that the scheduler runs under. Some of the autoserv > processes it launches more ram (for brief periods of time) due to large > external processes they launch.
Two questions: 1. Should this just be done for the child autoservs? 2. What are the large processes? If they're only your internal ones, then this would be better done in a site-specific override, or as a global config option? > Signed-off-by: Gregory Smith <[email protected]> > > --- autotest/utils/autotest.init 2010-03-09 12:26:49.000000000 -0800 > +++ autotest/utils/autotest.init 2010-03-09 12:26:49.000000000 -0800 > @@ -31,7 +31,7 @@ > ## END GOOGLE > > log_daemon_msg "Starting monitor_db_babysitter" > - ( ulimit -v 819200 ; \ > + ( ulimit -v 2048000 ; \ > start-stop-daemon --start --quiet --chuid $BECOME_USER \ > --background --exec $BASE_DIR/scheduler/monitor_db_babysitter ) > } > _______________________________________________ > Autotest mailing list > [email protected] > http://test.kernel.org/cgi-bin/mailman/listinfo/autotest > _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
