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.
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;
}
},
'help|?' => \$help,
- man => \$man,
+ 'man' => \$man,
'<>' => sub { $mycall = shift },
) or pod2usage(2);