From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: Unattended mongo benchmark? Date: Fri, 30 Jul 2004 22:19:38 -0700 Message-ID: <410B2BEA.6090508@namesys.com> References: <20040730204212.19E6015E7C@mail03.powweb.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <20040730204212.19E6015E7C@mail03.powweb.com> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: David Dabbs Cc: reiserfs-list@namesys.com David Dabbs wrote: >I was wondering about a solution to running mongo benchmarks unattended. >If one does not exist, how about the following as a 'straw man' approach? > >Create a script (say mongo_auto.sh) that takes one numeric parameter. The >parameter would indicate which action/mongo script to perform next. The >parameters and their associated actions might be something like the >following: > >Parameter: N=0 >- Make a copy of /etc/inittab >- Add a 'sysinit' entry in /etc/inittab that runs "/path/mongo_auto.sh 1" >- Reboot > > >Parameter: N >- Run the Nth mongo run (specified in a case statement in mongo_auto.sh)0. >- If (ran_without_error) > N = N + 1 > if ( N <= Last_Run_Number) > - Update /etc/inittab entry to run "/path/mongo_auto.sh N" > - Reboot > else > - Clean up/restore /etc/inittab > - Run /path/to/mongo_parse.sh 1.log 2.log... > comparison.html > > >Or, to limit inittab mods to the start/end, the script could read/write a >.mongo_auto file that specifies the next run number to take. > > >David > > > > > > > sounds good.