On Thu, 23 Jan 2014 14:17:25 -0500
Robert Moskowitz wrote:
> Did it, now to wait until the next logwatch run.
>
>
you can force it to run with either
running "sh /etc/cron.daily/0logwatch"
or run-parts /etc/cron.daily
(re-runs all the daily jobs in the that dir)
___
Regards,
Frank
www.fr
On 01/23/2014 01:55 PM, Daniel J Walsh wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2014 01:54 PM, Robert Moskowitz wrote:
On 01/23/2014 08:38 AM, Daniel J Walsh wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 01/22/2014 11:07 PM, Robert Moskowitz wrote:
I am seeing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2014 01:54 PM, Robert Moskowitz wrote:
>
> On 01/23/2014 08:38 AM, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 01/22/2014 11:07 PM, Robert Moskowitz wrote:
>>> I am seeing the following errors via "journal
On 01/23/2014 08:38 AM, Daniel J Walsh wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/2014 11:07 PM, Robert Moskowitz wrote:
I am seeing the following errors via "journalctl |grep logwatch":
I had performed the following selinux policy:
On 01/06/2014 08:14 AM, Daniel J Walsh w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/2014 11:07 PM, Robert Moskowitz wrote:
> I am seeing the following errors via "journalctl |grep logwatch":
>
> Jan 22 03:37:14 lx120e.htt-consult.com setroubleshoot[11102]: dbus
> avc(node=lx120e.htt-consult.com type=AVC msg=audit(1390390627
