Well, that's not FreeBSD's fault, but MySQL requires the mysql.sock file to be
writeable to the world, or else it wouldn't be changing the attribute by
itself. It's up to the administrator of the server to make sure that users
can't reach the /tmp partition then.
On Friday 30 January 2004 02:59, [EMAIL PROTECTED] wrote:
> Am probably wrong i hope.... but mysqld creates a file call /tmp/mysql.sock
> but this file got to be 777??? ...i loging with a other useran call a rm
> /ytmp/mysql.sock and mysql stop working ...O_o ..but then i did this ... #
> chmod -R 777 /tmp
> # /usr/local/blabla/sh mysql-server.sh start
> # chmod o-w /tmp/mysql.sock
> ..and then again mysql stop working ...soo ...from my as a administrador
> this is not posible ...because some body rm that file and ..thats ir
> ...mysql stops ...my setting bad?plz help me
> [EMAIL PROTECTED] mailing list
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"