Currently Being ModeratedJan 26, 2013 5:47 AM (in response to marc herman)
You've provided a very explaination of the what you're looking at and what you've tried, but is there a particular reason why you're looking to suppress these messages? If it's because those log entries are overruning the blasted mail-slot-sized log windows available in the Server Admin.app tool, it's usually easier to review or grep or otherwise directly process the raw logs in the /var/log directory.
Currently Being ModeratedJan 26, 2013 9:32 AM (in response to MrHoffman)
I guess I can live with this secure.log spam. It's just that it seems superfluous, erratic and, well, junk. As I went to check the log once more it is now again reporting at 300 secs intervals. A log with a life of its own, -should I consider it quaint and just move on?
Currently Being ModeratedJan 26, 2013 1:39 PM (in response to marc herman)
I would. (Ignore it.) OS X logging has long had this misfeature; various versions of applications have been far too chatty, others have log ominous messages that are harmless, and there's the occasional innocuous-nasty message logged.
If this particular message bugs you — I have several similar "favorites" in my own logs — add it onto a grep --invert-match pattern or such, and filter it out of the logs before you review them. When you're running OS X or another Unix box in production, message filters based on grep or similar are used to reduce the chatter, and also to flag the nasty messages.
Currently Being ModeratedJan 26, 2013 1:53 PM (in response to MrHoffman)
I bow my head and quietly resolve to store this in a little box, labelled "True To Life".