Image via Wikipedia
If you have problems with file permissions, the UMASK environment variable might be set incorrectly when mysqld starts. For example, MySQL might issue the following error message when you create a table:
ERROR: Can't find file: 'path/with/filename.frm' (Errcode: 13)
The default UMASK value is 0660. You can change this behavior by starting mysqld_safe as follows:
shell> UMASK=384 # = 600 in octal
shell> export UMASK
shell> mysqld_safe &
By default, MySQL creates database and RAID directories with an access permission value of 0700. You can modify this behavior by setting the UMASK_DIR variable. If you set its value, new directories are created with the combined UMASK and UMASK_DIR values. For example, if you want to give group access to all new directories, you can do this:
shell> UMASK_DIR=504 # = 770 in octal
shell> export UMASK_DIR
shell> mysqld_safe &
MySQL assumes that the value for UMASK or UMASK_DIR is in octal if it starts with a zero
Related articles by Zemanta
- mysql_upgrade and Innodb Tables (mysqlperformanceblog.com)
- Clearing Old Business Process Instances from LiveCycle Process Management (blogs.adobe.com)
- How To Diagnose And Fix Incorrect Post Comment Counts In WordPress (beerpla.net)
- Using Aspersa to capture diagnostic data (xaprb.com)
- Metasploit 3.4.0 Released (blogs.securiteam.com)
- Table of Contents (slideshare.net)
- MySQL Security (slideshare.net)
- Force MySQL Import to NearlyFreeSpeech.Net Host (masbuchin.com)
- MOW2010: 1TB MySQL Database Migration and HA Infrastructure by Alex Gorbachev, Pythian (slideshare.net)
- Strategy: Scale Writes to 734 Million Records Per Day Using Time Partitioning (highscalability.com)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=8d121421-eaec-414f-8fbd-0252f0406ad4)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=edbe6051-c925-4327-8ddb-7e080d202a27)
