On Tue, Mar 9, 2010 at 5:51 PM, Martin Bligh <[email protected]> wrote: > 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?
This being a shell script, it is harder to extract values from the global config file (to a point it's not worth picking up values from the file). A site specific override would be OK, but need to verify first if this is not beneficial to upstream. I just took the time and read the script, it makes use of log_daemon_msg, which is a utility commonly present in debian boxes, I guess we should make an effort to make this a bit more distro agnostic... >> 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 > -- Lucas _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
