* Dave Plater <dplater.list@gmail.com> [10-29-18 08:33]:
On 29/10/2018 14:21, Carlos E. R. wrote:
On 29/10/2018 13.12, Per Jessen wrote:
Carlos E. R. wrote:
Well, it is running. No problem with it that I can see.
That is when it is started manually - the problem is $SUBJ.
Then check the logs after boot. That's the only way to know what happened.
All I can find, the two bottom lines are when I started it manually. # journalctl -b|grep firewalld Oct 29 11:46:54 Arbuthnot systemd[1]: is_symlink_with_known_name(firewalld.service, dbus-org.fedoraproject.FirewallD1.service) → 1 Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic firewall daemon... Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic firewall daemon.
maybe if I uninstall it and install it again. Dave P
there is configuration in yast system->/etcsysconfig Editor->network->general->firewall # With this variable you can determine if the SuSEfirewall when enabled # should get started when network interfaces are started. FIREWALL="yes" it doesn't start the firewall on system startup but when the network interface is started. you should not need the firewall before then as there is no access to your computer except what you have physically allowed. does that provide the information you seek? if not and you still want your firewall running on boot, you will have to construct a service script to do that. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org