Comment 11 for bug 1349949

Note that in a customer site with HA=3 and ~100 machines we are seeing syslog grow to around 3.6GB before it gets rotated (presumably daily?). Which means that we end up consuming 7.2GB just before the second rotation, and most of it is going to be these fairly useless logging output.
I believe we can filter out some of these messages. Ideally with a way to turn that filtering off quickly in case you really do want to debug authentication issues.

Also, it would be good to know why we are authenticating so often. It certainly seems far too often.