Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Feb 2015 12:41:54 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 197705] Periodic configuration prints unneeded header when show_sucess="no"
Message-ID:  <bug-197705-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197705

            Bug ID: 197705
           Summary: Periodic configuration prints unneeded header when
                    show_sucess="no"
           Product: Base System
           Version: 9.3-RELEASE
          Hardware: i386
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: misc
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: frank@deze.org

I have a very small issue in the configuration of the periodic framework.

If I configure the following in periodic.conf

daily_show_success="NO"
daily_show_info="YES"
daily_show_badconfig="YES"

security_show_success="NO"
security_show_info="YES"
security_show_badconfig="YES"

daily_status_security_enable="YES"
daily_status_security_inline="YES"

I would expect that I will not get a daily email when there is no warning or
error. 

However, I get every day an empty email with the following line:

#### Start of email ####
Return-Path: <root@xxx>
X-Original-To: root@xxx
To: root@xxx
Subject: xxx daily run output
Date: Mon, 16 Feb 2015 03:02:00 +0100 (CET)


Security check:

-- End of daily output --
#### End of email ####


It would be much nicer if the line "Security check:" was not printed (and hence
no email was send) when there are no security events to report.

In my opinion the daily_show_success="NO" and security_show_success="NO"
options should mean that this empty header is not to be printed.

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-197705-8>