Zbigniew Szalbot wrote:
Will any future upgrade (by means of portupgrade) not change the custom
mysql location back to /var/db/mysql?
Not if you set:
mysql_dbdir="/usr/mysql"
in /etc/rc.conf
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory
On May 2, 2008, at 9:28 AM, Zbigniew Szalbot wrote:
Hi Chris,
Chris Pratt pisze:
Thank you anyway - this was very helpful and I instantly saved a
lot of space on a shrinking /var partition!
I find it most comfortable to do this manually so I can check
my backups first. There is an examp
Hi Chris,
Chris Pratt pisze:
Thank you anyway - this was very helpful and I instantly saved a
lot of space on a shrinking /var partition!
I find it most comfortable to do this manually so I can check
my backups first. There is an example in the reply comments
below the documentation on the
On May 2, 2008, at 8:58 AM, Zbigniew Szalbot wrote:
The procedure for this is here:
http://dev.mysql.com/doc/refman/5.1/en/purge-master-logs.html
for 5.1 and here:
http://dev.mysql.com/doc/refman/5.0/en/purge-master-logs.html
for 5.0
Thanks a lot! It did help me get rid of a few files in a
Hello,
Chris Pratt pisze:
On May 2, 2008, at 5:27 AM, Zbigniew Szalbot wrote:
Hello,
Following a recent thread I would like to ask if it is safe to
remove old binlog data. From the below I understand that the
current binlog is mysql-bin.07 and the previous ones (from
01-06)
On May 2, 2008, at 5:27 AM, Zbigniew Szalbot wrote:
Hello,
Following a recent thread I would like to ask if it is safe to
remove old binlog data. From the below I understand that the
current binlog is mysql-bin.07 and the previous ones (from
01-06) are not written to any more
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Zbigniew Szalbot wrote:
> Hello,
>
> Following a recent thread I would like to ask if it is safe to remove
> old binlog data. From the below I understand that the current binlog is
> mysql-bin.07 and the previous ones (from 01-06) are
