> Jesper Krogh <[email protected]> writes: > > > What: Currently a restore defaults to "yes" in the confirm dialog. > > This is suggested to change the default to "no" or better "no > > defaults" but require operator intervention. > > +1 > > > Why: In our production environment we have filesystems with > > millions of files. The step before changing restore > > parameters can be really time consuming. The current > > implementation hang on client input making it possible > > to accidentally buffer a "newline" on the input buffer, > > making the job just fly through and run. If the defaults > > "mostly" were preferrable and safe, then it wouldn't be > > problem. > > a "no" would be just as annoying (although safer), since it can take > hours(!) for Bacula to get to the point where you are prompted for > modification of these parameters. >
I would agree with this, most of the time I like to blindly hit next, but in this case, the default might be better to simply ask again (have no default). -Blake ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
