File: gpgme.info, Node: Additional Logs, Prev: Locale, Up: Context Attributes 7.4.15 Additional Logs ---------------------- Additional logs can be associated with a context. These logs are engine specific and can be be obtained with ‘gpgme_op_getauditlog’. -- Function: gpgme_error_t gpgme_op_getauditlog (gpgme_ctx_t CTX, gpgme_data_t OUTPUT, unsigned int FLAGS) SINCE: 1.1.1 The function ‘gpgme_op_getauditlog’ is used to obtain additional logs as specified by FLAGS into the OUTPUT data. If The function returns the error code ‘GPG_ERR_NO_ERROR’ if a log could be queried from the engine, and ‘GPG_ERR_NOT_IMPLEMENTED’ if the log specified in FLAGS is not available for this engine. If no log is available ‘GPG_ERR_NO_DATA’ is returned. The value in FLAGS is a bitwise-or combination of one or multiple of the following bit values: ‘GPGME_AUDITLOG_DIAG’ SINCE: 1.11.2 Obtain diagnostic output which would be written to ‘stderr’ in interactive use of the engine. This can be used to provide additional diagnostic information in case of errors in other operations. Note: If log-file has been set in the configuration the log will be empty and ‘GPG_ERR_NO_DATA’ will be returned. Implemented for: ‘GPGME_PROTOCOL_OpenPGP’ ‘GPGME_AUDITLOG_DEFAULT’ SINCE: 1.11.2 This flag has the value 0 for compatibility reasons. Obtains additional information from the engine by issuing the ‘GETAUDITLOG’ command. For ‘GPGME_PROTOCOL_CMS’ this provides additional information about the X509 certificate chain. Implemented for: ‘GPGME_PROTOCOL_CMS’ ‘GPGME_AUDITLOG_HTML’ SINCE: 1.1.1 Same as ‘GPGME_AUDITLOG_DEFAULT’ but in HTML. Implemented for: ‘GPGME_PROTOCOL_CMS’ -- Function: gpgme_error_t gpgme_op_getauditlog_start (gpgme_ctx_t CTX, gpgme_data_t OUTPUT, unsigned int FLAGS) SINCE: 1.1.1 This is the asynchronous variant of ‘gpgme_op_getauditlog’.