14415 2021-06-01 10:11:15 +0000 Cannot stop weston service on systemd 2021-07-01 15:22:18 +0000 1 1 7 Build System, Metadata & Runtime Runtime build-appliance 3.2.3 All Multiple RESOLVED WONTFIX Medium normal 3.4 1 mb JPEWhacker randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 90540 0 mb 2021-06-01 10:11:15 +0000 Hi everyone. When I build a systemd rootfs/kernel, including weston (core-image-weston), weston comes up fine, but I am not able to stop it. Neither `systemctl stop weston` nor `service weston stop` works. The reason is, that `/etc/init.d/weston` has "killproc weston" inside it - but on systemd `/etc/init.d/weston stop` the call of the init.d file generates a pid which is found by `/bin/pidof weston` also. This means, the "stop" call is killed before it's able to kill weston. My hotfix is the following: ` stop) echo "Stopping Weston" killproc /usr/bin/weston ;; ` But what if you are running weston on multiple VT's? Wouldn't it be better if weston service would leave a pid and we could kill exactly that pid? Best Regards Markus Bauer 90570 1 JPEWhacker 2021-06-03 15:14:30 +0000 What version of Yocto are you using? The latest versions have a dedicated systemd service for dealing with weston, so that should be used instead of the sysvinit scripts. 90585 2 mb 2021-06-07 06:36:57 +0000 I use poky Gatesgarth - 3.2.3. The `service weston stop` call is not working for me. 90614 3 sjolley.yp.pm 2021-06-12 05:34:10 +0000 Question answered. Ask another question in you want it in NEEDINFO. 90617 4 JPEWhacker 2021-06-12 15:47:17 +0000 Sorry, I'm having a little trouble understanding why the sysvinit scripts are being used to start and stop Weston when systemd is in use. There are specific systemd services for Weston that should be used in stead. Can you clarify? 90622 5 mb 2021-06-14 06:06:10 +0000 No, I can't. I just see that it's not working - neither `/etc/init.d/weston stop` nor `service weston stop` works. Are you able to reproduce this? 90826 6 JPEWhacker 2021-07-01 15:22:18 +0000 If systemd is enable, you really need to use it to start and stop weston instead of the sysvinit scripts. If you can reproduce the same issue without systemd, please reopen the bug.