- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 30, 2004 3:01 AM
Subject: i found something ugly about freeBSD
Am probably wrong i hope.
Yes, you are. :)
... but mysqld creates a file call /tmp/mysql.sock,
but this file got to be 777
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.
Cheers,
Jorn
On Friday 30
On Friday 30 January 2004 10:20, Jorn Argelo wrote:
It's up to the administrator of the server to make sure that users
can't reach the /tmp partition then.
Ehm, you really don't want to advise this.
A proper solution:
/etc/my.cnf:
[mysqld]
socket = /var/run/mysql/socket
Then:
mkdir
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
[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 ...
Your mysql configuration isn't very secure.
(Or:
In the last episode (Jan 29), [EMAIL PROTECTED] said:
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
