[opensuse-factory] disable wickedd-dhcp* - openSUSE Factory - openSUSE Mailing Lists

newer
[opensuse-factory] Missing program...

[opensuse-factory] disable wickedd-dhcp*

older
[opensuse-factory] New Tumbleweed...

Michael Ströder

18 Jan 2017 18 Jan '17

17:44

My systems all have static network configuration (wicked) and therefore they don't need DHCP / auto-IP client(s) running. But still these processes are always started: /usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground /usr/lib/wicked/bin/wickedd-auto4 --systemd --foreground /usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground What's official way to completely disable these wicked services? Ciao, Michael.

Attachments:

smime.p7s (application/pkcs7-signature — 3.7 KB)

Reply

Sign in to reply online Use email software

Show replies by date

Patrick Shanahan

18 Jan 18 Jan

17:57

* Michael Ströder [01-18-17 12:46]:

My systems all have static network configuration (wicked) and therefore they don't need DHCP / auto-IP client(s) running. But still these processes are always started:

/usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground /usr/lib/wicked/bin/wickedd-auto4 --systemd --foreground /usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground

What's official way to completely disable these wicked services?

locate service |grep dhcp /etc/sysconfig/SuSEfirewall2.d/services/dhcp-server /etc/sysconfig/SuSEfirewall2.d/services/dhcp6-server /etc/sysconfig/SuSEfirewall2.d/services/dnsmasq-dhcp /etc/systemd/system/wickedd.service.wants/wickedd-dhcp4.service /etc/systemd/system/wickedd.service.wants/wickedd-dhcp6.service /usr/lib/systemd/system/wickedd-dhcp4.service /usr/lib/systemd/system/wickedd-dhcp6.service /usr/share/logwatch/default.conf/services/dhcpd.conf /usr/share/logwatch/scripts/services/dhcpd 12:54 Crash: ~ # systemctl status wickedd-dhcp6.service ● wickedd-dhcp6.service - wicked DHCPv6 supplicant service Loaded: loaded (/usr/lib/systemd/system/wickedd-dhcp6.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2017-01-15 08:57:04 EST; 3 days ago Main PID: 10288 (wickedd-dhcp6) Tasks: 1 (limit: 512) CGroup: /system.slice/wickedd-dhcp6.service └─10288 /usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground

I would guess: systemctl disable wickedd-dhcp6.service I didn't look for the others. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Reply

Sign in to reply online Use email software

Michael Ströder

18:16

Patrick Shanahan wrote:

* Michael Ströder [01-18-17 12:46]:

...
My systems all have static network configuration (wicked) and therefore they don't need DHCP / auto-IP client(s) running. But still these processes are always started:

/usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground /usr/lib/wicked/bin/wickedd-auto4 --systemd --foreground /usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground

What's official way to completely disable these wicked services?

I would guess: systemctl disable wickedd-dhcp6.service

That's what I've tried *before* asking. But I'm asking for a persistent solution. Why I'm asking here: tw1:~ # systemctl status wickedd-dhcp6.service ● wickedd-dhcp6.service - wicked DHCPv6 supplicant service Loaded: loaded (/usr/lib/systemd/system/wickedd-dhcp6.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2017-01-18 17:58:35 CET; 1h 10min ago Main PID: 415 (wickedd-dhcp6) Tasks: 1 (limit: 512) CGroup: /system.slice/wickedd-dhcp6.service └─415 /usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground Jan 18 17:58:35 tw1 systemd[1]: Starting wicked DHCPv6 supplicant service... Jan 18 17:58:35 tw1 systemd[1]: Started wicked DHCPv6 supplicant service. tw1:~ # systemctl disable wickedd-dhcp6.service Removed symlink /etc/systemd/system/dbus-org.opensuse.Network.DHCP6.service. tw1:~ # systemctl stop wickedd-dhcp6.service tw1:~ # systemctl status wickedd-dhcp6.service ● wickedd-dhcp6.service - wicked DHCPv6 supplicant service Loaded: loaded (/usr/lib/systemd/system/wickedd-dhcp6.service; disabled; vendor preset: disabled) Active: inactive (dead) since Wed 2017-01-18 19:08:49 CET; 1s ago Main PID: 415 (code=exited, status=0/SUCCESS) Jan 18 17:58:35 tw1 systemd[1]: Starting wicked DHCPv6 supplicant service... Jan 18 17:58:35 tw1 systemd[1]: Started wicked DHCPv6 supplicant service. Jan 18 19:08:49 tw1 systemd[1]: Stopping wicked DHCPv6 supplicant service... Jan 18 19:08:49 tw1 systemd[1]: Stopped wicked DHCPv6 supplicant service. Looks good so far. But after *reboot* it says "disabled" and is "running" even though all my ifcfg* files have BOOTPROTO='static': tw1:~ # systemctl status wickedd-dhcp6.service ● wickedd-dhcp6.service - wicked DHCPv6 supplicant service Loaded: loaded (/usr/lib/systemd/system/wickedd-dhcp6.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2017-01-18 19:10:34 CET; 1min 1s ago Main PID: 431 (wickedd-dhcp6) Tasks: 1 (limit: 512) CGroup: /system.slice/wickedd-dhcp6.service └─431 /usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground Jan 18 19:10:33 tw1 systemd[1]: Starting wicked DHCPv6 supplicant service... Jan 18 19:10:34 tw1 systemd[1]: Started wicked DHCPv6 supplicant service. Ciao, Michael.

Reply

Sign in to reply online Use email software

Andrei Borzenkov

18:23

18.01.2017 21:16, Michael Ströder пишет:

Patrick Shanahan wrote:

...
* Michael Ströder [01-18-17 12:46]:

...
My systems all have static network configuration (wicked) and therefore they don't need DHCP / auto-IP client(s) running. But still these processes are always started:

/usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground /usr/lib/wicked/bin/wickedd-auto4 --systemd --foreground /usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground

What's official way to completely disable these wicked services?

I would guess: systemctl disable wickedd-dhcp6.service

That's what I've tried *before* asking. But I'm asking for a persistent solution.

Why I'm asking here:

tw1:~ # systemctl status wickedd-dhcp6.service ● wickedd-dhcp6.service - wicked DHCPv6 supplicant service Loaded: loaded (/usr/lib/systemd/system/wickedd-dhcp6.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2017-01-18 17:58:35 CET; 1h 10min ago Main PID: 415 (wickedd-dhcp6) Tasks: 1 (limit: 512) CGroup: /system.slice/wickedd-dhcp6.service └─415 /usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground

Jan 18 17:58:35 tw1 systemd[1]: Starting wicked DHCPv6 supplicant service... Jan 18 17:58:35 tw1 systemd[1]: Started wicked DHCPv6 supplicant service. tw1:~ # systemctl disable wickedd-dhcp6.service Removed symlink /etc/systemd/system/dbus-org.opensuse.Network.DHCP6.service. tw1:~ # systemctl stop wickedd-dhcp6.service tw1:~ # systemctl status wickedd-dhcp6.service ● wickedd-dhcp6.service - wicked DHCPv6 supplicant service Loaded: loaded (/usr/lib/systemd/system/wickedd-dhcp6.service; disabled; vendor preset: disabled) Active: inactive (dead) since Wed 2017-01-18 19:08:49 CET; 1s ago Main PID: 415 (code=exited, status=0/SUCCESS)

Jan 18 17:58:35 tw1 systemd[1]: Starting wicked DHCPv6 supplicant service... Jan 18 17:58:35 tw1 systemd[1]: Started wicked DHCPv6 supplicant service. Jan 18 19:08:49 tw1 systemd[1]: Stopping wicked DHCPv6 supplicant service... Jan 18 19:08:49 tw1 systemd[1]: Stopped wicked DHCPv6 supplicant service.

Looks good so far.

But after *reboot* it says "disabled" and is "running" even though all my ifcfg* files have BOOTPROTO='static':

It is pulled in by wickedd.service. If you want to completely disable it, you need to mask it (although I do not know how wickedd will react to it). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Reply

Sign in to reply online Use email software

Jan Engelhardt

21:42

On Wednesday 2017-01-18 18:44, Michael Ströder wrote:

My systems all have static network configuration (wicked) and therefore they don't need DHCP / auto-IP client(s) running. But still these processes are always started:

If you are not using NetworkManager, then: Can I interest you in switching to systemd-networkd? :-) It's a daemon that does not even run if there are no actionable events (which there are not in a fully staticly-configured system). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Reply

Sign in to reply online Use email software

2667

Age (days ago)

2667

Last active (days ago)

Download

4 comments

4 participants

tags

participants (4)

Andrei Borzenkov
Jan Engelhardt
Michael Ströder
Patrick Shanahan