Jan S Berg wrote: >Jyri Virkki wrote: > > >>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. >> >> >> >There are quite a few files, so having it as a separate package sounds >ok with me, >but as I think there could be some use of them it would be nice to have >them available at least. > >
if we decide to have a seperate package for mysqltest, than we can have everything under mysql-test and sql-bench directory in that package. I agree with you that since mysql-test and sql-bench directories are components of typical mysql release directory, we should also made them available..... >> >> >> >>>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 default location can be used or changed also via the config file. > > >>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. >> >> >> >You can also start the MySQL server without smf. You could always use >the config file >to change the options for the server as well, but as MySQL has quite a >few configuration options >(and in many cases you need in-fact to do quite some changes to make it >run good for your application) >so I think users also want to access the MySQL server directly with the >comand line options > > >>That leads to the question whether there is any command line option >>without config file equivalent? >> >> >> >No > > >>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. >> >> >> >> >> >The ARC case has been updated with the smf interfaces, are they sufficient? >(the interfaces are: > >svc:/network/mysql Committed FMRI >/lib/svc/method/mysql-svc Project Private SMF service method script >/var/svc/manifest/network/mysql.xml > Project Private SMF Manifest >) > >Thanks, >Jan S >_______________________________________________ >webstack-discuss mailing list >webstack-discuss at opensolaris.org >http://mail.opensolaris.org/mailman/listinfo/webstack-discuss > >
