Starting an already installed app seems to work:
qemux86-64:~# afm-util list |grep \"id\" "id":"mediaplayer@0.1", "id":"settings@0.1", "id":"dashboard@0.1", "id":"homescreen@0.1", "id":"phone@0.1", "id":"hvac@0.1", "id":"launcher@0.1", "id":"poi@0.1", "id":"mixer@5.99", "id":"navigation@0.1", "id":"radio@0.1", qemux86-64:~# afm-util status dashboard@0.1 ERROR: not-found qemux86-64:~# afm-util start dashboard@0.1 1703 qemux86-64:~# afm-util status dashboard@0.1 { "runid":1703, "pids":[ 1703 ], "state":"running", "id":"dashboard@0.1" }
But then trying to stop it does not seem to work:
qemux86-64:~# afm-util stop 1703 ERROR: not-found qemux86-64:~# afm-util stop dashboard@0.1 ERROR: not-found
Removing it appears to be successful:
qemux86-64:~# afm-util remove dashboard@0.1 null qemux86-64:~# afm-util status dashboard@0.1 ERROR: not-found
But the process is still running:
qemux86-64:~# pgrep dashboard 1703 1704
@Jan-Simon Moeller This issue is closed as a duplicate of https://lf-automotivelinux.atlassian.net/browse/SPEC-1872#icft=SPEC-1872. Please use that issue to track.
@jose bollo can we use the systemd units for stopping / starting so @Kevin Hilman can complete the basic app lifecycle tests in a lava testdefinition
(e.g. dl wgt, stop old, uninstall old, install new, start new, check status)
Can you provide some details about the unit naming pattern ?
Duplicate of some tasks being taken care of in https://lf-automotivelinux.atlassian.net/browse/SPEC-1872#icft=SPEC-1872
I created the https://lf-automotivelinux.atlassian.net/browse/SPEC-1872 to track specially that improvement. So it is probably already fixed upstream and in flounder. Thus I propose to close with "won't fix"
Yes, I misread the comment from @jose bollo. Re-opened.
Starting an already installed app seems to work:
qemux86-64:~# afm-util list |grep \"id\" "id":"mediaplayer@0.1", "id":"settings@0.1", "id":"dashboard@0.1", "id":"homescreen@0.1", "id":"phone@0.1", "id":"hvac@0.1", "id":"launcher@0.1", "id":"poi@0.1", "id":"mixer@5.99", "id":"navigation@0.1", "id":"radio@0.1", qemux86-64:~# afm-util status dashboard@0.1 ERROR: not-found qemux86-64:~# afm-util start dashboard@0.1 1703 qemux86-64:~# afm-util status dashboard@0.1 { "runid":1703, "pids":[ 1703 ], "state":"running", "id":"dashboard@0.1" }
But then trying to stop it does not seem to work:
qemux86-64:~# afm-util stop 1703 ERROR: not-found qemux86-64:~# afm-util stop dashboard@0.1 ERROR: not-found
Removing it appears to be successful:
qemux86-64:~# afm-util remove dashboard@0.1 null qemux86-64:~# afm-util status dashboard@0.1 ERROR: not-found
But the process is still running:
qemux86-64:~# pgrep dashboard 1703 1704