In practice they are not.
On Mon, 13 Mar 2006, Alex Moore wrote:
> To: mysql@lists.mysql.com
> From: Alex Moore <[EMAIL PROTECTED]>
> Subject: Re: mysql5 options file location
>
> On Mon, 13 Mar 2006 23:05:30 + (GMT)
> [EMAIL PROTECTED] wrote:
>
> > Exactly
On Mon, 13 Mar 2006 23:05:30 + (GMT)
[EMAIL PROTECTED] wrote:
> Exactly what are the problems you are having with the server
> specific my.cnf file?
Sorry, I thought that I had described the problem. A quick example was
'my_print_defaults mysqld' returning only the options defined in the
gl
puts them.
HTH
Keith
In theory, theory and practice are the same;
In practice they are not.
On Mon, 13 Mar 2006, Alex Moore wrote:
> To: mysql@lists.mysql.com
> From: Alex Moore <[EMAIL PROTECTED]>
> Subject: Re: mysql5 options file location
>
> On Mon, 13 Mar 2006 16:
On Mon, 13 Mar 2006 16:52:03 + (GMT)
[EMAIL PROTECTED] wrote:
>
> Hi Alex. It seems that mysqld and all the client
> programs insist on reading /etc/my.cnf first.
>
> To overide this behaviour for a particular instance of
> mysqld you need to pass the --defaults-file option as the
> FIRST
Hi Alex. It seems that mysqld and all the client
programs insist on reading /etc/my.cnf first.
To overide this behaviour for a particular instance of
mysqld you need to pass the --defaults-file option as the
FIRST parameter to mysqld_safe or mysqld if you are not using mysqld_safe.
--defaults
