Hello Phil, I can see that this would be useful, but on the other hand, I worry that it would break users scripts.
Does anyone else have any comments? Kern On Friday 09 November 2007 13:51, Phil Stracchino wrote: > Just a quick suggestion before we shut down to move. > > Currently, when running a job from the console, the process goes > something like this: > > run > [select job number] > OK to run yes/mod/no? > > If I want to change the level, pool, and priority, I must now do this: > > m > 1 > [select level] > OK to run y/m/n? > m > 7 > [select new priority] > OK to run y/m/n? > 8 > [select pool] > OK to run y/m/n? > > > Since when running a console job, there will seldom be only ONE > parameter I want to alter, I suggest the following change: Add one more > item to the job parameters list, perhaps 0 at the top, for "finished > with changes, ready to run", and stay in the change menu until that is > selected. The above then becomes: > > m > 1 > [select level] > 7 > [select priority] > 8 > [select pool] > 0 > OK to run (yes/mod/no)? > > > It's a much shorter and more efficient process. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
