+1 for now. -re On Mon, Sep 11, 2017 at 8:36 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > On 09/11/2017 01:08 PM, R P Herrold wrote: >> On Mon, 11 Sep 2017, Kevin Fenzi wrote: >> >>> At least for now I would like to just weed all of them out: >> >> I suspect although I do not see a pointer to the 'auditd' log >> clutter problem, that it is similar to this: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1451469 > > Somewhat similar, although we don't use logwatch anywhere. > > Instead we are getting tons of messages from builders about adding a > mockbuild user to the mock chroot, and adding a group and a homedir, and > ... so it's like 50 messages per build. :) > >> Rather than putting a piece of black tape over the 'check >> engine' light, adding a regex seems a more proper fix. >> Without a ticket, and without a bug, it will just recur and >> get glossed over for (ahem) 'opaque' reasons >> >> -- Russ herrold > > Well, we are currently in freeze, so I want to not be disruptive. The > proper fix I suppose is to split out all these audit messages to another > log we can look at only if we need to audit something. > > kevin > > > > > > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
