Chapter 2. Configuring KWatchGnuPG

WatchGnuPG is the process that actually monitors the logging socket for activity and formats the lines as seen in the KWatchGnuPG text view. Settings in this group are passed down to the backend using the GPGConf mechanism.

Executable contains the path to the WatchGnuPG application. If WatchGnuPG is in your $PATH, you can keep the default watchgnupg. If WatchGnuPG is not in your $PATH, or if you have more than one version installed, enter the absolute filename of the watchgnupg executable here.

Socket contains the socket that WatchGnuPG should listen on. A change here is distributed to all GnuPG backend modules using GPGConf, so you don't need to change this setting if your GnuPG config files have another log-file set.

Default log level determines the amount of logging information returned by the backend modules. See the WatchGnuPG documentation for what level includes which information. A change here is distributed to all GnuPG backend modules using GPGConf, so you don't need to change this setting if your GnuPG config files have another log-level set.

Here, you can configure the size of the history buffer, i.e. the number of log lines that is kept. If more lines have been emitted by the GnuPG backend since the last clearance of the history, then the oldest lines are discarded until there is enough room for the new lines again.

You can disable the history size limit by clicking Set Unlimited. Note, however, that KWatchGnuPG's memory consumption will grow with the number of lines it currently displays. If you use an unlimited history size, then make sure to run KWatchGnuPG only for short operations, or regularly clear the history manually.