1. Starting, stopping and restarting Weston[edit | edit source]
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[edit | edit source]
2.1. Weston service with udev rules[edit | edit source]
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[edit | edit source]
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[edit | edit source]