mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-02 22:46:30 +02:00
Fix regression in logging.
Add a registry key to enable catch-all remote debugging for W32. Replace more stdio stuff by estream.
This commit is contained in:
parent
7e752a4208
commit
34dde96669
20 changed files with 423 additions and 294 deletions
|
@ -1,3 +1,7 @@
|
|||
2010-08-18 Werner Koch <wk@g10code.com>
|
||||
|
||||
* tools.texi (watchgnupg): Add examples section.
|
||||
|
||||
2010-06-10 Werner Koch <wk@g10code.com>
|
||||
|
||||
* Makefile.am (gnupg_TEXINFOS): Add dirmngr.texi.
|
||||
|
|
|
@ -42,11 +42,12 @@ GnuPG comes with a couple of smaller tools:
|
|||
@end ifset
|
||||
|
||||
@mansect description
|
||||
Most of the main utilities are able to write their log files to a
|
||||
Unix Domain socket if configured that way. @command{watchgnupg} is a simple
|
||||
listener for such a socket. It ameliorates the output with a time
|
||||
stamp and makes sure that long lines are not interspersed with log
|
||||
output from other utilities.
|
||||
Most of the main utilities are able to write their log files to a Unix
|
||||
Domain socket if configured that way. @command{watchgnupg} is a simple
|
||||
listener for such a socket. It ameliorates the output with a time stamp
|
||||
and makes sure that long lines are not interspersed with log output from
|
||||
other utilities. This tool is not available for Windows.
|
||||
|
||||
|
||||
@noindent
|
||||
@command{watchgnupg} is commonly invoked as
|
||||
|
@ -70,6 +71,10 @@ This starts it on the current terminal for listening on the socket
|
|||
@opindex force
|
||||
Delete an already existing socket file.
|
||||
|
||||
@item --tcp @var{n}
|
||||
Instead of reading from a local socket, listen for connects on TCP port
|
||||
@var{n}.
|
||||
|
||||
@item --verbose
|
||||
@opindex verbose
|
||||
Enable extra informational output.
|
||||
|
@ -84,6 +89,41 @@ Display a brief help page and exit.
|
|||
|
||||
@end table
|
||||
|
||||
@noindent
|
||||
@mansect examples
|
||||
@chapheading Examples
|
||||
|
||||
@example
|
||||
$ watchgnupg --force /home/foo/.gnupg/S.log
|
||||
@end example
|
||||
|
||||
This waits for connections on the local socket
|
||||
@file{/home/foo/.gnupg/S.log} and shows all log entries. To make this
|
||||
work the option @option{log-file} needs to be used with all modules
|
||||
which logs are to be shown. The value for that option must be given
|
||||
with a special prefix (e.g. in the conf file):
|
||||
|
||||
@example
|
||||
log-file socket:///home/foo/.gnupg/S.log
|
||||
@end example
|
||||
|
||||
For debugging purposes it is also possible to do remote logging. Take
|
||||
care if you use this feature because the information is send in the
|
||||
clear over the network. Use this syntax in the conf files:
|
||||
|
||||
@example
|
||||
log-file tcp://192.168.1.1:4711
|
||||
@end example
|
||||
|
||||
You may use any port and not just 4711 as shown above; only IP addresses
|
||||
are supported (v4 and v6) and no host names. You need to start
|
||||
@command{watchgnupg} with the @option{tcp} option. Note that under
|
||||
Windows the registry entry @var{HKCU\Software\GNU\GnuPG:DefaultLogFile}
|
||||
can be used to change the default log output from @code{stderr} to
|
||||
whatever is given by that entry. However the only useful entry is a TCP
|
||||
name for remote debugging.
|
||||
|
||||
|
||||
@mansect see also
|
||||
@ifset isman
|
||||
@command{gpg}(1),
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue