2013/04/05 11:16 +0200, Johan De Meersman
Half and half - rename the file, then issue "flush logs" in mysql to close and
reopen the logs, which will cause a new log with the configured name to be
created.
That being said, I'm not much aware of Windows' idiosyncracies - I hope the
damn
Am 04.04.2013 23:08, schrieb h...@tbbs.net:
> Is there somewhere within MySQL means of aging the error log, that it not
> indefinitly grow big, or is that done through the OS and filesystem on which
> "mysqld" runs?
man logrotate
signature.asc
Description: OpenPGP digital signature
Am 05.04.2013 11:16, schrieb Johan De Meersman:
> - Original Message -
>> From: h...@tbbs.net
>> Subject: Re: error-log aging
>>
>> man logrotate
>> <<<<<<<<
>> Not Unix!
>
> So get unix :-)
>
>> In any cas
- Original Message -
> From: h...@tbbs.net
> Subject: Re: error-log aging
>
> man logrotate
> <<<<<<<<
> Not Unix!
So get unix :-)
> In any case, I take this to mean that this is not done within MySQL,
> right?
Half and half - rename the
2013/04/04 23:18 +0200, Reindl Harald
> Is there somewhere within MySQL means of aging the error log, that it not
> indefinitly grow big, or is that done through the OS and filesystem on which
> "mysqld" runs?
man logrotate
Not Unix!
In any case, I take this to mean that this
Is there somewhere within MySQL means of aging the error log, that it not
indefinitly grow big, or is that done through the OS and filesystem on which
"mysqld" runs?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
