[chef] Re: Re: Re: Re: Re: Re: Re: MySQL Cookbook

[AJ Christensen < >]

Indeed, that is why there is the restart dances / preseed / templates
/ template re-opening at specific stages.

One day I suppose we'll be able to install mysql or mariadb without
starting the service or shipping potentially broken config; it's so
hard to reverse the changes once it has started up, nuke data etc.
Yawn.

--AJ

On 27 March 2013 11:58, Jesse Campbell 
<
 >
 wrote:
> i thought the reason the template happened after install was because most
> packages include a my.cnf which would overwrite the template...
>
>
> On Tue, Mar 26, 2013 at 6:42 PM, Aaron Brown 
> <
 >
> wrote:
>>
>>
>> On Tue, Mar 26, 2013 at 5:57 PM, Steven Barre
>> <
 >
>>  wrote:
>>>
>>>
>>>
>>> I'm also trying to understand why mysql is installed, started, and then
>>> the conf file is changed then mysql restarted. Wouldn't it make more sense
>>> to have the config file set up before the first run of mysql? Things like
>>> pid file and innodb log files don't handle changing very well. (as pointed
>>> out here http://tickets.opscode.com/browse/COOK-2100)
>>>
>>
>> I have just finished committing a bunch of changes that move the template
>> creation to before the package is installed for this very reason, if you 
>> are
>> interested in reviewing:
>> https://github.com/9minutesnooze/mysql/tree/mysql56
>>
>> I will prepare a pull request in the next few days.
>>
>> Aaron
>
>