I’ve read and read all instructions, IMHO, very very closely. And in the
last 8 hours - after installing perl 5.6.1 and all it’s friends, in almost
every order - I give up. I ask now for help if you would be so kind =)
[Wed Aug 15 16:43:30 2001] [error] Can’t write to
’/u02/rt/masonpath/rt.log.27956.0’: Permission denied at
/usr/local/lib/perl5/site_perl/5.6.1/Log/Dispatch/File.pm line 69.
Now. It’s a virtual server running suexec to allow the server to run as a
different user - in this case rt/rt.
The permissions on that directory are 1 drwxr-xr-x 2
rt rt 1024 Aug 15 13:38 masonpath which should be fine if
the server is writing the log file as rt.
I’ve read and read all instructions, IMHO, very very closely. And in the
last 8 hours - after installing perl 5.6.1 and all it’s friends, in almost
every order - I give up. I ask now for help if you would be so kind =)
[Wed Aug 15 16:43:30 2001] [error] Can’t write to
‘/u02/rt/masonpath/rt.log.27956.0’: Permission denied at
/usr/local/lib/perl5/site_perl/5.6.1/Log/Dispatch/File.pm line 69.
Now. It’s a virtual server running suexec to allow the server to run as a
different user - in this case rt/rt.
The permissions on that directory are 1 drwxr-xr-x 2
rt rt 1024 Aug 15 13:38 masonpath which should be fine if
the server is writing the log file as rt.
With modperl, the server is writing the file as your modperl user.
I’m not sure why we haven’t seen a feature where in you can select multiple
items in the queue and delete all at once? I mean - I can’t be the only
one who has had to go into MySql and issue:
SQL-query:
select count(1) from each_req where requestors=‘spam’;
update each_req set status=‘resolved’ where requestors=‘info@’;
SQL-query:
select count(1) from each_req where subject LIKE ‘%spam here%’;
update each_req set status=‘resolved’ where subject LIKE ‘%Spam here%’;
Am I? =) Problem is - not everyone here has that sort of access to the
database so they have to sit there with sometimes 1000’s of unresolved queue!
I would also like to request that it would be possible to set a “ignore” switch
for a user/email similar to the “Let the user access RT” switch so that all
email from this user is ignored.
Would be handy to minimise repeated spamming.
OliOn Thu, 16 Aug 2001, Phillip White wrote:
I’m not sure why we haven’t seen a feature where in you can select multiple
items in the queue and delete all at once? I mean - I can’t be the only
one who has had to go into MySql and issue:
SQL-query:
select count(1) from each_req where requestors=‘spam’;
update each_req set status=‘resolved’ where requestors=‘info@’;
SQL-query:
select count(1) from each_req where subject LIKE ‘%spam here%’;
update each_req set status=‘resolved’ where subject LIKE ‘%Spam here%’;
Am I? =) Problem is - not everyone here has that sort of access to the
database so they have to sit there with sometimes 1000’s of unresolved queue!
From the web ui. Do a search. Click on “Update all these tickets at once”
The CLI also supports operations across multiple tickets natively.On Thu, Aug 16, 2001 at 05:10:30AM -0400, Phillip White wrote:
I’m not sure why we haven’t seen a feature where in you can select multiple
items in the queue and delete all at once? I mean - I can’t be the only
one who has had to go into MySql and issue:
SQL-query:
select count(1) from each_req where requestors=‘spam’;
update each_req set status=‘resolved’ where requestors=‘info@’;
SQL-query:
select count(1) from each_req where subject LIKE ‘%spam here%’;
update each_req set status=‘resolved’ where subject LIKE ‘%Spam here%’;
Am I? =) Problem is - not everyone here has that sort of access to the
database so they have to sit there with sometimes 1000’s of unresolved queue!