Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Manish Sinha (manishsinha.techgmail.com)
Date: Tue Dec 30 2008 - 13:57:58 CST
> in a *nix environment, restarting the mysql server is done with a
> system-level command and requires *system* root privileges, not
> something that the average db-admin is likely to have. also,
> changing the port a service is listening on has potentially serious
> implications as you have to understand what (other) services are
> assigned to, and potentially listening on, which ports, again,
> generally beyond the knowledge level of the average db-admin.
> what are you trying to accomplish with this capability? except for a
> few very limited reasons (e.g., running multiple mysql instances)
> there really isn't a valid reason to change the port a mysql
> instance is listening on in the first place.
I can understand the point. I have used MySQL for two years and can
understand mostly all of the options in the config file and its the only
DB software I have put all my effort into. I have a good and sound
understanding of MySQL.
I can understand that management requires root priviliges, so my app
would run as root itself. I even understand that its not required, but
this is the only thing which I was unable to achieve via my app since I
don't want to read and change the my.cnf file itself. Any mistake could
cost more than expected. Additionally parsing that file to get the port
no can be problematic since there are two instances of
port = 3306
one of client and other for the server. By mistake I can change the
wrong one if not taken care of.
I can understand the security issues but I am actually trying to make an
app which can administrate MySQL and would later add a GUI over it.
Personal Blog: http://www.manishsinha.info
Tech Blog: http://manishtech.wordpress.com
OpenPGP Key: 99E6658F
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql