[imp] Problem with linked attachment on larger files

[Jan Schneider]

Please don't top-post.

Zitat von Kim Haverblad <kim at haverblad.net>:

> On 26/07/2010 13:35, Jochen Roderburg wrote:
>> Zitat von Kim Haverblad <kim at haverblad.net>:
>>
>>> file_uploads: On
>>> upload_max_filesize: 256M
>>> max_input_time: 180
>>> memory_limit: 256M
>>> max_execution_time: 600
>>> post_max_size: 256M
>>
>> Well, the memory_limit might still be to small for your 30MB attachments.
>> In my experience the thing needs unexpectedly high amounts of main
>> memory to encode attachments. If you are brave, set it to -1
>> (unlimited).  ;-)
>>
>> Regards, J.Roderburg
>>
> Setting the memory limit to either 2048 or -1 gives me DB Error: unknown
> error within the Composer windows. So that didn't work out and actually
> -1 seems to crash MySql or something since I had to restart the server
> to bring up mysql again.
>
> Makes me wonder; since I'm using Owl dms (php based as well) where I
> easily can upload and process 60-80M files. How is the file actually
> processed within Imp since it actually fails and as well fails to clean
> out the temporary files from /var/tmp?

If you configured VFS (which is used to store linked attachments) to  
use SQL as the backend storage, you might have hit a limit in your  
database configuration.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/