RT 3.8 and RT 4.0 uses sessions for uploaded files, so this shouldn’t
be an issue.
Also, even one server true tmp files can not be shared between apache
processes, so RT avoids them. Even tmp file is created, it’s destroyed
during the same request.
As far as I can see from our code and modules we use, everything
should respect TMPDIR. The only reason for files to be created in
different dir that TMPDIR ENV variable is either cleared or
overwritten later.On Wed, Aug 10, 2011 at 3:16 PM, Luca Villani email@example.com wrote:
In data giovedì 4 agosto 2011 17:15:38, hai scritto:
Depending on your version of RT, it uses HTML::Mason’s cgi_object,
which is often CGI.pm, and that should respect TMPDIR
We had upgrade yesterday to RT 4.0.1, this is the relevand section in
Allow from all
SetEnv TMPDIR /www/COMMON/tmp
PerlSetVar psgi_app /opt/rt/rt-4.0.1/sbin/rt-server
SetEnv appears also at virtualhost definition, with no results.
No one can give us a feedback about this?
As far as RT store web loaded ticket attachments in /var/tmp, there is no
chance to clusterize an installation: it is ok to use a NFS shared directory
for tmpdir so all webserver in cluster can find attach even in case the
balancer move the connection from one server to other, but it is not
acceptable to mount the entire /var/tmp from a filer…
Luca Villani - Register.It S.p.A. - Dada Group
Tel: +39 055 20021517 Mobile: +39 335 8753086
ICQ: 76272621 Skype: luca.villani
RT Training Sessions (http://bestpractical.com/services/training.html)
- Chicago, IL, USA September 26 & 27, 2011
- San Francisco, CA, USA October 18 & 19, 2011
- Washington DC, USA October 31 & November 1, 2011
- Melbourne VIC, Australia November 28 & 29, 2011
- Barcelona, Spain November 28 & 29, 2011
Best regards, Ruslan.