From: Julien Lory
Date: September 2 2010 8:26pm
Subject: Re: Symlinks not working when pointing to another table.
List-Archive: http://lists.mysql.com/mysql/222816
Message-Id: <4C800883.3070000@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I'm using Debian Lenny ( up to date ), so there is no app armor / 
selinux / grsec :/

ii  mysql-client-5.0                  5.0.51a-24+lenny4         MySQL 
database client binaries
ii  mysql-common                      5.0.51a-24+lenny4         MySQL 
database common files
ii  mysql-server-5.0                  5.0.51a-24+lenny4         MySQL 
database server binaries


On 02/09/2010 16:18, Daevid Vincent wrote:
>
>
>    
>> -----Original Message-----
>> From: Julien Lory [mailto:julien.lory@stripped]
>> Sent: Thursday, September 02, 2010 12:31 PM
>> To: mysql@stripped
>> Subject: Symlinks not working when pointing to another table.
>>
>>    Hello,
>>
>> I've done lot of researches and tests but can't find any
>> answer. I need
>> to share one table between two db, those two db are in the
>> same path (
>> /var/lib/mysql/db1&  db2 ). I created symbolic links for db2
>> pointing to
>> the table in db1.
>> When I query the table from db2 I get this error :
>> 'ERROR 1030 (HY000): Got error 140 from storage engine'
>> I'm sure it was working in previous version of MySQL, but
>> from the last
>> version it's no longer working.
>>
>> This is how it looks :
>>
>> test-lan:/var/lib/mysql/test3# ls -alh
>> drwx------ 2 mysql mysql 4.0K 2010-08-30 13:28 .
>> drwxr-xr-x 6 mysql mysql 4.0K 2010-08-30 13:29 ..
>> lrwxrwxrwx 1 mysql mysql 28 2010-08-30 13:28 blbl.frm ->
>> /var/lib/mysql/test/blbl.frm
>> lrwxrwxrwx 1 mysql mysql 28 2010-08-30 13:28 blbl.MYD ->
>> /var/lib/mysql/test/blbl.MYD
>> lrwxrwxrwx 1 mysql mysql 28 2010-08-30 13:28 blbl.MYI ->
>> /var/lib/mysql/test/blbl.MYI
>> -rw-rw---- 1 mysql mysql 65 2010-08-30 13:24 db.opt
>>
>>
>> I really need those symlinks, is there a way to make them
>> working like
>> before ? ( old MySQL-server is fine )
>>      
> Just out of curiosity. If you're using apparmor and this new directory is
> on another partion or mount point or anything, you might have to add a rule
> in apparmor's config for them...
>
>