Hello.
>I want to place my database on a NAS drive. Usually it is not recommended to use network filesystems, due to high performance penalty. > I'm trying to relocate the database files for MySQL 4.1 > I've seen two primary techniques for doing this: Have a look here as well: http://dev.mysql.com/doc/mysql/en/moving.html http://dev.mysql.com/doc/mysql/en/upgrading-to-arch.html William Fry wrote: > I'm trying to relocate the database files for MySQL 4.1 > I've seen two primary techniques for doing this: > 1) create/alter a my.cnf file with 'datadir' set to new location > 2) moving the physical files and creating a symlink in the original location > > Unfortunately, neither of these methods work for me. > > I have my MySQL server running on a Mandrake 10.1 Linux box with limited > hard drive space. I want to place my database on a NAS drive. > The NAS drive support many protocols: NFS, SMB, AFP, etc. so I have no > problem at all accessing the device from my database server. However, the > problem seems to be that, as part of MySQL server's normal operation, it > creates a socket file. Unfortunately, this activity is not allowed on a > remote share. So, when the server starts up, its attempt to create > "mysql.sock" fails. > > It appears that both relocation methods indicated above cause EVERYTHING to > be relocated, i.e. not only the "hard" files, but the socket "file" also. > > Is there a way to have the "hard" files relocated but keep the socket "file" > in /var/lib/mysql? > > Thanks! > - Liam > > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
