Is there a configurable temp directory for MODx?#

Hello,

I think I have a dumb question but I dare to ask it anyway. I am in a little struggle with a customer's ISP/hoster. The website does not work anymore, MODx only outputs an error, saying

« Execution of a query to the database failed - Can't create/write to file '/tmp/#sql_94a_0.MYI' (Errcode: 13) »

In my eyes, this is an error of the MySQL server and has nothing to do with MODx.

But he (the hoster) wants me to change the settings of the "MODX temp directory" to a path in the local space of the account, not to "/tmp". I told him: MODx uses the tmp setting from the php.ini (and that path is set absolutely correct). But he insists. Me too
BTW: I can login to the manager. In the manager, I see the resources tree. I can edit leaf documents, but as soon as I click a container resource, I get the same error as given above.

Am I right? Is he wrong?

MODx is: 1.0.0 (had no time to update, yet)
PHP is: 5.2.0-8+etch16
MySQL is: 5.0.32-Debian_7etch12-log
System is: Linux mx03 2.6.18-6-686-bigmem
Server API is: Apache 2.0 Handler

This problem has nothing at all to do with MODx. Nor PHP, for that matter. It's a MySQL problem.

http://dev.mysql.com/doc/refman/5.0/en/cannot-create.html

Thank you very much, Susan. That's what I thought. I'll give that link to the hoster.

Many thanks
Martin

I would first suspect a full hard drive; that's the most common source of the problem appearing after a period of successful use.

I told him three times, but he does not seem to listen to me

Quote from: FuryDE at Aug 18, 2010, 08:54 AM

I told him three times, but he does not seem to listen to me

If you host is unwilling to listen to you then I would ask him to listen as you move to another host. I rely on my host(s) to listen to my problems and solve them, not to blame my scripts when they aren't the cause.

If he would have been my hoster, he would not be any more ... But it is the decision of my customer ... we'll see.