I don't know the answer to your question, but as a side note, I've always found cat'ing /dev/null into a file to be safer if the file may be in use
cat /dev/null > foo.log > -----Original Message----- > From: Jesse Sheidlower [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 02, 2003 10:27 AM > To: [EMAIL PROTECTED] > Subject: Re-establishing nuked log file > > > > I recently restarted my MySQL server (4.0.10 in this case) with > the general query log enabled, to help out with some debugging and > optimization issues. After looking at a batch of these, I then > deleted the log file directly, with "rm foo.log", assuming that it > would be re-generated as soon as the next query came in. It was > not. > > Is there any way to get logging restarted without stopping and > restarting the server itself, which is live and which I'd prefer > not to interrupt? > > Thanks. > > Jesse Sheidlower > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
