PHP List,
Recently, my web hosting server has been maxing out it's alloted hard
drive space. It turns out that there are no single large files, but that
I have been maxing out my inode usage. Not being a Unix expert, I have a
limited understanding of inodes, but it seems they are related to files
and, essentially, more files being written to by active process creates
more inodes.
I've eliminated log files and email spools as possible causes, and now I
think the next most likely cause is PHP sessions not being properly cleared.
This was suggested to me by my web hosting services support staff. It
seems likely because a lot of PHP code that I wrote while early in the
process of learning PHP is still in use, and so it is easy to believe
that I had not properly cleared sessions.
Actually, I thought sessions timed out and cleared automatically, so I
erroneously haven't set up any specific cache clearing protocols.
Anyway, I have now begun adding the following code to my scripts:
$_SESSION = array();
session_unset();
session_destroy();
But, it seems that inodes related to earlier, not properly destroyed
sessions might still be lingering.
Is there a way I can:
1. Verify that sessions are in fact the cause of inodes being created?
2. Destroy them?
Thank you for any advice.
--
Dave M G
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
