I am running Debian Stable, with the package install of RT 3.4
The bosses would like to see some automatic Escalation. After looking
at the wiki (
http://wiki.bestpractical.com/index.cgi?AnotherConfigurationEscalationExample
) I tried the following:
rtuser@trouble:~$ rt-crontool --search RT::Search::ActiveTicketsInQueue
–search-arg testing --action RT::Action::EscalatePriority
But got the following error:
Can’t locate /etc/request-tracker3.4/RT_SiteConfig.pm in @INC (@INC
contains: /usr/local/share/request-tracker3.4/lib
/usr/share/request-tracker3.4/lib /etc/perl /usr/local/lib/perl/5.8.4
/usr/local/share/perl/5.8.4 /usr/lib/perl5 /usr/share/perl5
/usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at
/usr/share/request-tracker3.4/lib/RT.pm line 123.
I tried changing the variable in /usr/share/request-tracker3.4/lib/RT.pm
to:
$SITE_CONFIG_FILE = “RT_SiteConfig.pm”;
and then added a symlink in /usr/local/share/request-tracker3.4/lib to
/etc/request-tracker3.4/RT_SiteConfig.pm
when I tried re-running the rt-crontool command, I got a different
error. So as to not break anything, I just set things back to “normal”
RT on 3.4 has be stable for quite some time in Debian, so I can not
imagine this is a bug, so I am guessing I am doing something wrong. If
anyone could give me a few pointers where to look, I would appriciate
it. If this truly seems like a bug, I will be more then happy to turn
it in. I just can image that something as simple as this would not have
been caught already by the Debian users on this list 
Associate yourself with men of good quality if you esteem
your own reputation; for 'tis better to be alone then in bad
company. - George Washington, Rules of Civility
