The exchange files should be left there only if you have debugging
enabled for activation. Check your log configuration and switch off
debugging for i.m.m.exchangesimple and i.m.m.exchangetransactional so
there are no new files left there.
You can safely delete all exchange* files at runtime, as long as there
is no activation running (which might not be so easy to ensure in your
case) ... if nothing else you can definitively remove all exchange*
files older then today.
HTH,
Jan

On Wed, 2009-03-25 at 13:49 +0100, Matteo Pelucco wrote:
> Jan Haderka ha scritto:
> > what kind of files? can you provide sample of the file names of such
> > files?
> 
> Hi Jan, sure, this is an extract of ls -al:
> 
> -rw-r--r--  1   91   91      637 Mar 25 12:51 
> exchange_000133823.xml.gz.failed1237981977082
> 
> -rw-r--r--  1   91   91 25461045 Feb 27 20:12 
> data.rtsi.proxyObjects.2008.xml
> 
> -rw-r--r--  1   91   91      735 Mar 20 20:24 
> exchange_--034-Non-chiudete-gli-uffici-postali--034-475397.xml.gz.failed1237577114668
> 
> -rw-r--r--  1   91   91        0 Mar 16 16:09 resources155447.xml
> 
> 
> some statistics:
> exchange*failed around 7000
> resources*.xml around 8000
> other (content named) around 1000 / 2000
> 
> 
> Matteo
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
-- 
Best regards,

Jan Haderka
Magnolia International Ltd.

----------------------------------------------------------------------
[email protected]                http://www.magnolia-cms.com
Magnolia®  - Simple Open Source Content Management
----------------------------------------------------------------------


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to