On Sun, 23 Aug 2015 00:28, Bjoern Voigt <bjoernv@...> wrote:
Carlos E. R. wrote:
Please change the subject line so that it doesn't say "systemd", or the automatic mail filters vetoes the post :-(
On 2015-08-21 12:59, Bjoern Voigt wrote:
Carlos E. R. wrote: # insserv SuSEfirewall2 Warning: /etc/init.d/SuSEfirewall2 is masked by /usr/lib/systemd/system/SuSEfirewall2.service. Try 'chkconfig SuSEfirewall2 on' instead can't open SuSEfirewall2: No such file or directory at /usr/sbin/insserv line 80.
I'm unsure, but maybe you have to change directory to /etc/init.d
Wait. There is no firewall script there. That's the problem. Must be another name. No, there isn't any SuSEfirewall2 script in /etc/init.d. systemctl seems to search /etc/init.d first and continues with /usr/lib/systemd/system. /usr/local/lib/systemd/system/SuSEfirewall2.service exists.
Here is an ltrace-excerpt: ...
Just to make sure it is not a'trivial' error, what is the output of "rpm --verify SuSEfirewall2" ? Only one line is OK, and that is for the '/etc/sysconfig/SuSEfirewall2' file, e.g.: [output] S.5....T. c /etc/sysconfig/SuSEfirewall2 [/output] the service files should be in '/usr/lib/systemd/system/': /usr/lib/systemd/system/SuSEfirewall2.service /usr/lib/systemd/system/SuSEfirewall2_init.service when 'enabled', there are links to these files in '/etc/systemd/' /etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service /etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service and the called executeable resides in '/usr/sbin/': /usr/sbin/SuSEfirewall2 The 'helper scripts' are in '/etc/sysconfig/scripts/' /etc/sysconfig/scripts/SuSEfirewall2-* - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org