Ritu Kamboj wrote: > > The mysql-test directory exist in a typical MySQL release area. > > I would recommend that we merge the contents of mysql-test to > SUNWmysql5usr package.
I'm still curious to know how commonly (if ever) end users need the test suite? What are the use cases? If sometimes (or more often), combining into SUNWmysql5u package sounds good. If hardly ever, maybe a separate package is better so it can be removed by those who don't need it. If never.. don't package it. Also, how much content is there? That should also influence your decision. If it's only a few executables, doesn't make that much difference. If it is thousands of rarely-used files, a separate package starts looking better. > The user just needs to change the data directory in SMF manifest (if he > is using a different data directory than default) ...and SMF will work fine. To confirm, if it is the default location no change is needed? The properties are set via svccfg. > All the other configuration will be read from the configuration file. > > Not sure if that answers SMF related question. My question was about the exported interface entry for server binary. If that refers to command line options (output of 'mysqld --verbose --help') how would a user access these starting via smf? Or you'll just document to use the config files only? In which case the command line options are not exported interfaces as there isn't any way to access them. That leads to the question whether there is any command line option without config file equivalent? The other detail was to list the smf interfaces in the exported table. (Service name, property names). See the recent apache case for some examples in this space. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
