On Tue, Jun 16, 2015 at 3:02 AM, David Sommerseth
<[log in to unmask]> wrote:
> On 16 June 2015 07:52:05 CEST, ToddAndMargo <[log in to unmask]> wrote:
>>
>> # systemctl disable firewalld.service
>
> This avoids the firewalld.service unit to be automatically started during boot. The service may still be started using 'systemctl start ....' or if a service uses socket activation it will also start automatically.
If a unit's disabled but not masked, it can also be started as
dependency of another unit.