Freeing .MYD and .MYI Files

[himilecyclist]

After running my PHP/MySQL application, I have found that the
associated .MYD and .MYI files remain locked. Even after the browser
is closed, if I try to rename these files, I get the message:

Can't rename filename. It is being used by another person or
program...

These files remain locked until I reboot. I'm running on a Windows XP
machine.

Here is a code snippet that locks the two files:

<?php

//Connect to server and database

$host="localhos t";
$user="root";
$password="";

$edenconnect = mysql_connect($ host,$user,$pas sword)
or die("Could not connect to server.");
mysql_select_db ("eden")
or die("Could not connect to database.");

$sql = "SELECT * FROM edenmaster";

$result = mysql_query($sq l);

$row = mysql_fetch_arr ay($result);

mysql_free_resu lt($result);

mysql_close(); // Also tried mysql_close($ed enconnect);

exit;
?>

After running this snippet and closing the browser, files
edenmaster.myd and edenmaster.myi are locked to renaming until a
reboot.

I thought the mysql_close() would free the files, but it does not.

Any ideas?

Thanks!

[Andy Hassall]

On 7 Sep 2005 12:30:09 -0700, hi***********@y ahoo.com wrote:

After running my PHP/MySQL application, I have found that the
associated .MYD and .MYI files remain locked. Even after the browser
is closed, if I try to rename these files, I get the message:

Can't rename filename. It is being used by another person or
program...

These files remain locked until I reboot. I'm running on a Windows XP
machine.

After running this snippet and closing the browser, files
edenmaster.m yd and edenmaster.myi are locked to renaming until a
reboot.

I thought the mysql_close() would free the files, but it does not.

Why are you expecting the files to be unlocked?

The MySQL server daemon will have them open, and there's no reason for it to
close the files whilst it's running.

Why are you renaming the files via the filesystem? To rename a table you use
the RENAME SQL command.

--
Andy Hassall :: an**@andyh.co.u k :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool

[himilecyclist]

Andy Hassall wrote:

Why are you expecting the files to be unlocked?

I assumed when the application closed the database, the files would be
released.
The MySQL server daemon will have them open, and there's no reason for it to
close the files whilst it's running.

Even after closing MySQL and the Apache server, the files are still
locked.
Why are you renaming the files via the filesystem? To rename a table you use
the RENAME SQL command.
I bumped into this by accident. I'm not concerned about renaming them,
just the fact that the connection still seems to be open.

Thanks!
--
Andy Hassall :: an**@andyh.co.u k :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool

[Andy Hassall]

On 7 Sep 2005 12:56:51 -0700, hi***********@y ahoo.com wrote:

Andy Hassall wrote:

Why are you expecting the files to be unlocked?

I assumed when the application closed the database, the files would be
released.

The application only sees the view of the database that the MySQL daemon
offers it, through SQL. The files are an implementation detail handled by the
daemon itself; the client application can't open or close them.

The MySQL server daemon will have them open, and there's no reason for it to
close the files whilst it's running.

Even after closing MySQL and the Apache server, the files are still
locked.

After closing MySQL? As in stopping the MySQL daemon? That would be more
unusual - only MySQL itself has any business accessing those files, so if you
stop the MySQL service completely then nothing else should have them open.

Could you expand on what you mean by "closing MySQL"?

You can find what has files open with a tool like Process Explorer
(http://www.sysinternals.com/Utilitie...sExplorer.html)

Why are you renaming the files via the filesystem? To rename a table you use
the RENAME SQL command.

I bumped into this by accident. I'm not concerned about renaming them,
just the fact that the connection still seems to be open.

PHP will have closed its connection, as you were using mysql_connect rather
than mysql_pconnect (which does persistent connections).

That doesn't have any implication that the MySQL daemon will close files in
response - there's no particular reason it should, it'd only have to open them
again later.

--
Andy Hassall :: an**@andyh.co.u k :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool

[himilecyclist]

Andy Hassall wrote:

On 7 Sep 2005 12:56:51 -0700, hi***********@y ahoo.com wrote:

Could you expand on what you mean by "closing MySQL"?

I am running the Apache Friends implementation of PHP and MySQL. They
provide .bat files to start the two services which then stay resident.
I have been closing/stopping them by closing their Windows program
boxes. It looks like that does close Apache, but MySQL still appears
as a running process.

Just tried closing the MySQL process, and now the files are freed up.

Thanks for getting me on the right track!