Registered User No edit summary |
Registered User mNo edit summary Tag: 2017 source edit |
||
| Line 1: | Line 1: | ||
<noinclude> | |||
{{ApplicableFor | {{ApplicableFor | ||
|MPUs list=STM32MP13x, STM32MP15x, STM32MP25x | |MPUs list=STM32MP13x, STM32MP15x, STM32MP21x, STM32MP23x, STM32MP25x | ||
|MPUs checklist=STM32MP13x, STM32MP15x, STM32MP25x | |MPUs checklist=STM32MP13x, STM32MP15x, STM32MP21x, STM32MP23x, STM32MP25x | ||
}} | }} | ||
</noinclude> | |||
==Starting, stopping and restarting Weston== | ==Starting, stopping and restarting Weston== | ||
Weston has its own | Weston has its own <code>systemd</code> service (/lib/systemd/system/weston-graphical-session.service) to easily start, stop and restart Weston. | ||
The following command stops the Weston service: | The following command stops the Weston service: | ||
| Line 19: | Line 20: | ||
==Preventing Weston from automatically starting on boot== | ==Preventing Weston from automatically starting on boot== | ||
=== Weston service with udev rules === | === Weston service with udev rules === | ||
The Weston service is automatically started on boot thanks to an '''udev rules''' file, most of the time located in | The Weston service is automatically started on boot thanks to an '''udev rules''' file, most of the time located in <code>/etc/udev/rules.d/*weston*</code>, for instance <code>/etc/udev/rules.d/71-weston-drm.rules</code>. | ||
To disable this service, rename this file (by changing its extension for instance), then restart your board. | To disable this service, rename this file (by changing its extension for instance), then restart your board. | ||
| Line 26: | Line 27: | ||
=== Weston service with systemd === | === Weston service with systemd === | ||
During the development process, when udev rules are not fully configured, the Weston service can be automatically started on boot as specified in | During the development process, when udev rules are not fully configured, the Weston service can be automatically started on boot as specified in <code>/lib/systemd/system/weston*</code>. | ||
In this case, the following command disables the automatic start of the Weston service: | In this case, the following command disables the automatic start of the Weston service: | ||
Latest revision as of 15:49, 8 October 2024
1. Starting, stopping and restarting Weston
Weston has its own systemd service (/lib/systemd/system/weston-graphical-session.service) to easily start, stop and restart Weston.
The following command stops the Weston service:
systemctl stop weston-graphical-session
The following command starts the Weston service:
systemctl start weston-graphical-session
The following command stops and then restarts the Weston service:
systemctl restart weston-graphical-session
2. Preventing Weston from automatically starting on boot
2.1. Weston service with udev rules
The Weston service is automatically started on boot thanks to an udev rules file, most of the time located in /etc/udev/rules.d/*weston*, for instance /etc/udev/rules.d/71-weston-drm.rules.
To disable this service, rename this file (by changing its extension for instance), then restart your board.
To re-enable this service, rename this file according to the udev rules of your system.
2.2. Weston service with systemd
During the development process, when udev rules are not fully configured, the Weston service can be automatically started on boot as specified in /lib/systemd/system/weston*.
In this case, the following command disables the automatic start of the Weston service:
systemctl disable weston-graphical-session
The following command enables the automatic start of the Weston service:
systemctl enable weston-graphical-session
Depending on your systemd configuration, it may be required to mask/unmask the Weston service with the following commands:
systemctl mask weston-graphical-session
systemctl unmask weston-graphical-session
You can check the status of the Weston service with the following command:
systemctl list-unit-files | grep -i weston
Please refer to the systemctl manpage[1] and to the Running Weston documentation[2] to know more about related details.
3. References