http://bugzilla.opensuse.org/show_bug.cgi?id=907215
Marius Tomaschewski changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mt@suse.com
Flags|needinfo?(wicked-maintainer |
|s@suse.de) |
--- Comment #6 from Marius Tomaschewski ---
An initial pre/post-up/down custom script support is going into testing at:
https://github.com/openSUSE/wicked/pull/537
Currently the PRE_UP_SCRIPT,POST_UP_SCRIPT,PRE_DOWN_SCRIPT,POST_DOWN_SCRIPT
ifcfg variables are used and can be set to:
* systemd: scheme:
POST_UP_SCRIPT="systemd:my-post-up-eth1.service"
or using a service template with interface name argument:
POST_UP_SCRIPT="systemd:my-post-up@.service"
pre-up,post-up cause to start, pre-down,post-down to stop the service.
* wicked: scheme:
POST_UP_SCRIPT="wicked:my-script"
POST_UP_SCRIPT="wicked:/path/to/my-script"
The /etc/wicked/scripts directory is prepended to relative paths.
When the path does not point to an executable but to a directory,
all executables in it are called (/etc/wicked/scripts/my-script-up/*)
as "$script $action $ifname" (my-script post-up eth0).
* compat:suse: scheme, which is currently used as default for ifcfg:
POST_UP_SCRIPT="compat:suse:my-script"
POST_UP_SCRIPT="compat:suse:/path/to/my-script"
also:
POST_UP_SCRIPT="my-script"
POST_UP_SCRIPT="/path/to/my-script"
POST_UP_SCRIPT="if-up.d/22-test.sh"
Similar to wicked scheme, but prepending /etc/sysconfig/network/scripts
and /etc/sysconfig/network and using the old argument scheme of:
"$SCRIPT $CONFIG $INTERFACE ${OPTIONS:+-o $OPTIONS}"
with CONFIG==INTEFACE and action (post-up) in OPTIONS.
--
You are receiving this mail because:
You are on the CC list for the bug.
