Hi,
>> I have been receiving "logger: socket /dev/log: Connection refused"
>> from the 0anacron script every hour since recently doing an update.
>> I've enabled tracing in the script with -x to try and isolate where
>> it's coming from, but nothing obvious is produced.
>>
>> I've even disabled se
On 08/12/15 05:24, Alex wrote:
> Hi,
>
> I have been receiving "logger: socket /dev/log: Connection refused"
> from the 0anacron script every hour since recently doing an update.
> I've enabled tracing in the script with -x to try and isolate where
> it's coming from, but nothing obvious is produce
On 08/11/2015 04:20 PM, Alex wrote:
Yes, thanks. In the past, I've always received a ton of "have you
tried with selinux disabled?" responses, so it was an effort to
pre-empt those emails.
Understood. I've always found the best answer to be "What makes you
think SELinux is involved?"
--
user
Hi,
>> I've even disabled selinux to make sure. Running logger manually as
>> root succeeds as expected.
>
> Disabling SELinux because some random program crashes is nothing more than
> voodoo troubleshooting. If you're not getting alerts about violations, it's
> not a factor.
Yes, thanks. In th
On 08/11/2015 02:24 PM, Alex wrote:
I've even disabled selinux to make sure. Running logger manually as
root succeeds as expected.
Disabling SELinux because some random program crashes is nothing more
than voodoo troubleshooting. If you're not getting alerts about
violations, it's not a fact
Hi,
I have been receiving "logger: socket /dev/log: Connection refused"
from the 0anacron script every hour since recently doing an update.
I've enabled tracing in the script with -x to try and isolate where
it's coming from, but nothing obvious is produced.
I've even disabled selinux to make sur
