Hi there, On Tue, 02 Dec 2014, 09:42:43 +0100, Freek de Kruijf wrote:
Op maandag 1 december 2014 17:31:58 schreef Patrick Shanahan:
* Jon Nelson <jnelson-suse@jamponi.net> [12-01-14 13:24]:
I have to say, on the laptops which run KDE, using network manager is *great*. It has stabilized and works very well. Not being able to have more than one VPN is a problem, but it's a bit on the esoteric side.
That said, wicked has caused me some real pain.
On my non-GUI machines (servers, etc), wicked has been a real problem:
- No support for if-up/if-down/if-services
openSUSE 13.2
# ifup wlp3s0 wlp3s0 up
rpm -qf `which ifup` wicked-service-0.6.12-1.1.x86_64
??
Easy. The file ifup is present in the package wicked-service. So you still can use the commands ifup, ifdown and other if... commands. Maybe the problem is the dash (-) in the above mentioned commands.
"normal" ifup/ifdown works, that's not the issue. wicked's ifup and ifdown however have silently removed support for scripts which are executed when an interface comes up or goes down. These scripts are typically stored in the /etc/sysconfig/network/if-{up,down}.d/ directories. Here is an excerpt from the ifup manual page on 13.1: /etc/sysconfig/network/if-{up,down}.d/ Scripts in these directories will be executed when any interface is started, if-up.d, and when any interface is stopped, if-down.d. They have to be exe- cutable and may also be binary. The execution of these programs is controlled by the variables GLOBAL_POST_UP_EXEC and GLOBAL_PRE_DOWN_EXEC in the network configuration file /etc/sysconfig/network/config These are not interface spe- cific, and can have any name. If you need interface/configfile specific scripts to be executed have a look at PRE_UP_SCRIPT, POST_UP_SCRIPT, PRE_DOWN_SCRIPTand POST_DOWN_SCRIPT. HTH, cheers. l8er manfred