On 01/01/17 01:28, jdow wrote:
> 
> Obviously I really do NOT want firewalld to run. This is, apparently,
> usually done using "systemctl mask firewalld". Unfortunately this leaves
> divots all over the logs about systemctl not being able to bring up
> /dev/null er firewalld. That seems "unfriendly" to say the least. (And
> it seems there is no "friendly" way to undo the "systemctl mask"
> command, at least for firewalld.

# yum erase firewalld
# yum install iptables-services

Now you're back to the old way of firewall management.


-- 
kind regards,

David Sommerseth