try
tail -n 10 /mysql/why.log /tmp/why.log
echo /mysql/why.log
-Original Message-
From: Van [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 12, 2002 6:01 PM
To: Paul DuBois
Cc: MySQL
Subject: Re: Irritating Discovery
Paul DuBois wrote:
At 13:12 -0700 6/12/02
This works for me:
mv /mysql/log /mysql/Oldlog
mysqladmin flush-logs
MySQL follows the oldlog, keeps writing to it until the flush, when it
closes its Oldlog,
and open/create-s its logfile.
Cheers,
Kent
-
Before
Greetings:
Perhaps a bug, even. After about 5 months my mysql log file grew to over
300MBytes and I figured I'd do something about it as follows:
tail -n 10 /mysql/why.log /tmp/why.log sudo mv /tmp/why.log /mysql/
mysqladmin -u root flush-logs
Unfortunately, this set the permissions of
At 13:12 -0700 6/12/02, Van wrote:
Greetings:
Perhaps a bug, even. After about 5 months my mysql log file grew to over
300MBytes and I figured I'd do something about it as follows:
tail -n 10 /mysql/why.log /tmp/why.log sudo mv /tmp/why.log
/mysql/
mysqladmin -u root flush-logs
Paul DuBois wrote:
At 13:12 -0700 6/12/02, Van wrote:
Greetings:
Perhaps a bug, even. After about 5 months my mysql log file grew to over
300MBytes and I figured I'd do something about it as follows:
tail -n 10 /mysql/why.log /tmp/why.log sudo mv /tmp/why.log
/mysql/
mysqladmin
