A problem with rt-crontool

Helptext for rt-crontool is wrong:

Under example:
"bin/rt-cron-tool " <- One too many -'s there
and
"Escalate ticketsrt-crontool " <- add “\nbin/” maybe?

And when I try to actually use the escalate function
I just keep getting the help-screen no matter what I do.
No errors, just help. It also doesn’t escalate.

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

Is this not the right syntax?

-HK

Helptext for rt-crontool is wrong:

Diff for correct (as far as I can see) help text example below.
It does not fix the problem I have of course.

@@ -194,7 +194,7 @@
)
. “\n\n”;

  • print " bin/rt-crontool \\n";
  • print " bin/rt-cron-tool \\n";
    print
    " --search RT::Search::ActiveTicketsInQueue --search-arg
    general \\n";
    print
    @@ -203,10 +203,10 @@
    print " --verbose\n";

    print “\n”;

  • print loc(“Escalate tickets\n”);
  • print " bin/rt-crontool \\n";
  • print " --search RT::Search::ActiveTicketsInQueue --search-arg
    thequeuename \\n";
  • print " --action RT::Action::EscalatePriority \\n";
  • print loc(“Escalate tickets”);
  • print “rt-crontool \\n”;
  • print " --search RT::Search::ActiveTicketsInQueue --search-arg
    thequeuename \\n";
  • print " --action RT::Action::EscalatePriority \\n";

Thanks very much for the patch.On Fri, Jul 02, 2004 at 03:09:49PM +0200, Hans K wrote:

Helptext for rt-crontool is wrong:

Diff for correct (as far as I can see) help text example below.
It does not fix the problem I have of course.

@@ -194,7 +194,7 @@
)
. “\n\n”;

  • print " bin/rt-crontool \\n";
  • print " bin/rt-cron-tool \\n";
    print
    " --search RT::Search::ActiveTicketsInQueue --search-arg
    general \\n";
    print
    @@ -203,10 +203,10 @@
    print " --verbose\n";

    print “\n”;

  • print loc(“Escalate tickets\n”);
  • print " bin/rt-crontool \\n";
  • print " --search RT::Search::ActiveTicketsInQueue --search-arg
    thequeuename \\n";
  • print " --action RT::Action::EscalatePriority \\n";
  • print loc(“Escalate tickets”);
  • print “rt-crontool \\n”;
  • print " --search RT::Search::ActiveTicketsInQueue --search-arg
    thequeuename \\n";
  • print " --action RT::Action::EscalatePriority \\n";

Rt-devel mailing list
Rt-devel@lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

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?

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@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

-HK

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@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

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:

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: [snip]
Good catch. I introduced this by mistake a couple of weeks ago. I’ve
applied it to 3.0.HEAD, so it will show up in 3.2.1 as well

  • Alex

Networking – one letter away from not working