Hi Hal,
You might like to try setting the umask for the mysql user. I would
think the server would abide by the OS rules for permission settings.
You may be able to set the UMASK_DIR environment variable (as described
here http://dev.mysql.com/doc/refman/5.0/en/environment-variables.html).
Regards
---
** _/ ** David Logan
*** _/ *** ITO Delivery Specialist - Database
*_/* Hewlett-Packard Australia Ltd
_/_/_/ _/_/_/ E-Mail: [EMAIL PROTECTED]
_/ _/ _/ _/ Desk: +618 8408 4273
_/ _/ _/_/_/ Mobile: 0417 268 665
*_/ **
** _/ Postal: 148 Frome Street,
_/ ** Adelaide SA 5001
Australia
invent
---
-Original Message-
From: Hal Vaughan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 3 January 2006 7:54 AM
To: mysql@lists.mysql.com
Subject: File Permissions On Database Files
My MySQL databases are stored in a directory that is with the rest of my
project. I am using rsync to back up the entire project, including the
database files. I'd much rather do it this way than to create files
with
mysqldump. Whenever MySQL creates a new database, the file is owned by
the
user mysql, and has limited read and write permissions (this is on
Linux,
btw). It would be a HUGE help if I could make sure every time MySQL
creates
any files, it creates them with at least group if not all read access
for
backup purposes.
Is there a simple way to do this?
Thanks!
Hal
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
