[bug-notifications] [mysql5 0004646]: /var/opt/csw/mysql5/my.cnf ignored

[Mantis Bug Tracker]

The following issue has been ASSIGNED. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4646 
====================================================================== 
Reported By:                james
Assigned To:                laurent
====================================================================== 
Project:                    mysql5
Issue ID:                   4646
Category:                   other
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2010-12-22 13:49 CET
Last Modified:              2013-06-09 15:55 CEST
====================================================================== 
Summary:                    /var/opt/csw/mysql5/my.cnf ignored
Description: 
The start up script:
/var/opt/csw/svc/method/svc-cswmysql5
has provision to use a local configuration:
MYSQL_VAR=/var/opt/csw/mysql5
CONFFILE=$MYSQL_VAR/my.cnf

but it fails:

WARNING: Found two instances of my.cnf -
/opt/csw/mysql5/my.cnf and
/var/opt/csw/mysql5/my.cnf
IGNORING /var/opt/csw/mysql5/my.cnf

If I can't write to /opt this is a problem and if I can then I'm wasting my
time in /var/opt anyway.



====================================================================== 

---------------------------------------------------------------------- 
 (0008667) phil (reporter) - 2011-01-04 23:31
 https://www.opencsw.org/mantis/view.php?id=4646#c8667 
---------------------------------------------------------------------- 
Ah sorry. I was reading the wrong file. my "patch" was for mysqld_safe, not
our init file.


I think we would be best to focus on patching mysqld_safe, and keeping the
init file as minimal as possible.
I say that, because mysqld_safe is quite complex.  Usually, for maintanance
purposes, its a good idea to minimise complexity whereever possible.

Having large complexity in TWO areas of the chain for startup, I would
suggest is counterproductive for us. 

---------------------------------------------------------------------- 
 (0008668) maciej (developer) - 2011-01-05 01:00
 https://www.opencsw.org/mantis/view.php?id=4646#c8668 
---------------------------------------------------------------------- 
The problem with patching mysqld_safe is that it changes the documented way
MySQL startup works.  Imagine someone trying to debug a problem that is
related to these settings.  They will probably read MySQL documentation[1]
and examine our startup script.  If we patch mysqld_safe, they will find no
indication that we're changing the default behavior.  They might spend a
lot of time debugging, until they discover that we've modified mysqld_safe.
 Don't you think it might be a problem?

[1] http://dev.mysql.com/doc/refman/5.0/en/option-files.html