Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Repair PHP/MySQL connections in 10.4.4' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Repair PHP/MySQL connections in 10.4.4
Authored by: sjk on Jan 15, '06 12:48:54AM
Are there good reasons to continue using /tmp/mysql.sock instead of /var/mysql/mysql.sock after reading this hint and knowing now that the former is less secure than the latter? Seems to me that's undoing Apple's intended fix in 10.4.4 (Server):

Mac OS X Server 10.4.4: Improvements to Apache/PHP/MySQL interaction

... and also the /usr/libexec/httpd/libphp4.so update (sorry, lagroue) on Client to use that path:

'--with-mysql-sock=/var/mysql/mysql.sock'

I'm not saying it's right or wrong, just hoping to understand anything I might have missed. Thanks.

[ Reply to This | # ]
10.4: Repair PHP/MySQL connections in 10.4.4
Authored by: TvE on Jan 15, '06 02:50:58AM
Are there good reasons to continue using /tmp/mysql.sock instead of /var/mysql/mysql.sock

no - it only makes your system less secure, as stated earlier in this thread. Kind'a like putin' a band-aid on a broken arm…

[ Reply to This | # ]
10.4: Repair PHP/MySQL connections in 10.4.4
Authored by: sjk on Jan 16, '06 01:31:59PM

Right, which is why I'm still puzzled that several people here apparently want to make their systems less secure by using the deprecated socket pathname. Are they misunderstanding the warnings or knowingly ignoring them?



[ Reply to This | # ]