The command stop was linked to the SIGSTOP of
processes. It came in deprecation. Keeping it
is confusing.
Bug-AGL: SPEC-2247
Bug-AGL: SPEC-2248
Change-Id: Iad6af317ba4fd6466f306ef493ef8dd62d8de778
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
send terminate "$i"
;;
- stop|pause)
- i=$2
- send pause "$i"
- ;;
-
- resume|continue)
- i=$2
- send resume "$i"
- ;;
-
state|status)
i=$2
send state "$i"
kill rid
terminate rid terminate the running instance rid
- stop rid
- pause rid pause the running instance rid
-
- resume rid
- continue rid continue the previously paused rid
-
status rid
state rid get status of the running instance rid