setenforce notice to dbus, 13 minute delay?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I notice that when I do 'setenforce', dbus is notified. 
But there appears to be a significant delay, e.g., 13-15 minutes,
before dbus logs it.

Is this just log buffer 'flush buffer' timing? Is this to be expected?

thanks,
   tom

Sep 25 10:29:54 fedora kernel: audit(1096133394.349:0): avc:  granted 
{ setenforce } for  pid=4107 exe=/usr/bin/setenforce
scontext=root:sysadm_r:sysadm_t tcontext=system_u:object_r:security_t
tclass=security
<SNIP>
Sep 25 10:43:21 fedora dbus: avc:  received setenforce notice (enforcing=0)
-- 
Tom London

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux