From 55d89da47d81b4a66fab966620dacd213b6ca20e Mon Sep 17 00:00:00 2001 From: Dirk Koopman Date: Thu, 5 Jan 2017 12:07:12 +0000 Subject: [PATCH] improve rbn.pl --- UPGRADE.mojo | 2 +- perl/rbn.pl | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/UPGRADE.mojo b/UPGRADE.mojo index 378b943f..6e5047fb 100644 --- a/UPGRADE.mojo +++ b/UPGRADE.mojo @@ -11,7 +11,7 @@ the node. I am also using a modern, event driven, web socket "manager" called Mo which is considerably more efficient than what went before (but is not necessary for small nodes). There are some 200-400 user nodes out there that will definitely see the difference in terms of both CPU usage and general responsiveness. Using Mojolicious also brings the -tantalising possibility of grafting on a web frontend, as it where, to the "side" of a +tantalising possibility of grafting on a web frontend, as it were, to the "side" of a DXSpider node. But serious work on this won't start until we have a stable base to work on. Apart from anything else there will, almost certainly, need to be some internal data structure reorganisation before a decent web frontend could be constructed. diff --git a/perl/rbn.pl b/perl/rbn.pl index eb2c743e..670caed5 100755 --- a/perl/rbn.pl +++ b/perl/rbn.pl @@ -30,12 +30,13 @@ my $help = 0; my $man = 0; my $mycall; +#Getopt::Long::Configure( qw(auto_abbrev) ); GetOptions('host=s' => \$host, 'port=i' => \$port, 'debug' => \$dbg, 'rbn' => \$showrbn, 'stats' => \$showstats, - 'repeattime=i' => sub { $minspottime = $_[1] * 60 }, + 'repeattime|rt=i' => sub { $minspottime = $_[1] * 60 }, 'want=s' => sub { my ($name, $value) = @_; $wantcw = $wantrtty = $wantpsk = $wantbeacon = 0; @@ -47,7 +48,7 @@ GetOptions('host=s' => \$host, } }, 'help|?' => \$help, - man => \$man, + 'man' => \$man, '<>' => sub { $mycall = shift }, ) or pod2usage(2); -- 2.34.1