replication binary log files location

[Crouch, Luke H.]

I'm trying to move my binary log files onto a different drive than our main data drive 
to get a little performance boost.
 
the drives are set up like so:
drive 1 (sda):
swap
/boot
/usr
 
drive 2 (sdb):
/
 
mysql is installed in /usr/local/mysql and its data directory is /usr/local/mysql/var
I want to set the binary logs to go to the 2nd drive, sdb, so I made a new directory, 
/logging
I went into logging and changed its ownership and group to mysql...
chown -R mysql .
chgrp -R mysql .
[EMAIL PROTECTED] logging]# pwd
/logging
[EMAIL PROTECTED] logging]# ls -al
total 8
drwxr-xr-x2 mysqlmysql4096 Aug 24 04:26 .
drwxr-xr-x   23 root root 4096 Aug 24 04:53 ..
 
then went into my.cnf and put:
log-bin=/logging
 
but when I try to start mysql this way:
[EMAIL PROTECTED] mysql]# bin/mysqld_safe --user=mysql 

no logging, and I get this in the .err file
040824  5:46:53  Could not use /logging for logging (error 13). Turning logging off 
for the whole duration of the MySQL server process. To turn it on again: fix the 
cause, shutdown the MySQL server and restart it.

error 13 is typically a unix permissions error, right? but I changed the /logging 
directory to be owned by mysql (and am running mysqld_safe --user=mysql)
 
any ideas?
 
thanks,
-L

Luke Crouch 
918-461-5326 
[EMAIL PROTECTED] 

 

Re: replication binary log files location

[Crouch, Luke H.]

I found the solution to my own problem...
 
the log-bin option is a specific filename. so when you set:
log-bin=/logging
 
mysql must have ownership of the / folder, as it is trying to create /logging.001 and 
/logging.index
 
easily fixed by adding the file-name to the path...
 
log-bin=/logging/host-name
which will now create /logging/host-name-bin.001 and /logging/host-name-bin.index
and since mysql has ownership of the logging directory, this is okay...
 
-L

Luke Crouch 
918-461-5326 
[EMAIL PROTECTED]