Walter, Le 16 janv. 2012 à 12:23, Walter Heck a écrit : > On Mon, Jan 16, 2012 at 20:26, Daniel Nichter <[email protected]> wrote: >> My one big question concerns the reasoning in item #13: should plugins be >> "all on" by default, or "all off" requiring the user to turn on what they >> want? I tend to think "all on" because most plugins only do one thing so if >> the user adds it, they want it to be working now. The argument for "all >> off" is in cases like syslog which do multiple things, or perhaps query_log >> which, if configured badly, may come on and start hammering the disk. I >> think the 95% case is "all on". What do you think? > > Couldn't it be done much like certain packages in debian? The package > is in full configged shape, but you have to set a param in > /etc/default/$pkgname to from disabled to enabled in order for it to > actually work when started. If you leave it at disabled, you will get > a message when you invoke the /etc/init.d/$pkgname script. > That allows the developer to roll the package out with a sane > configuration, but the user won't be surprised with new functionality > without taking actual manual action.
That's a good idea. Henrik has mentioned something similar to me: requiring that each plugin provide a config file for itself. So query_log would come with query_log.cnf which contains some default/sane configuration. This plus your suggestion would be "off but configured". However, I'm not sure how well that will work for most plugins where this is an issue because most plugins require a specific config for which there is no determinable default. For example, all the auth_* plugins, all replication-related plugins, and even query_log is rather useless without a specific config for threshold_execution_time. So perhaps I'm rendering my own question moot and rather we should focus on items 10, 11, and 15 of https://blueprints.launchpad.net/drizzle/+spec/plugin-standards which, if implemented, would make it so that if you --plugin-add=X you get X but it may not be working because it's not configured, but you can configure it dynamically. I'll look at all the plugins and see for which of them this is really an issue. For example, it's a non-issue for all functions and table functions. -Daniel _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
