SCIENTIFIC-LINUX-USERS Archives

June 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Sommerseth <[log in to unmask]>
Reply To:
David Sommerseth <[log in to unmask]>
Date:
Tue, 16 Jun 2015 07:02:14 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
On 16 June 2015 07:52:05 CEST, ToddAndMargo <[log in to unmask]> wrote:
>Hi All,
>
>What is the difference between these two commands?
>
>     # 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. 

>     # systemctl mask firewalld

This will completely disable the service and it cannot be started by systemd at all, no matter which approach is used.  (Well, you may use iptables-restore or iptables commands directly, but that is outside of systemd's control.)


--
kind regards,

David Sommerseth

ATOM RSS1 RSS2