> What I was asking for is information on the log levels like "127", "128".
Ah sorry, this is a glib thing. They're defined by GLogLevelFlags.
typedef enum
{
/* log flags */
G_LOG_FLAG_RECURSION = 1 << 0,
G_LOG_FLAG_FATAL = 1 << 1,
/* GLib log levels */
G_LOG_LEVEL_ERROR = 1 << 2, /* always fatal */
G_LOG_LEVEL_CRITICAL = 1 << 3,
G_LOG_LEVEL_WARNING = 1 << 4,
G_LOG_LEVEL_MESSAGE = 1 << 5,
G_LOG_LEVEL_INFO = 1 << 6,
G_LOG_LEVEL_DEBUG = 1 << 7,
G_LOG_LEVEL_MASK = ~(G_LOG_FLAG_RECURSION |
G_LOG_FLAG_FATAL)
} GLogLevelFlags;
Mostly each level corresponds to a particular log function.
G_LOG_LEVEL_DEBUG includes g_debug messages, G_LOG_LEVEL_INFO includes
g_info messages, etc.
>
> Message I noticed being logged are baisc information like for a status
> change of a task as shown in the example below:
>
> event task:MESSAGE:2015-03-31 08h18.33 CEST:29827: Status of task "xxxxx"
> has changed to Requested
> event task:MESSAGE:2015-03-31 08h18.33 CEST:29827: Task "xxxxx" has been
> requested to start by "user"
These are G_LOG_LEVEL_MESSAGE messages.
>
> I have not found any log information for scheduled scans.
I'll try reproduce.
--
Greenbone Networks GmbH
Neuer Graben 17, 49074 Osnabrueck, Germany | AG Osnabrueck, HR B 202460
Executive Directors: Lukas Grunwald, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
