Yes, the file permissions do affect whether the table can be updated.
The files need to be writable (in the filesystem sense) by the user
running mysqld.
By default MySQL creates directories umask 0700 and files 0660 unless
the UMASK env variable is set differently when mysqld is started. If you
chown to the user running mysql and chmod the files to an appropriate
umask you should see this issue go away.
Robert Reed wrote:
Greetings,
I've recently inherited a FreeBSD server running MySQL
3.23.54. It's good and stable. I have a second
server that runs as a slave to the first. Everything
goes smoothly until I make changes to a certain table
on my master. This will kill the slave with the error
that this table is read-only. These are all MyISAM
tables. I noticed recently that the various
directories have different permissions and access
levels on them and wondered what the correct levels
should be. And...does this even have an effect on
whether the table can be written to?
Thanks in Advance
=
Robert Reed
512-869-0063 home
512-818-2460 cell
__
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
