[OE-core] Cannot disable weston
We are no longer able to disable weston service with standard `systemctl disable weston@root.service`. On boot the service is started again. It seems likely this started with the introduction of a starting udev rule: https://github.com/openembedded/openembedded-core/commit/aa3bced2e1de2f4ba507aa014835b06edccc138a#diff-d92aa97566c1bd0dd1eb817bb4511cda Is this behaving correctly? Can the rule be made to honor the service disablement? Tom <>-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137989): https://lists.openembedded.org/g/openembedded-core/message/137989 Mute This Topic: https://lists.openembedded.org/mt/74037529/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] Cannot disable weston
On Wed, May 6, 2020 at 1:58 PM Otavio Salvador wrote: > > Hello all, > > Adding Khem on Cc. > > On Wed, May 6, 2020 at 5:42 PM Andrey Zhizhikin wrote: > > On Wed, May 6, 2020 at 10:29 PM Tom Hochstein wrote: > > > > > > We are no longer able to disable weston service with standard `systemctl > > > disable weston@root.service`. > > > > I've faced similar issues a while back, and also found out that weston > > has been actually started twice: once from udev, and once from > > systemd. At that time, I removed the udev locally on the EVK and > > didn't look further into it. > > > > > On boot the service is started again. It seems likely this started with > > > the introduction of a starting udev rule: > > > > > > https://github.com/openembedded/openembedded-core/commit/aa3bced2e1de2f4ba507aa014835b06edccc138a#diff-d92aa97566c1bd0dd1eb817bb4511cda > > > > > > Is this behaving correctly? Can the rule be made to honor the service > > > disablement? > > > > Or the other way around: can the systemd service be disabled? Or in > > general: is it possible to leave only one of those mechanisms, and > > which one is the correct one? > > Why the udev support was added and why this cannot be done in the service? > udev service integrates well when you have weston but for some reason no drm on machine so it only launches when system detects graphics/drm if you need to manually control it then disable the udev rule and it will show up disabled always and then can be managed manually. > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.brhttp://code.ossystems.com.br > Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#138358): https://lists.openembedded.org/g/openembedded-core/message/138358 Mute This Topic: https://lists.openembedded.org/mt/74037529/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] Cannot disable weston
Hello Khem, On Sat, May 16, 2020 at 12:00 PM Khem Raj wrote: > On Wed, May 6, 2020 at 1:58 PM Otavio Salvador > wrote: > > > > Hello all, > > > > Adding Khem on Cc. > > > > On Wed, May 6, 2020 at 5:42 PM Andrey Zhizhikin wrote: > > > On Wed, May 6, 2020 at 10:29 PM Tom Hochstein > > > wrote: > > > > > > > > We are no longer able to disable weston service with standard > > > > `systemctl disable weston@root.service`. > > > > > > I've faced similar issues a while back, and also found out that weston > > > has been actually started twice: once from udev, and once from > > > systemd. At that time, I removed the udev locally on the EVK and > > > didn't look further into it. > > > > > > > On boot the service is started again. It seems likely this started with > > > > the introduction of a starting udev rule: > > > > > > > > https://github.com/openembedded/openembedded-core/commit/aa3bced2e1de2f4ba507aa014835b06edccc138a#diff-d92aa97566c1bd0dd1eb817bb4511cda > > > > > > > > Is this behaving correctly? Can the rule be made to honor the service > > > > disablement? > > > > > > Or the other way around: can the systemd service be disabled? Or in > > > general: is it possible to leave only one of those mechanisms, and > > > which one is the correct one? > > > > Why the udev support was added and why this cannot be done in the service? > > > > udev service integrates well when you have weston but for some reason > no drm on machine so it only launches > when system detects graphics/drm > > if you need to manually control it then disable the udev rule and it > will show up disabled always and then can be managed > manually. I understand the use case you are intending to cover however: - we now have two overlapping mechanisms to start the weston service - we have more than a way to control the weston service it is confusing and I don't foresee a easy way to disable the udev service. How do you think it should be done? -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#138384): https://lists.openembedded.org/g/openembedded-core/message/138384 Mute This Topic: https://lists.openembedded.org/mt/74037529/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] Cannot disable weston
On Sun, May 17, 2020 at 2:52 PM Otavio Salvador wrote: > > Hello Khem, > > On Sat, May 16, 2020 at 12:00 PM Khem Raj wrote: > > On Wed, May 6, 2020 at 1:58 PM Otavio Salvador > > wrote: > > > > > > Hello all, > > > > > > Adding Khem on Cc. > > > > > > On Wed, May 6, 2020 at 5:42 PM Andrey Zhizhikin > > > wrote: > > > > On Wed, May 6, 2020 at 10:29 PM Tom Hochstein > > > > wrote: > > > > > > > > > > We are no longer able to disable weston service with standard > > > > > `systemctl disable weston@root.service`. > > > > > > > > I've faced similar issues a while back, and also found out that weston > > > > has been actually started twice: once from udev, and once from > > > > systemd. At that time, I removed the udev locally on the EVK and > > > > didn't look further into it. > > > > > > > > > On boot the service is started again. It seems likely this started > > > > > with the introduction of a starting udev rule: > > > > > > > > > > https://github.com/openembedded/openembedded-core/commit/aa3bced2e1de2f4ba507aa014835b06edccc138a#diff-d92aa97566c1bd0dd1eb817bb4511cda > > > > > > > > > > Is this behaving correctly? Can the rule be made to honor the service > > > > > disablement? > > > > > > > > Or the other way around: can the systemd service be disabled? Or in > > > > general: is it possible to leave only one of those mechanisms, and > > > > which one is the correct one? > > > > > > Why the udev support was added and why this cannot be done in the service? > > > > > > > udev service integrates well when you have weston but for some reason > > no drm on machine so it only launches > > when system detects graphics/drm > > > > if you need to manually control it then disable the udev rule and it > > will show up disabled always and then can be managed > > manually. > > I understand the use case you are intending to cover however: > > - we now have two overlapping mechanisms to start the weston service > - we have more than a way to control the weston service > > it is confusing and I don't foresee a easy way to disable the udev > service. How do you think it should be done? > In a bbappend remove udev service. Like you would do to disable service if it was controlled by systemd service > > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.brhttp://code.ossystems.com.br > Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#138385): https://lists.openembedded.org/g/openembedded-core/message/138385 Mute This Topic: https://lists.openembedded.org/mt/74037529/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] Cannot disable weston
On Wed, May 6, 2020 at 10:29 PM Tom Hochstein wrote: > > We are no longer able to disable weston service with standard `systemctl > disable weston@root.service`. I've faced similar issues a while back, and also found out that weston has been actually started twice: once from udev, and once from systemd. At that time, I removed the udev locally on the EVK and didn't look further into it. > On boot the service is started again. It seems likely this started with the > introduction of a starting udev rule: > > https://github.com/openembedded/openembedded-core/commit/aa3bced2e1de2f4ba507aa014835b06edccc138a#diff-d92aa97566c1bd0dd1eb817bb4511cda > > Is this behaving correctly? Can the rule be made to honor the service > disablement? Or the other way around: can the systemd service be disabled? Or in general: is it possible to leave only one of those mechanisms, and which one is the correct one? > > Tom > > -- Regards, Andrey. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137991): https://lists.openembedded.org/g/openembedded-core/message/137991 Mute This Topic: https://lists.openembedded.org/mt/74037529/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] Cannot disable weston
Hello all, Adding Khem on Cc. On Wed, May 6, 2020 at 5:42 PM Andrey Zhizhikin wrote: > On Wed, May 6, 2020 at 10:29 PM Tom Hochstein wrote: > > > > We are no longer able to disable weston service with standard `systemctl > > disable weston@root.service`. > > I've faced similar issues a while back, and also found out that weston > has been actually started twice: once from udev, and once from > systemd. At that time, I removed the udev locally on the EVK and > didn't look further into it. > > > On boot the service is started again. It seems likely this started with the > > introduction of a starting udev rule: > > > > https://github.com/openembedded/openembedded-core/commit/aa3bced2e1de2f4ba507aa014835b06edccc138a#diff-d92aa97566c1bd0dd1eb817bb4511cda > > > > Is this behaving correctly? Can the rule be made to honor the service > > disablement? > > Or the other way around: can the systemd service be disabled? Or in > general: is it possible to leave only one of those mechanisms, and > which one is the correct one? Why the udev support was added and why this cannot be done in the service? -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137992): https://lists.openembedded.org/g/openembedded-core/message/137992 Mute This Topic: https://lists.openembedded.org/mt/74037529/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-