I wanted to respond with what I found:
APPARMOR blocks mysql from writing to any other directory than the data
dir and /tmp.
I had to edit the /etc/apparmor.d/usr.sbin.mysqld file and add the
following:
/backups/mysql** rwk,
to the bottom.
Hope this helps someone.
Ray
--
MySQL General
So I am trying to use mysqldump --tab for the first time. I am running
into the same problem everybody does on their first try --- Errcode: 13. I
have set the permissions on the target directory to be completely liberal
--- anybody can do anything with it --- and I still get Errcode: 13. I
Mike Spreitzer wrote:
So I am trying to use mysqldump --tab for the first time. I am running
into the same problem everybody does on their first try --- Errcode: 13. I
have set the permissions on the target directory to be completely liberal
--- anybody can do anything with it --- and I still
PROTECTED] /]#
Thanks,
Mike
Jed Reynolds [EMAIL PROTECTED]
02/22/08 07:04 PM
Please respond to
[EMAIL PROTECTED]
To
Mike Spreitzer/Watson/[EMAIL PROTECTED]
cc
mysql list mysql@lists.mysql.com
Subject
Re: mysqldump: Got error: 1: Can't create/write to file
'dumpdir/tablename.txt' (Errcode: 13
what happens when you delete the files that are already in there? Looks
like you're dumping to a file owned by root.
Jed
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Subject
Re: mysqldump: Got error: 1: Can't create/write to file
'dumpdir/tablename.txt' (Errcode: 13) when executing 'SELECT INTO OUTFILE'
what happens when you delete the files that are already in there? Looks
like you're dumping to a file owned by root.
Jed
--
MySQL General Mailing List
Mike Spreitzer wrote:
Sorry if I have confused people by presenting
evidence in the wrong order. Also, it seems that the .sql file is
written by the client while the .txt file is (attempted to be) written
by the server. Here is a single typescript with all the evidence:
[EMAIL PROTECTED]
