From bc5798bad9474460df4943701933c9444f6a2305 Mon Sep 17 00:00:00 2001 From: Carlo von lynX Date: Thu, 28 Jul 2016 13:05:33 +0000 Subject: gnunet-logread with intelligent usage message and proper perldoc --- contrib/gnunet-logread | 89 ++++++++++++++++++++++++++++++++++++++------------ 1 file changed, 68 insertions(+), 21 deletions(-) diff --git a/contrib/gnunet-logread b/contrib/gnunet-logread index 2e54d133f..f58758cb9 100755 --- a/contrib/gnunet-logread +++ b/contrib/gnunet-logread @@ -6,30 +6,19 @@ use strict; use warnings; my $DEFAULT_SOCKET = '/tmp/gnunet-logread-ipc.sock'; -use Getopt::Std; -my (%opts, $name, $ipc, $msg_level, $msg_regex); -getopts ('i:x:n:s:L:m:fh', \%opts); - -die < |& $0 [] - or - $0 [] [] +print STDERR < Include only messages that match . - -x Exclude all messages that match . +use Getopt::Std; +my (%opts, $name, $ipc, $msg_level, $msg_regex); +getopts ('i:x:n:s:L:m:fhq', \%opts); - Options to enable message passing to IPC socket: - -n Name of this component to use for IPC logging. - -s Default = $DEFAULT_SOCKET - -L Minimum level of messages to pass on. - Log levels: NONE, ERROR, WARNING, INFO, DEBUG. - -m Only pass messages matching a regular expression. -X +use Pod::Usage qw( pod2usage ); +die pod2usage if $opts{h}; use POSIX qw(mkfifo); @@ -150,3 +139,61 @@ sub perform { print; } +__END__ + +=pod + +=head1 NAME + +gnunet-logread - a GNUnet log analyzer, colorizer and aggregator + +=head1 SYNOPSIS + + |& $0 [] + or + $0 [] [] + + Options: + -f Follow input from IPC FIFO socket. + + Regular screen output options: + -i Include only messages that match . + -x Exclude all messages that match . + -q Quiet: Do not show usage advice to new users. + + Options to forward messages to the IPC FIFO socket: + -n Name of the component we are forwarding messages for. + -s Default = $DEFAULT_SOCKET + -L Minimum level of messages to forward: + Log levels: NONE, ERROR, WARNING, INFO, DEBUG. + -m Only forward messages matching a regular expression. + + See 'perldoc gnunet-logread' for a longer explanation. + +=head1 MOTIVATION + +GNUnet debug logs are a tedious read, but given a complex system that we +cannot run all parts of in a debugger all the time, some gathering and +structuring of events and message passing is useful. + +At first, this tool simply makes logs easier to read. Both if viewed in +real-time or taken from disk. Then it also allows to extract all message +passing events from it and forward them to a special process that aggregates +all message passing events and therefore helps you make sense of all the +inter-process communication (IPC) happening between the various pieces of +the GNUnet system beast. + +That master process is simply an extra gnunet-logread that you run in a +separate window and adorn it with the '-f' flag. The submitting processes +instead need to be given a '-n' flag. That is because from the GNUnet logs +it isn't clear which process events belong too. For example you may be +having events taking place in the 'util' subsystem of gnunet-psyc-service +just as much as in the 'util' subsystem of gnunet-multicast-service. In +order to make sense of them it is necessary to manually add that info. This +could be remedied by extending the semantics of the GNUNET_log facility +instead, but that is still subject to further consideration. + +=head1 AUTHORS + +tg & lynX + -- cgit v1.2.3