id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
256	LogmonMarkSeverity using the wrong config handler	rainer	rainer	"
As pointed out by Sean Chittenden, the !LogmonMarkSeverity directive uses the wrong
handler, and hence does nothing. In src/sh_log_check.c:1302:

{{{
    {
        N_(""logmonsavedir""),
        sh_logmon_set_save_dir,
    },
    {
        N_(""logmonmarkseverity""),
        sh_logmon_set_save_dir,
    },
}}}"	defect	closed	major	2.8.5	main		fixed