Hi all,
>From the manual:
*Any file created by INTO OUTFILE or INTO DUMPFILE is writable by all users
on the server host. The reason for this is that the MySQL server cannot
create a file that is owned by anyone other than the user under whose
account it is running. (You should never run
mysqld
Thank you. It's working now.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Ok, on my linux (slackware 10) /var/www is owner by root.root with
permissions rwxr-xr-x (755). Say you want mysql to put your data
in a subdirectory under /var/www named data.
As root, do:
mkdir /var/www/data
chgrp mysql /var/www/data
chmod 775 /var/www/data
Now mysql has write permissions to /
I experimented with a local /var/www folder. I assumed setting 2, 6, or
7 for the Other value would give mysql write privileges, but mysql would
not settle for anything less than a 7 in that last slot. What was really
curious to me was that the User and Group settings were inconsequential.
I even s
ctory to some other folder?
>
>> --
>> From:Gerald L. Clark
>> Sent:Friday, April 27, 2007 10:09 AM
>> To: Kebbel, John
>> Cc: mysql@lists.mysql.com
>> Subject: Re: Permissions and Into Outfile
>>
>> Kebbel, John wrote:
>> >
Kebbel, John wrote:
cat /etc/passwd on my Macintosh 10.3 at work (I'm using Linux at home) shows me
this for mysql ...
mysql:*:74:74:MySQL Server:/var/empty:/usr/bin/false
The home directory for mysql is /var/empty, which does exist. Should I write
~into file~ output to this folder or should
mysql home directory
to some other folder?
> --
> From: Gerald L. Clark
> Sent: Friday, April 27, 2007 10:09 AM
> To: Kebbel, John
> Cc: mysql@lists.mysql.com
> Subject: Re: Permissions and Into Outfile
>
> Kebbel, John wrote:
> > I
Kebbel, John wrote:
I was trying to write the output of a select statement to a tab-delimited text file. I could not write the file to a folder inside /var/www or to my home file because of permission problems. After a moment's reflection, I realized /tmp had stuff written to it all the time, so