On Fri, Jun 09, 2006 at 12:35:15AM +0200, Christian Hammers wrote: > tags 371842 + moreinfo > thanks > > Hello Nathan > > On 2006-06-07 Nathan A. Ferch wrote: > > /usr/bin/mysql_upgrade, which is called out of /etc/mysql/debian-start, > > fails to look the /etc/mysql/debian.cnf file for socket or port > > information, and thusly fails. > > > > included patch modifies mysql_upgrade to check /etc/mysql/debian.cnf for > > 'port' and/or 'socket' statements. > Although it is right that mysql_upgrade better should accept these > parameters, when calling from debian-start it can only get the values > from /etc/mysql/debian.cnf so I'm wondering in which case you encountered > a problem here? > > Do you start debian-start for a server that is not on localhost? Or > did you rename the socket and if so, why?
i'm running another instance of mysql on port 3306 and on the standard socket of /var/run/mysqld/mysql.sock, so I need the debian mysql running on a different socket and port. before 5.0.20a-2 i was able to place this information in debian.cnf so that the init script was able to connect to the correct mysqld instance. my debian.cnf looks something like this: [client] host = localhost user = debian-sys-maint password = -removed- socket = /var/run/mysqld/mysqld4.sock port = 3307 [mysql_upgrade] host = localhost user = debian-sys-maint password = -removed- socket = /var/run/mysqld/mysqld4.sock port = 3307 -- nathan a ferch [EMAIL PROTECTED] "Ray, as your friend I have to tell you I think you've really gone around the bend on this ghost stuff. You've been running your ass off for two years checking out every schizo in the Five Boroughs who thinks he's had an experience. And what have you seen?" -Venkman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
