On Sunday 30 November 2003 22:57, DG wrote:

> > -----Original Message-----
> > [mailto:[EMAIL PROTECTED] Behalf Of
> > Melvyn Sopacua
> > Sent: Monday, 1 December 2003 3:54 AM
> > To: FreeBSD-questions
> > Cc: Xpression
> > Subject: Re: MySQL question...
> <snip>
> > All databases will go under /var/db/mysql and the quick and
> > dirty answer is:
> > mysql -e "GRANT ALL ON $dbname.* TO '$dbuser'@'localhost'
> > '$userpasswd'"
> >
> > --
> > Melvyn
> Something I've wondered is why the default location for the MySQL databasi
> is /var/db/mysql?  Yes /var/db seems to make sense, but most /var
> filesystems would be fairly small.

By tradition /var is for 'variable data'.
By tradition, /var has been used for mail and news and as such do not require 
large partitions unless you run binary newsgroups. Therefore most /var 
partitions are small.
However - I agree that the chosen default is not up-to-par with the use of 
MySQL, especially since you would take smaller fragment size for a /var 
partition if you have a busy mail- or newsserver and that certainly won't 
benefit MySQL.

> Is it generally common practice to create a symbolic link to somewhere on,
> say, /usr to store the databasi?

If you know beforehand that you're going to run a mysql database with large 
databases (or use innodb which will never shrink!), than it's wise to create 
a large partition /var/db/mysql on boot.

Otherwise you can set the DB_DIR variable during installation of MySQL to 

which is not unheard of. On my workstation I use /usr/db/mysql, but on my 
workstation I also have a 15G /usr partition.

Whichever you choose, it's best to choose a DB_DIR ending in /mysql, so you 
can always decide to add another disk and mount that as $DB_DIR.

By the way: don't underestimate the size of the binary logs, especially with 
large inserts.


FreeBSD sarevok.webteckies.org 5.2-BETA FreeBSD 5.2-BETA #1: Sat Nov 29 
00:15:33 CET 2003     [EMAIL PROTECTED]:/usr/obj/usr/src/sys/

Attachment: pgp00000.pgp
Description: signature

Reply via email to