[Rt-devel] A problem with rt-crontool

[Jason Witt]

The problem is with the @ARGV check.  Getopt::Long removes the options 
that it finds from @ARGV.  Thus if you specify only recognized options 
@ARGV will be empty.  Here is a patch:

--- /usr/local/rt3/bin/rt-crontool.orig Thu Jul  8 12:50:46 2004
+++ /usr/local/rt3/bin/rt-crontool      Thu Jul  8 13:03:58 2004
@@ -65,7 +65,7 @@
              "help"            => \$help,
              "verbose|v"       => \$verbose );

-help() if $help or not @ARGV or not $action;
+help() if $help or not $search or not $action;

  # We _must_ have a search object
  load_module($search);



Hans K wrote:
>>>>I have tried (among a lot of others) this:
>>>>/usr/rt3/bin/rt-crontool --search RT::Search::ActiveTicketsInQueue
>>>>--search-arg no-Support --action RT::Action::EscalatePriority
> 
> --verbose
> 
>>>Tail your database log while this runs. What's it do to the database
>>>when it runs?
>>
>>9 Connect     rt_user at localhost on rt3
>>9 Query       SELECT  * FROM Users WHERE Name = 'RT_System'
>>9 Query       SELECT  * FROM Users WHERE Name = 'Nobody'
>>9 Query       SELECT  * FROM Users WHERE Gecos = 'root'
>>9 Quit
> 
> 
> Uhm, I'm at a standstill with this..  Will there be a fix
> for 3.2.1 so that we can escalate tickets again?
> 
> -HK
> 
> _______________________________________________
> Rt-devel mailing list
> Rt-devel at lists.bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel