Hey Everyone!

I’m configuring the system so it uses a FileServer to save the attachments, like indicated on the last e-mail. Now I’m having some difficulties

My OTRS installation is on Windows and I’m trying to set the ArticleDir so it has access to my FileServer. When I try to set it like //scwsti1444/FileServer, it gives me the following error:

directory //mycomputer/FileServer/2010/05/24/check_permissions.4228 changed before chdir,
expected dev=2 ino=0, actual dev=-1 ino=0, aborting. at ../..//Kernel/System/Ticket/ArticleStorageFS.pm line 48

I’ve given all access to this folder which, for testing, is located in my computer.

What else is missing?

Thanks and regards

María Alejandra Piedra

Unidad de Informática y Sistemas de Información

IICA (506) 2216-0171

Alejandra.Piedra@iica.int

De: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] En nombre de Leonardo Certuche
Enviado el: Viernes, 21 de Mayo de 2010 10:26 a.m.
Para: User questions and discussions about OTRS.
Asunto: Re: [otrs] OTRS Terms of use (Alexander Halle)

Hi there,

Alejandra, there is a sysconfig setting that allows you to store attachments not in DB but in filesystem, where are much easier to delete. It's at Ticket -> Core::Ticket and it's called Ticket::StorageModule ;)

Leonardo Certuche
www.itconsultores.com.co

On 21 May 2010 09:09, Alejandra Piedra <Alejandra.Piedra@iica.int> wrote:

Hello Philippe

I would be greatly interested in the remove attachment feature. Since some of the attachments the users send aren't useful, it would be great if we could just delete them and not make the database any bigger.

If you can't share your code is there a chance you could tell where to look into so I can make my own modifications?

Thanks and regards
Maria Alejandra Piedra

-----Mensaje original-----
De: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] En nombre de Martignier, Philippe
Enviado el: Viernes, 21 de Mayo de 2010 08:01 a.m.
Para: 'otrs@otrs.org'
Asunto: Re: [otrs] OTRS Terms of use (Alexander Halle)

Alexander,

Thanks for your response, it seems so we can do what we want with OTRS :)

I have nothing against giving our code.

The only point is that I will not be the one who will develop that code and can not force him to do so (but I will propose) :)

I wanted only to be sure that there is no problem if we customize the code in the way WE want and need.

I put WE in capitals as this draft feature for example may not be to the taste of others.

The developments will be made as much as possible OUTSIDE Otrs in order to be able to upgrade without being able to rewrite all code ...

So I am still wondering if others could be interested by such modifications ...

Cheers

Philippe

World Intellectual Property Organization Disclaimer:

This electronic message may contain privileged, confidential and
copyright protected information. If you have received this e-mail
by mistake, please immediately notify the sender and delete this
e-mail and all its attachments. Please ensure all e-mail attachments
are scanned for viruses prior to opening or using.
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/